Operator and scope
Gitscrolls is operated by Matias Andrade Guzmán, an individual in Chile. Contact: [email protected].
This notice covers the Gitscrolls mobile and desktop apps, account and sync services, support, and gitscrolls.com. Gitscrolls does not sell your information. The apps are for people aged 16 or older.
Accounts, security, and support
Local use does not require an account. Account services process your email, profile and sign-in information, sessions, and verification records to provide access and keep the service secure. Requests can include your IP address and browser or device information. Passwords are sent for sign-up and sign-in; the stored password record is a hash, not the password itself.
If you sign in with Apple or Google, Gitscrolls receives your provider account identifier, email address (including an Apple private-relay address when supplied), verification status and any profile information supplied for account setup. These sign-ins do not grant access to GitHub repositories.
For Apple sign-in, Gitscrolls retains an encrypted refresh token on its server to revoke Apple authorization when you unlink Apple or delete your account. For account deletion, revocation runs after the seven-day cancellation window; failed revocations retain the encrypted credential for retry. Successful revocation clears it. Google access and refresh tokens and Apple access and identity tokens are not retained as account credentials.
We use email-delivery and mailbox-hosting providers for account messages, support and privacy requests. Matias personally handles requests, including what you send us and the records needed to handle them. Terms acceptance records contain the version and time; without an account, that record stays on your device.
GitHub access and credentials
The Gitscrolls GitHub App requests read access to contents, emails, metadata, starring, and watching. You choose the repositories it can access and can review or revoke access on GitHub.
GitHub credentials pass through Gitscrolls to GitHub for sign-in, token exchange, refresh, and revocation. GitHub tokens are stored on your device, not intentionally retained as account data.
Device credential stores protect stored tokens and API keys. They do not encrypt repository clones, notes, or chat history on disk. Protect your device and any exports or backups you make.
Local content and cloud sync
Repository clones stay on your device. You can create, edit, rename, reorder, and delete local notes without an account or sync subscription.
With active sync access, Gitscrolls and its hosting and sync providers store and transmit your notes, scroll descriptions, selected code snippets, and related repository information, including repository identity, file paths, and code references. Some app configuration is also synced. This lets your authorized devices work with the same content; it does not upload the whole repository or publish your content to other accounts.
Gitscrolls and its service providers can access synced content. Sync is not end-to-end encrypted and does not replace an independent backup. Keep your own backups. Sync and recovery features do not guarantee data preservation or recovery. Ordinary technical support is discretionary under the terms; this does not affect mandatory legal duties or your privacy rights.
Expiry stops sync, not local editing or access to recovery history. Cloud copies remain while the account exists, including during inactivity or suspension, so sync can resume when access is restored. These events do not automatically delete your account or content.
Optional AI transfers
If you use AI, the app sends your prompt and the repository, source-code, note, conversation, and tool context included in the request to the provider and endpoint you configure. Your API key is stored on the device and transmitted as needed to authenticate with that endpoint. You pay the provider’s charges.
Before your first-ever AI request, you must acknowledge the content transfer, provider policies and charges, and your responsibility to have permission to send the content. This acknowledgement covers requests to the AI destinations you configure. Once accepted, it is remembered across restarts; later requests and changes of provider, model or endpoint do not prompt again. Declining leaves non-AI app use available under the terms.
Your chosen AI provider is not automatically a provider contracted by Gitscrolls. Its retention, training, and confidentiality practices depend on its terms and your settings; Gitscrolls does not guarantee them or the correctness of AI output.
Content and model training
Gitscrolls will not use your code, notes, or other content to train AI models. The terms grant no permission for that use. If you use optional AI, your chosen provider’s training practices depend on its terms and your account settings, as explained above.
Usage analytics and crash reports
Gitscrolls uses PostHog to understand feature use and Sentry to investigate crashes and errors. Reports use opaque identifiers to connect activity and errors over time and, when signed in, across your devices. Before sign-in, PostHog uses a generated identifier; signing in can link earlier usage to your account. These reports are pseudonymous personal data, not anonymous data.
Reports are filtered to exclude email addresses, GitHub usernames, credentials, code, note content, repository names, file paths and repository URLs. Reports can include app versions, platform information and technical error and usage details. Receiving services also receive connection information such as your IP address; excluding identity fields from a report does not make the connection anonymous. Gitscrolls does not use app session replay. Local use does not require continuous internet access.
Usage analytics is on by default. You can turn it off in Settings without affecting local use, subscriptions or sync. Previous opt-outs, including an earlier Not now choice, stay off. Turning it off stops subsequent usage capture and account identification; it does not request deletion of earlier reports. The apps suppress IP-based location enrichment in outgoing analytics events; this does not hide your connection IP from the receiving service. Crash reporting is separate and stays on. Older distributed versions may collect different fields and require an update to change their behavior.
Sentry diagnostics are kept under the standard 30-day policy; provider backups expire separately. PostHog’s one-year reporting window is not an erasure guarantee. Identifiable account-linked analytics and diagnostics collected by earlier versions, including merged pre-login history, remain within the access and deletion scope described below, subject to provider capabilities.
Purchases
Apple or Google handles mobile purchases. RevenueCat connects transaction and subscription-access information to your Gitscrolls account. There is no web or desktop checkout. Store records, refunds, and subscription management follow the original store’s rules. Account deletion does not cancel a store subscription or erase records the store must retain; manage renewal there.
Website measurement and delivery
Cloudflare delivers the website and provides Web Analytics, including on legal pages, to measure visits and performance. It replaces self-hosted Umami for new measurements without deleting historical Umami records or backups. Measurements can include page addresses, referrers and browser or device information. Services receiving website requests also see connection IPs and request headers. Cloudflare says Web Analytics does not use cookies or local storage to track visitors; that is not a guarantee that website requests contain no personal information. See Cloudflare’s privacy policy and Web Analytics documentation.
There is no on-page measurement switch or consent banner. App controls do not control website measurement. Cloudflare’s own retention rules apply to its copies. Separately held website measurements, including historical Umami records, are kept up to 12 months. Only verified non-identifying totals, without individual events, URLs, referrers or visitor identifiers, may remain indefinitely.
Where information is processed
Matias operates Gitscrolls from Chile. Gitscrolls uses service providers in the United States for hosting, data storage, cloud sync, account-email delivery, usage measurement and diagnostics. Providers also supply website delivery, collaboration infrastructure and support/privacy mailbox hosting. They process the information needed for those functions. Provider support, subprocessors, network services and recovery copies may involve additional locations. A selected hosting region is not a promise that all processing stays there.
Apple, Google and GitHub process information under their own applicable arrangements. Your chosen AI provider or endpoint is separately described above; choosing it does not make it a Gitscrolls-contracted processor.
Contact [email protected] to ask about specific recipients, cross-border processing and applicable contractual safeguards, subject to necessary redaction of confidential or other people’s information.
Retention and backups
Accounts and synced content remain while the account exists, including during inactivity or subscription expiry. Security, service-operation, and request records are used for their respective purposes. Account deletion applies to account-linked live data, with the limited exceptions below.
Expired login-session and temporary verification records are deleted within 24 hours after expiry. This does not extend their validity or shorten active sessions. Gitscrolls operational logs are kept for no more than 30 days, except for narrowly necessary documented legal or actual-dispute records below.
Privacy-request emails and attachments are deleted within 90 days after the request is closed. A minimal record of the requester, request type, dates and outcome is kept for 12 months after closure, without code, notes or credentials. Deleting mailbox messages does not immediately erase every provider-held copy. The mailbox provider’s Trash handling and additional 30-day server recovery period apply separately.
Recovery copies expire separately. Managed database backups normally expire after 2 days; recovery can extend an individual backup’s expiry. Temporary copies made for service changes are kept up to 30 days from creation. Separately held website-measurement backups are kept up to 90 days from creation. Restores do not return deleted accounts or content to active service.
Only narrowly necessary records may be kept for a legal obligation or actual dispute, with a documented reason and duration; this is not a general right to retain code or notes after deletion. Independent providers and stores have their own retention rules. Live-data deletion does not mean immediate erasure from every backup or independent service.
For an actual active billing dispute, only necessary purchase references, dates, amounts and relevant dispute correspondence are retained. These records are deleted within 90 days after resolution unless a specific documented legal obligation requires longer. This does not automatically preserve code, notes, credentials or the rest of the account.
Access, export, correction, and deletion
Email [email protected] for access, export, correction, deletion, or privacy concerns. You can also start account deletion in the app or on the website. Matias handles requests. Access, export, correction and deletion require confirmation through your verified account email; a password, linked GitHub account or signed-in session does not replace it. Changing your account email requires confirmation from both the current verified and replacement addresses. If you cannot access your verified address, contact Matias about the limitation and your applicable rights. Initial replies are targeted within 7 calendar days; access/export/correction within 30 calendar days of receipt, subject to shorter legal deadlines. Your additional rights under applicable law remain available.
Depending on applicable law, you may also request restriction or temporary blocking of processing, object to processing, and exercise data-portability rights. Where processing relies on consent, you may withdraw it without affecting the lawfulness of processing before withdrawal. Requesting these rights does not authorize disclosure of someone else’s information.
You may complain to the competent data-protection authority or seek an applicable judicial remedy. For Chilean requests, the applicable remedies change when the amended law takes effect on 1 December 2026: current-law judicial remedies and, under the amended law, complaints to the Personal Data Protection Agency apply according to their respective requirements. For EU/UK requests, applicable supervisory-authority complaint rights remain available. You do not have to waive these remedies to use Gitscrolls.
Cloud exports cover account/profile information, stored subscription records, synced scrolls and notes including readable bodies and code snippets, and obtainable account-linked analytics and diagnostics. Exports use structured JSON plus readable content and explain unavailable or excluded categories. Credentials, other users’ data and local-only or unsynced work are excluded. Device-local backup/export is separate.
Exports are delivered through private, expiring and revocable links sent to your verified email, not email attachments. Download requires an explicit action. Availability and temporary-package retention are 7 days, after which the link is revoked and the package deleted. Replacement links require email verification and do not restart the original request deadline. These limits do not change retention of the underlying records or provider/backup copies. Requests remain available by email even if server access is suspended or you decline app terms.
For account deletion, Gitscrolls sends a confirmation link to your verified account email. An incoming email alone is not authorization. Confirmation disables server access and starts a 7-day cancellation window. A separate, single-use emailed cancellation link remains usable while ordinary account access is disabled. Opening it shows a confirmation screen; cancellation requires your explicit confirmation, not merely opening the link. Unless canceled, deletion begins after the window, with removal from live systems targeted within 30 calendar days of confirmation, including that window, subject to applicable legal requirements.
Deletion covers your account, sign-in data, and cloud-held content, including synced notes and code snippets. It includes requests to remove identifiable account-linked PostHog and Sentry data. Backups and limited legal/dispute records follow the rules above.
An explicit account-deletion request intentionally removes synced data, including copies removed from devices through sync. Sync and recovery features do not guarantee recovery of intentionally deleted data. Unrelated local-only or unsynced work and its recovery history are preserved. Reconnecting cannot resurrect the account or its deleted cloud data. Gitscrolls does not promise remote erasure of local copies on offline devices. Signing out, deleting a note, or removing a repository is not account deletion.
Changes
Material changes appear on this page with a version and effective date. Account holders receive email notice at least 14 calendar days before ordinary material changes take effect. Necessary urgent security or legally required changes may use shorter notice, with an explanation emailed as soon as practicable. Users without an account receive webpage updates, not direct or in-app notifications.
A privacy notice or change notice is not itself consent. Any separate choice required by applicable law remains separate from terms acceptance.