ScribeLocal editing works without an account. Cloud sync is optional. Internet is used for cloud/account services and release downloads or updates, even though local note-taking is offline.
1. Local first, cloud optional
This notice covers the independent Scribe project, its website and the described development app workflow. “The project” refers to its maintainers, not any other organisation or product named Scribe. Local-only use does not send your notes to the project cloud. Signing in alone does not enable workspace sync. Cloud sync is off by default for each account on each device. Enabling it in General settings requires confirmation and uploads supported workspace data under your account; do not enable it for notes you want to keep only on your device. Account sign-in, security features, signed-in device registration/session check-ins and cloud-storage checks still communicate with their services when workspace sync is off. An offline profile has no cloud account and does not register a signed-in device.
Your saved offline profile and each online account use separate local workspace identifiers. Notes, folders, reminders, pending saves and preferences belong to their own workspace. Signing in does not convert, merge or upload an offline profile. To move notes, explicitly export them from one workspace and import them into the other. Local profiles have no password protection; separation within Scribe is not a security boundary against someone who controls your operating-system account.
The website previews use sample content and save nothing. This is a development notice: website-hosting details, provider log retention and release-specific service information will be confirmed before public cloud distribution.
2. What data is used, and why
Data is used to provide the features you choose, remember settings, synchronise changes and maintain account security. No advertising, sale of personal data, analytics profiling or AI training is implemented by this project in the inspected code. Third-party providers process information under their own notices.
| Category | Information | Purpose | Where it goes |
|---|---|---|---|
| Local notes | Titles, text/Markdown, pasted links, note IDs, folder assignment, draft/pin/trash state, creation and modification times. | Create, display, search and organise your notes; recover local edits. | Your device. Sent to Supabase only when using cloud sync. |
| Folders & preferences | Folder names, icons and colours; theme, accent, font, avatar colour, shortcuts, sorting, reminder presets and Windows options. Preferences are saved separately for the offline profile and each signed-in workspace. | Keep each workspace organised and remember its own choices. | Preferences stay in device storage for that workspace. Folders go to Supabase only when its cloud sync is enabled. |
| Reminders & notifications | Note ID, title used for a local notification, due time, lead time, update time, delivered/dismissed state and notification history. | Schedule reminders and avoid repeat alerts. | On device. Reminder schedules sync through Supabase when cloud sync is used. Native notification text is provided to Windows. |
| Cloud note data | Workspace notes, folders and reminder schedules uploaded when you enable cloud sync, linked to your account ID. | Synchronise the signed-in workspace across devices. | Supabase database. The maintainer administers this project and authorised access is possible; this is not end-to-end encryption. |
| Offline profile | Chosen display name, avatar colour and a randomly generated local workspace ID. No email, password or mandatory terms checkbox is required to create it; policy links are provided. | Personalise the offline workspace and keep its notes and preferences separate from signed-in accounts. | Only on your device. Creating an offline profile does not create a server account or upload this information. |
| Import & export | Selected note content, titles, folders, dates, pins, Draft/Trash status and optional reminder schedules; a local import job and a content fingerprint recording completed imports. Markdown files preserve fewer details. | Let you save a copy, move notes between workspaces, recover interrupted imports and warn about repeated imports. | Chosen export files and local device storage. Import does not turn sync on; an online workspace with sync already enabled can upload imported content through its normal queue. Export files contain readable content, not account credentials or app preferences. |
| Deletion verification & recovery | An account password and, when enabled, a current authenticator code for account deletion; a random deletion-status receipt, its hash/status/timestamps on the service, and a local recovery record. Offline deletion asks you to type confirm. | Verify ownership before account deletion and safely finish local cleanup after an interrupted request. | Credentials are processed for verification, not stored in the note database. The service clears the receipt’s account link after account deletion; the content-free receipt can remain until the app acknowledges cleanup. A local deletion marker can remain to prevent stale windows from writing deleted data. |
| Account & profile | Email address, account ID, display name, linked provider identifiers and provider profile fields such as name, email and avatar URL if supplied. | Create and identify the account, show its profile and manage optional sign-in methods. | Supabase Auth and profile records; session/profile copies may be on your device. |
| Authentication | Password submitted for email/password sign-in, access/refresh tokens, verification/reset codes, optional TOTP factor information and verification requests. Pending email-flow intent includes the email, purpose and request time locally. | Verify identity, maintain sign-in, reset passwords and provide two-step verification. | Supabase Auth processes credentials. Scribe does not store plaintext passwords in its note database. Persistent session tokens are stored locally. |
| Signed-in devices | Session ID, device/computer display name, client type, operating-system/platform, sign-in, refresh and last-seen times. Auth infrastructure may also process IP address and user-agent. | Show active devices, distinguish this session, revoke sessions and prevent abuse. | Supabase Auth/device-session records. Device registration may reveal the computer name. |
| Sync & retry history | Revision IDs, timestamps, change cursors, deleted-ID tombstones, storage counters, retry acknowledgements and, for note batches, copies of the operation payload/results. | Handle offline retries, avoid duplicate/stale writes, preserve conflicts and enforce storage limits. | Local queues and Supabase protocol records. Retry records can include prior note content. |
| Security events | Account/session IDs, revocation action, target session, number revoked and event time; service providers maintain their own operational/auth logs. | Record account-security actions, investigate failures and operate the service. | Private project records and provider infrastructure; not a public log. |
| Update/download traffic | Requested release URL, network address, browser/client information and request timing visible to the release host. | Retrieve update details or application downloads. | Your chosen official release host. No automated updater is currently configured in the inspected build. |
| Website visits | Standard network/request information available to the future hosting provider. This static site has no analytics, advertising tracker, login, form submission or note-storage endpoint. | Serve pages/assets and protect hosting infrastructure. | The chosen hosting provider. Hosting region and log-retention settings must be published once deployment is chosen. |
| Terms acceptance | Account ID, required and accepted Terms of Use version, server-recorded acceptance timestamp and acceptance method. Accounts created before this requirement are not given a fabricated acceptance record. | Record agreement when creating a new account and control access until required terms are accepted. | Private Supabase account records, retained for the account lifetime and removed with account deletion. |
| Privacy requests | Your reply address, request details, minimum information needed to verify account ownership and resolution correspondence. | Handle access, correction, deletion, consent withdrawal and grievances. | Project maintainer and their email service when you contact the privacy channel. Never send passwords or TOTP secrets. |
No AI inference service or model is connected in the current app. External links open only when you choose them; the destination can then process normal visit information. Clipboard text/HTML is processed when pasted; Quick Capture is not a background clipboard monitor.
4. How long data stays
Scribe does not maintain backup copies of your cloud database. Cloud sync is not a backup, and recovery of lost or permanently deleted data is not guaranteed. Use the in-app export to keep a separate copy of important notes. Export files are created only when you choose; this is not an automatic backup service. This statement covers backups maintained by the project; provider-controlled operational copies may follow separate retention rules.
- Local workspace data: stays until you delete it or remove the app’s storage. Signing out does not erase its notes or preferences. Deleting an offline profile removes that profile’s saved content from this device. Online-account deletion also removes that account’s saved workspace on the device completing deletion, after the server confirms it. Other workspaces are not removed. Uninstalling may leave storage behind, so use the in-app controls when you want deletion.
- Export files and import history: a file you export stays wherever you save or copy it until you delete it there. Import jobs and duplicate-detection history stay in the destination workspace until its local data is cleared. Removing a workspace does not delete exported files, OS backups or copies in other apps.
- Cloud allowance and size measurements: the 2 MB allowance counts UTF-8 note titles, serialized structured note content including formatting fields, folder data and active reminder metadata. Drafts and Trash count too. Local notes use Markdown, while cloud notes include structured formatting information, so the same notes can use more cloud space than the local serialized-data estimate. These measurements are not directly comparable and do not represent physical disk usage. Sync history and physical database/index overhead are outside this allowance. Local storage has no Scribe quota and remains subject to device/browser capacity.
- Active cloud data: remains for your account until deleted. Trashed notes remain until you permanently delete them or delete the account; no automatic trash expiry is configured. Trash still contains note content and counts toward the cloud allowance.
- Note retry receipts: the current retention design bounds them by 32 batches and 64 MB per account, with rollover on later writes. There is no fixed-day expiry; earlier note content can remain until rollover or account deletion.
- Reminder receipts/deleted IDs: retained for safe offline retry handling, with a 100,000-entry allowance for each history class. They are removed with an account's data, rather than blindly expiring and restoring stale changes.
- Project revocation logs: the current retention design retains up to 1,000 events/account and prunes records older than 90 days on that account's next logged revocation. It is not a guaranteed nightly deletion schedule.
- Provider logs and request correspondence: have separate retention. Actual configured periods must be confirmed for the deployed service; no unverified instant-deletion promise is made.
Records necessary for a legal obligation, security investigation or unresolved request may need limited retention. The applicable reason and scope should be explained when relevant. These are development settings; actual hosted retention will be confirmed for the release you use.
5. Your choices, rights and requests
- Stay offline: create an offline profile with only a display name. Its notes and preferences stay on this device. Cloud-only account settings are unavailable for this profile.
- Choose cloud sync: signed-in accounts start with sync off on each device. Open SettingsGeneralCloud sync to review the upload explanation and confirm your choice. Turning sync off keeps local notes available and stops new workspace uploads/downloads here. Previously uploaded data stays until deleted; enabling sync again uploads pending changes and downloads cloud changes.
- Export or import notes: open SettingsGeneralMove your notes. Choose a Scribe backup to preserve note details, or a Markdown ZIP for use in other apps. You can select notes, filter folders, include Drafts/Trash, and choose reminder schedules. Both formats can be imported into offline or online workspaces. Imports add fresh copies, do not replace existing notes, and do not restore credentials or app preferences. Activating future reminders requires a separate choice. Export includes data saved on this device; sync first if you need changes from other devices.
- Control saved data: use SettingsAccountDelete Data to choose cloud data, local data, or both. Account and offline-profile deletion are separate actions described below. Deleting content is different from signing out or turning sync off.
You may request information about your personal data and its recipients, correction, an available copy, erasure, withdrawal of consent for optional processing, and grievance review. Nomination and other statutory requests will be handled to the extent applicable law provides them. In-app note export is available without emailing support; requests concerning other personal account records can use the privacy channel below.
Email scribesupport@proton.me. Use “Scribe privacy request” or “Scribe grievance” as the subject. Account deletion does not require an email. Include your registered email, if applicable, and the request scope. Do not send passwords, session tokens, authenticator secrets or sensitive note content.
Requests may require proportionate verification of ownership to prevent someone else deleting or accessing your data. Request information is used only to handle and document the request, not marketing. Acknowledge and resolve requests within the period required by applicable law; where delay or limited retention is necessary, explain it. This notice does not promise an unimplemented automated response system.
If a grievance remains unresolved, you may use a competent regulator or lawful remedy available to you. India's DPDP framework has phased commencement; Board procedures and statutory deadlines should be checked against the official rules in force when you make the request. This notice does not remove applicable rights.
6. Account and data deletion is possible
Choose the action that matches what you want to remove. The app shows the scope and a data summary before you confirm. No deletion email is required.
What deletion does not do
- Moving a note to Trash is not permanent erasure. Permanent note deletion removes the active record; earlier content may remain in bounded retry history until rollover or account-data deletion.
- Signing out or revoking a session is not account/data deletion. Other devices may still hold local copies after losing cloud access; clear those copies on each device you no longer want to keep.
- Deleting a workspace does not remove files you exported, copies imported into another workspace, OS backups, other apps’ copies, or your separate Google/GitHub account.
- Scribe does not maintain project database backups. Provider-controlled operational copies and lawful retention exceptions may follow separate rules; deletion is not a promise of immediate erasure from every provider system.
- A content-free deletion-status receipt and local deletion marker may remain to confirm cleanup and prevent stale writes, as described in the data table. They do not retain your deleted notes.
7. Security and children
HTTPS, account-scoped database policies, session checks and optional TOTP help protect cloud access. Local files and cloud notes are not end-to-end encrypted. Anyone controlling your OS account may access local data. No system can guarantee complete security.
The project is not designed to collect children's data through cloud accounts. The current release has no verified parental-consent workflow; public cloud access for children under 18 must not be offered without the safeguards required by applicable law. Local-only use does not require supplying an age or identity to the project.
8. Notice changes
The date above identifies this draft's update. Material changes to cloud processing, providers, hosting, update delivery or data controls will be reflected in a revised notice before those changes are presented to users. Review the notice for the release you use.