Privacy Policy

Cue (“Cue,” “we,” “us,” or “our”) is operated by Brian Roney.

This Privacy Policy explains how Cue collects, uses, stores, and discloses information when you use the Cue mobile application, Cue’s mobile share extension, the Cue browser extension, and our website at sharetocue.com.

The current Cue beta is intended for users in the United States who are at least 13 years old.

If you have questions about this Privacy Policy or Cue’s privacy practices, contact us at [email protected].

1. Overview

Cue is designed to let you save information from different apps, organize that information, and optionally create reminders.

Cue is designed to keep certain information on your device whenever possible.

You may use the Cue mobile application without creating an account. In guest mode, your saved Cue content is stored locally on your device and is not synchronized to Cue’s cloud database. The Cue browser extension does not offer guest mode. It cannot save a page, selected text, or a link until you sign in to a Cue account.

If you create an account, certain reminder, folder, and account information is transmitted to and stored with our cloud service provider so Cue can synchronize supported information across your devices.

Images and screenshots that you share with Cue are stored locally on your device and are not uploaded to Cue’s cloud storage.

Cue does not sell your personal information, use your saved Cue content for advertising, share your information for cross-app behavioral advertising, or use your Cue content to train AI models.

2. Information We Collect and Process

The information Cue processes depends on how you use the service and whether you create an account.

Account Information

If you create a Cue account, we may process:

• your email address;
• a Cue/Supabase user identifier;
• information necessary to authenticate your account;
• information provided by your selected authentication provider;
• authentication and session information.

Cue currently supports authentication through email and password, Sign in with Apple, and Google Sign-In.

If you use email and password, Cue does not maintain a separate copy of your plaintext password. Authentication is handled through Supabase Auth.

Apple or Google may provide Cue or our authentication provider with information associated with your authentication request according to the choices you make with those services. For example, Sign in with Apple may provide an Apple relay email address instead of your personal email address.

Content You Save in Cue

Depending on how you use Cue, you may create or share information such as:

• reminder titles;
• notes;
• reminder dates and times;
• shared text;
• URLs;
• source domains;
• folder names;
• completion, snooze, and reminder state;
• page titles and descriptions;
• preview image URLs;
• favicons and other link-preview information.

This information is stored locally on your device.

If you are signed in, supported reminder and folder information may also be synchronized to Cue’s cloud database so it can be available across your signed-in devices.

Browser Extension

The Cue browser extension saves a page, selected text, or a link that you choose. It is separate from Cue’s mobile share extension.

Sign-in opens the Cue web app at https://app.sharetocue.com/extension-auth. You enter your Cue account there. The extension then keeps its own session in browser storage. That session contains the authentication tokens returned by Supabase and the account record Supabase returns with them, including your email address when Supabase provides it. Signing out of the Cue website does not sign the extension out.

When you save, the extension sends the following to Supabase so the item can be stored with your signed-in Cue account:

• the page URL and browser title, the text you selected, or the link URL you chose;
• the reminder time you chose, which may be no reminder;
• the folder you chose, or no folder.

The extension does not ask for a note. It does not upload images or screenshots, run screenshot recognition, or fetch link previews. It does not include an analytics or crash-reporting SDK.

The extension reads the URL and title of the tab where you open Cue or use a Cue menu. It may keep that page, selection, or link in the browser’s session storage until you save, close the signed-in popup, or 15 minutes pass. It does not read your browsing history, other tabs, website forms, or cookies.

On Firefox, a script runs only on the Cue sign-in page to hand the session to the extension. That script does not read the page.

The browser extension uses this information only to save the item you chose into your Cue account and to keep you signed in for that purpose. Cue transfers that information to Supabase, which stores your signed-in Cue account. Cue does not sell this information, use it for advertising, or use it to determine creditworthiness.

Images and Screenshots

Cue can receive images or screenshots that you intentionally share with the app.

Cue stores these image files locally on your device. Cue does not upload the image bytes to Cue’s cloud database or cloud object storage.

Images may contain personal, private, or sensitive information depending on what you choose to share with Cue. Because the image remains on your device, you are responsible for deciding what content you choose to save.

Screenshot Recognition and OCR

Cue may analyze supported screenshots to help identify their source or generate useful reminder information.

