Alt+Q Notes Privacy Policy
- Operator: RICO
- Privacy contact: ariadnelabs.contact@gmail.com
- Effective date: September 15, 2026
- Last updated: November 18, 2026
1. Scope
This policy explains how the Alt+Q Notes Chrome extension handles information when you create notes, attach images, save tabs, use the local calendar view, save a draft, connect optional Google Drive sync, and use features covered by usage analytics.
You can use the note-taking features without an account or cloud connection. Notes and attachments are stored in your current Chrome profile. Section 4 applies to versions that offer Google Drive sync, and only after you connect it. Version 0.3.0 keeps notes and attachments on your device. On first use, the extension presents its feature introduction and analytics disclosure. Note-taking starts after you choose Agree and start. Builds with analytics enabled then send the usage events described below to PostHog.
2. Information We Handle and Why
| Information | Purpose | Storage and transmission |
|---|---|---|
| Note content, formatting, colors, ordering, and creation, modification, and deletion timestamps | Creating, displaying, organizing, and restoring notes | Stored locally; saved notes and their ordering also sync to your Drive if you connect sync |
| Images and screenshots you paste, including image dimensions and formats | Attaching and previewing images | Stored locally; attachments to saved notes also sync to your Drive if you connect sync |
| Open-tab titles and URLs read by tab-selection features, saved tabs, and note sources | Selecting tabs, saving links to notes, and reopening them | Processed locally for selection; only tabs and sources you save with a note are included in sync |
| Note, revision, image and device identifiers, attachment hashes, and deletion records | Maintaining note relationships, ordering, Trash, sync integrity, and conflict recovery | Stored locally; technical records needed for sync are also stored in your Drive if you connect sync |
| Unsaved draft text, images, and tab links | Resuming edits after the editor or browser closes | Stored locally in the current Chrome profile |
| Installation identifiers, usage events, and environment information | Analyzing feature use, return use, and task success or failure, and improving the product | Sent to PostHog in builds with analytics enabled |
The extension reads tab information in response to user actions needed for its note-taking features. It does not continuously collect your full browsing history. Image pasting is initiated by you; the extension does not continuously monitor your clipboard.
3. Local Storage
Notes and images are stored in the extension's IndexedDB database. Settings, installation identifiers, and similar information are kept in Chrome extension storage. Session information and some temporary data are kept in browser session storage or memory.
Unsaved drafts and their attachments stay in the current Chrome profile. A draft is removed when you explicitly discard it or when its note is successfully saved. Local calendar settings and metadata stay on the device. Dates written in a saved note are part of its text and can sync with the note.
The operator does not receive a copy of your notes on its own servers or through analytics. Usage analytics contains only the coarse allowlisted information described in Section 5.
4. Optional Google Drive Sync
In a version that supports Drive sync, choose Sync across devices and approve Google’s authorization prompt to connect. The extension uses Chrome Identity to request the drive.appdata scope. This scope allows the extension to read, write, and delete its own application data in a hidden area of your Google Drive. Your ordinary Drive files are outside this scope.
While connected, the extension sends saved note content, formatting, colors, images and screenshots, saved tab titles and URLs, note sources, ordering, revisions, and Trash or permanent-deletion records directly to Google Drive over HTTPS. It uses this information to synchronize your saved notes across Chrome profiles and devices connected to the same Google account, resume interrupted uploads, and preserve conflicting edits. Unsaved drafts are stored locally. The extension stores an account identifier returned by Drive in your Chrome profile to detect account changes. Chrome Identity handles OAuth tokens for Drive requests. This account identifier and the tokens are excluded from analytics.
Use Log out in the extension to stop further sync. The notes already on the device and the copies in that Drive remain. You can also revoke the app's Google access in your Google Account settings. If you choose to connect a different Google account, the extension can merge the saved notes remaining on this device with that account's app data. See Google's Privacy Policy for information about Google's handling of data.
5. PostHog Usage Analytics and First-Use Agreement
Before you agree, the extension does not contact PostHog, create analytics installation/session/workflow identifiers, store pre-agreement actions for later upload, or allow access to the note-taking interface. If you close the panel, the disclosure appears again the next time you open it. When the disclosure changes materially, its version can require agreement again.
After you choose Agree and start, builds with analytics enabled send the following information to PostHog's EU ingestion endpoint (eu.i.posthog.com):
- Random installation, session, workflow, and event identifiers
- Event timestamps and sequence within a session
- Extension version, Chrome major version, and operating system family
- Events for completing agreement; opening note interfaces; first successful save; meaningful active days; opening, saving, or deleting notes; adding attachments; and the start, progress, and outcome of note creation and editing
- Calendar events for opening the calendar or a schedule popover, saving schedule adjustments, and responding to an inferred-time prompt
- Quick-note iframe outcomes and fixed fallback reason codes used to measure whether opening the editor or its side-panel recovery succeeded
- Feature entry points, attachment types, count ranges, whether tabs are attached, parser version, coarse date-format and time-interpretation categories, whether a schedule field changed, success/failure/cancellation outcomes, and predefined error codes
The installation identifier is used to recognize return use of the same installation and is not linked to your name or Google account. Because these identifiers distinguish repeated use, we do not describe this data as fully anonymous.
Analytics events do not include note content or titles, note identifiers, exact dates or times, schedule titles or matched source text, images or screenshots, clipboard content, search terms, tab URLs or titles, Google account information, authentication tokens, keystrokes, raw error messages, or stack traces. We also do not use automatic pageview collection, DOM capture, screen recording, or session replay.
PostHog may receive your source IP address as part of network communication. The extension sends a setting that disables geographic enrichment. Server-side handling, including whether IP addresses are stored, depends on the actual PostHog project settings.
This release requires the first-use agreement to enter the product and does not provide a continue-without-analytics path. Disabling or uninstalling the extension stops future transmission. Builds with analytics disabled do not send events to PostHog even after agreement.
- Analytics retention: We retain analytics data indefinitely, without a fixed retention period, to analyze long-term feature usage and return use. We do not set a scheduled automatic deletion deadline. Uninstalling the extension does not delete analytics data already sent.
- Analytics deletion requests: Contact ariadnelabs.contact@gmail.com with questions or requests about deleting analytics data. Analytics identifiers are not linked to your name or Google account, so your email address alone may not identify the events associated with your installation.
For information about PostHog's own handling of data, see the PostHog Privacy Policy.
6. Sharing and Limits on Use
The extension uses Google Drive for optional sync and PostHog for enabled usage analytics. Sections 4 and 5 describe what is sent to each service and why.
We do not sell user data or use it for personalized advertising. Note content is not provided to analytics services. User data handled through the extension is used to provide and improve note-taking and related user-facing features, in accordance with the Limited Use requirements of the Chrome Web Store User Data Policy.
Our use of data received through Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. We use Google Drive data to provide sync and conflict recovery. We exclude it from analytics and advertising.
7. Retention and Deletion
Notes and Images
Notes remain on your device until you delete them. Deleted notes move to Trash. Items that have been in Trash for 30 days are permanently deleted when the extension's cleanup process runs. You can also permanently delete notes from Trash yourself. Cleanup may be delayed while Chrome is not running.
Synced Drive Data
Synced note revisions and images remain in your Drive app data until they are removed. When a synced note is permanently deleted, a connected browser processes the deletion and removes its saved Drive revisions and attachments. A minimal deletion record can remain to prevent the same note from returning when another device reconnects. Cleanup can be delayed while the extension is offline or disconnected. If an unsynced edit conflicts with a permanent deletion, a copy of that edit can remain on the device where it was made.
To remove all hidden Alt+Q Notes app data from your Drive, disconnect sync on your devices and use Google Drive's Settings → Manage apps → Options → Delete hidden app data for Alt+Q Notes when that option is available. You can find more information in Google's storage help. You can separately remove the app's access in Google Account connections.
Uninstalling
Uninstalling the extension removes its stored data from that browser profile. Local migration backups created by earlier versions may remain in extension storage after individual notes are deleted.
Uninstalling the Chrome extension does not send a request to remove your Drive app data or analytics data already sent. Local data belonging to separate Chrome profiles or other installations must be removed from those profiles or installations separately.
Usage Analytics
Analytics data already sent is subject to the retention and deletion practices in Section 5. The operator cannot directly access your device's note storage to delete notes for you.
8. Security
Communication with Google Drive and PostHog uses HTTPS. The extension does not add its own encryption to locally stored notes. You should protect access to your device and browser profile.
9. Contact and Policy Changes
For questions about privacy or data deletion, contact ariadnelabs.contact@gmail.com. Do not include note content or authentication tokens in your inquiry.
When this policy changes, we will update its content and effective date. Material changes to data handling will be accompanied by any required notices and consent procedures.