This analysis is performed on-device using platform technologies such as Apple Vision on iOS and Google ML Kit on Android.

Cue may derive information such as:

• the apparent source application;
• a sender or display name visible in a screenshot;
• a phone number visible in a screenshot;
• a source type;
• a confidence indication.

Cue’s detailed screenshot-recognition fields remain local to the device and are not synchronized to Cue’s cloud database.

However, Cue may use recognized information to generate ordinary reminder content. For example, Cue might create a reminder title such as “Message from Sam.” If you are signed in, that resulting reminder title may synchronize to Cue’s cloud database in the same way as another reminder title.

Cue does not currently send screenshots to a cloud-based OCR or generative-AI service for this processing.

Link Preview Information

When you save a URL, Cue may retrieve information used to create a preview, including:

• page title;
• description;
• domain;
• favicon;
• preview image URL;
• other publicly available page-preview metadata.

These requests are generally made directly from your device to the website associated with the URL or to a preview endpoint offered by a third-party service.

For certain services, Cue may use publicly available preview or oEmbed endpoints, including services associated with Reddit, YouTube, TikTok, or Spotify.

Because these requests come from your device, the destination website or preview provider may receive technical information normally associated with an internet connection, including your IP address, user agent, and the URL being requested.

Cue stores the resulting preview metadata when needed to provide the service. Cue does not store the complete HTML page as part of the saved preview.

When Cue displays a remotely hosted preview image, your device may also contact the host of that image directly.

Device and Application Information

Cue and service providers used to operate Cue may process limited technical information associated with use of the application, such as:

• application version;
• operating-system version;
• device type or model;
• technical application identifiers;
• session or installation identifiers;
• IP address;
• crash and diagnostic information.

Cue does not use the iOS advertising identifier, IDFA, for advertising or cross-app tracking.

Product Analytics

Cue may use PostHog to understand how people interact with the application.

Analytics may include information such as:

• application events;
• feature usage;
• coarse interaction information;
• Cue user or guest identifiers;
• technical device and application information supplied by the analytics SDK.

Cue’s application-authored analytics events are designed not to include the contents of your reminder titles, notes, shared text, saved URLs, screenshot sender names, phone numbers, or images as analytics event properties.

We use this information to understand product usage and improve Cue.

We do not use Cue analytics for third-party advertising or cross-app behavioral advertising.

Crash and Diagnostic Information

Cue may use Sentry to identify crashes, errors, performance issues, and other technical problems.

Sentry may receive technical information such as:

• crash reports;
• stack traces;
• application version;
• operating-system and device information;
• performance information;
• technical error information.

Cue configures Sentry not to send default personally identifiable information and takes steps to limit user-generated content from diagnostic metadata. However, technical error reports may contain information generated in connection with the error.

We use diagnostic information to maintain and improve Cue.

Notifications

Cue uses local device notifications to provide reminders.

Reminder notifications may contain identifying reminder information, such as a reminder title or an excerpt of shared text, so that the notification is useful.

Under the current architecture, Cue schedules these reminder notifications locally on your device rather than sending reminder content through a Cue remote-push server.

You control notification permission through your device settings.

Support Communications

If you email [email protected], we receive the information you choose to include in your email, along with information normally associated with email communications such as your email address.

We use this information to answer your request and provide support.

Cue does not currently send marketing emails.

3. Guest Mode

You can use the Cue mobile application without creating an account. The browser extension does not offer guest mode.

When you use Cue as a guest:

• your Cue reminders and folders are stored locally on your device;
• images and screenshots remain locally stored;
• Cue does not synchronize your saved Cue content to Cue’s cloud database.

Certain network activity can still occur in guest mode.

For example:

• Cue may contact a website to generate a preview for a link you saved;
• product analytics may be transmitted if analytics are enabled;
• crash diagnostics may be transmitted if diagnostic reporting is enabled.

Cue may assign a local guest identifier for application functionality and analytics.

Guest users can use Cue’s local-data deletion controls to remove Cue content stored on the device.

4. Cloud Synchronization

If you create and sign into a Cue account, Cue uses Supabase to provide authentication and cloud synchronization.

The information synchronized to Cue’s backend may include:

• account identifier;
• reminder titles;
• notes;
• URLs;
• shared text;
• preview metadata;
• reminder schedule and state;
• folder names and organization information;
• synchronization timestamps and related operational data.

A save from the browser extension is written to that same signed-in account. The extension sends the page, selection, or link you chose, the reminder time, and the folder. It does not send a note, an image, or link-preview fields.

Cue does not synchronize the original image or screenshot files stored in Cue’s local image storage.

Cue also does not synchronize Cue’s detailed local screenshot/OCR fields, although ordinary reminder content derived from those fields may synchronize as described above.

5. How We Use Information

We use information processed through Cue to:

• provide and operate the Cue application;
• create and manage accounts;
• authenticate users;
• save, organize, and synchronize reminders and folders;
• save a page, selected text, or link you choose in the browser extension;
• generate link previews;
• analyze supported screenshots on-device;
• schedule reminders and notifications;
• maintain synchronization between devices;
• provide customer support;
• understand how Cue features are used;
• diagnose technical problems;
• maintain the security and integrity of the service;
• prevent misuse;
• comply with applicable legal obligations;
• improve Cue.

We do not use your Cue content to train AI models.

6. How We Disclose Information

We do not sell your personal information.

We do not use your saved Cue content for advertising.

We do not share personal information for cross-app behavioral advertising.

We may disclose information to service providers when necessary to operate Cue.

Supabase

We use Supabase for services including:

• authentication;
• account management;
• database hosting;
• synchronization;
• realtime functionality;
• account deletion infrastructure.

If you are signed in, Supabase processes your account information and the Cue information synchronized to our backend.

Apple

Cue uses Apple services and platform capabilities including Sign in with Apple and, on iOS, operating-system features used for local notifications, secure credential storage, application sharing, and on-device text recognition.

Apple’s treatment of information processed through its services is governed by Apple’s own terms and privacy policies.

Google

Cue may use Google for authentication when you choose Google Sign-In.

On Android, Cue also uses Google ML Kit for on-device text recognition. Cue’s current OCR implementation performs that image analysis locally rather than uploading screenshots to a Cue cloud OCR service.

Google’s treatment of information associated with Google authentication is governed by Google’s own terms and privacy policies.

PostHog

We may use PostHog for product analytics.

PostHog may receive application events, Cue user or guest identifiers, network information, and technical device/application information associated with those events.

We use PostHog for product analytics, not advertising.

Sentry

We may use Sentry for crash reporting and technical diagnostics.

Sentry may receive crash information, stack traces, performance information, and technical application/device context.

We use Sentry to maintain and improve Cue.

Cloudflare

Our website is hosted using Cloudflare Pages.

When you visit sharetocue.com, Cloudflare may process technical information associated with delivering the site, such as IP addresses and request information.

Website Analytics

We may use privacy-focused, cookie-free analytics on sharetocue.com to understand basic website usage.

If Umami is enabled on the production website, it may process page-view and site-interaction information for this purpose.

We do not use website analytics for cross-site advertising.

Websites and Preview Providers

When Cue retrieves link previews, your device may communicate directly with the relevant destination website, image host, or preview/oEmbed provider.

Those third parties receive information associated with the request according to their own privacy practices.

7. Advertising, Tracking, Sale of Information, and AI Training

Cue does not currently contain advertising.

We do not sell personal information.

We do not use Cue content for advertising.

We do not share personal information for cross-context or cross-app behavioral advertising.

We do not use IDFA for advertising tracking.

We do not use saved Cue content to train AI models.

Cue currently uses on-device OCR technology for supported screenshot recognition rather than sending that content to a third-party generative-AI model.

8. Website Cookies and Similar Technologies

The Cue marketing website does not currently require advertising cookies or cross-site tracking cookies.

We may use privacy-focused, cookie-free website analytics as described above.

Your browser, Cloudflare, or third-party destinations that you choose to visit may process information according to their own practices.

9. Data Retention

We retain information for as long as reasonably necessary to provide Cue, maintain the service, fulfill the purposes described in this Privacy Policy, resolve disputes, enforce agreements, maintain security, and comply with applicable legal obligations.

Cue does not currently use a single fixed retention period for every category of information.

Active account information and synchronized Cue content may generally remain in Cue’s primary systems while your account remains active.

When you delete an individual synchronized item, Cue may temporarily retain a deletion record or tombstone so that the deletion can be synchronized correctly across devices.

Service providers such as hosting, analytics, authentication, crash-reporting, or infrastructure providers may retain backup, security, diagnostic, or operational records according to their own retention schedules and legal obligations.

We will update this Privacy Policy if Cue adopts materially different retention practices.

10. Deleting Your Data

Individual Cue Content

You can delete individual Cue content through the application.

When you delete a reminder containing a locally stored Cue image, Cue removes the Cue-managed local image associated with that reminder.

For signed-in users, Cue may retain a limited cloud deletion marker as needed to synchronize the deletion to other devices.

Account Deletion

Signed-in users can request account deletion through Cue’s Settings.

When account deletion is completed:

• Cue deletes the authentication account;
• Cue deletes the associated reminder, folder, and account records from its primary application database;
• Cue clears Cue-managed account data stored locally on the device;
• Cue removes Cue-managed local images associated with the deleted data;
• Cue clears the local authenticated session;
• Cue cancels Cue reminder notifications associated with that local data.

Some information may remain for a period in backups, security records, diagnostic records, or service-provider logs where retention is necessary for security, fraud prevention, legal compliance, disaster recovery, or other legitimate operational purposes.

Analytics or diagnostic information that has already been separated from the active Cue account may also remain according to the relevant provider’s retention practices.

Guest Data

Guest users do not have a cloud Cue account to delete.

Guest users can use Cue’s local-data deletion controls to remove Cue content and Cue-managed images stored on the device.

You may also remove locally stored application data using controls available through your device or by uninstalling Cue, subject to the behavior of your operating system and device backups.

11. Your Choices and Privacy Rights

You can choose whether to create a Cue account.

You can:

• use Cue in guest mode;
• edit or delete saved Cue content;
• control notification permission through your device;
• delete your Cue account if you are signed in;
• delete local Cue data if you use Cue as a guest;
• contact us with privacy questions or requests.

Depending on where you live and applicable law, you may have additional rights regarding your personal information, which may include rights to request access, correction, or deletion of information.

To make a privacy request, email [email protected].

We may need to verify your identity before completing a request involving account information.

12. Security

We use technical and organizational measures intended to protect information processed through Cue.

These measures include use of secure network connections, authenticated backend access, database access controls, secure operating-system credential storage, and platform security features.

Cue’s synchronized reminder content is not end-to-end encrypted. Information stored in Cue’s cloud database is therefore accessible to the infrastructure necessary to operate Cue and may be accessible to authorized service-provider or Cue systems as required to provide and secure the service.

No system can guarantee absolute security, and we cannot guarantee that information will never be accessed, disclosed, altered, or destroyed improperly.

13. Third-Party Content and Services

Cue can save links and content originating from third-party apps and websites.

Cue does not control the privacy practices of those third parties.

If you visit a third-party website, authenticate through a third-party service, or interact with third-party content, that third party’s terms and privacy policy govern its own collection and use of information.

14. Children

Cue is intended for users who are at least 13 years old and is not directed to children under 13.

We do not knowingly collect personal information from children under 13.

If you believe a child under 13 has provided personal information to Cue, contact us at [email protected] so we can investigate and take appropriate action.

15. United States Beta

The current Cue beta is offered to testers in the United States.

Information processed by Cue and our service providers may be processed in locations where those providers operate their infrastructure.

If Cue expands availability to additional countries or regions, we may update this Privacy Policy and our data-processing practices as appropriate.

16. Beta and Future Paid Service

The current Cue beta is free.

Cue plans to offer paid subscriptions when the product is publicly released, but the current beta does not process Cue subscription purchases.

If Cue introduces paid subscriptions or new payment providers, we may update this Privacy Policy to explain any additional information associated with purchases or subscriptions.

17. Changes to This Privacy Policy

We may update this Privacy Policy as Cue changes.

If we make material changes, we will update the effective date above and may provide additional notice through the app, website, or another appropriate method.

Your continued use of Cue after an updated Privacy Policy becomes effective is subject to the updated policy, except where applicable law requires another form of notice or consent.

18. Contact Us

For privacy questions, data requests, or support, contact:

Brian Roney
Operator of Cue
Email: [email protected]