Privacy Policy

1. Information we collect

• Account information from Google sign-in: your name, email address, profile picture, Google account identifier, and authentication records and tokens needed to connect your account. We do not receive your Google password or request access to your Gmail inbox or Google Drive.
• Saved content: link addresses, page titles, descriptions, source, image addresses, tags, and text you share with a link. We also store your edits, AI-generated metadata, and save and update timestamps.
• Preferences and activity needed for the service: resurfacing frequency, selected day, timezone, batch size, email preference, resurfacing history, and AI-processing status.
• Sharing and integration information: share names, descriptions, visibility and selected links; access-token names, hashes, creation dates, and last-use timestamps. The server stores a hash of each personal access token rather than the usable token itself. The iPhone and Android apps keep their sign-in credential in the device’s secure storage (Keychain or Keystore).
• Usage records kept in our own database: when you open a saved link, when a reminder email is sent and opened, how each link was saved (website, extension, iPhone app or Android app), when a public share is viewed, and a record of each AI request. Section 8 explains these.
• Technical information processed by our infrastructure, such as IP addresses, request URLs, browser information, timestamps, and errors, to deliver, troubleshoot, and secure the service. If you contact us, we also receive your message and contact information.

2. How we use information

We use this information to sign you in, store and search your library, retrieve page metadata, improve saved titles and descriptions with AI, organize tags, generate resurfacing batches, deliver requested emails, enable sharing and integrations, respond to requests, and protect and maintain Revisit. We do not sell your personal data or use your library for targeted advertising.

3. How AI processing works

Revisit uses the OpenAI API to suggest a clearer title, a short description, and a topic tag for an eligible saved link. This can run after saving through Add Link, the browser extension, or the share sheet in the iPhone or Android app. Background recovery jobs can process pending saves, and an operator-run backfill can process older eligible links. AI access is currently restricted to an early-access allowlist; it does not run for every account or when insufficient information is available.

• An AI request can include the full saved URL, source platform, scraped title and description, site name, author, page type, and structured metadata such as a headline or publication date.
• It can also include text shared with the link, including a caption or browser-tab title, existing tags from your library to help reuse tags, and the saved title and description when an older link is processed.
• We do not add your account name, email address, Google credentials, or the full contents of your library to the AI request. However, personal or sensitive information within a URL, caption, title, description, or tag is included as part of that content. Do not save or share secrets or sensitive material you do not want processed.

The integration sends text metadata, not uploaded files, images, audio, video, or full article bodies. It does not give the model tools to browse your account. Search and resurfacing selection use database logic rather than AI. Generated text can be inaccurate; you can edit or delete it. A failed AI request does not prevent a link from being saved. For each AI request we keep a record of the model used, how many tokens it used, its cost and whether it succeeded, tied to your account and the link. That record does not include the text that was sent. There is currently no per-account AI switch in Settings; contact us about excluding your account from future AI processing.

OpenAI states that API inputs and outputs are not used to train its models by default unless the API customer opts in. Its default abuse monitoring logs may include prompts and responses and are retained for up to 30 days, with exceptions for legal or safety needs. We do not promise zero data retention. See OpenAI’s API data controls for its current terms. Deleting a link in Revisit does not recall a request already sent to OpenAI.

4. Page metadata and external websites

When you save a link, our server may request its page, a public metadata or embed service operated by YouTube, Reddit, X, Spotify, or GitHub, or Instagram’s public embed page for a post or reel. For short share links (such as Reddit’s), the server follows the redirect to find the original post. These services receive the requested address or content identifier and our server’s connection information. We do not forward your Google sign-in credentials or browser cookies to fetch saved pages. The extension can send a tab title that was visible while you were signed into another website. Visiting saved links or loading externally hosted images, such as your Google profile picture, also involves those websites and their own privacy practices.

5. Service providers and disclosures

• Vercel provides production hosting and the infrastructure through which we operate Revisit and its data storage.
• Google provides sign-in and processes authentication information under its own policy.
• OpenAI processes the AI inputs described in section 3.
• Emails are sent through an SMTP email-delivery provider. That provider receives your email address and email content, including selected saved links and their titles and descriptions, to deliver resurfacing and test emails. Your mailbox provider also processes delivered messages.

Providers process information as needed to deliver their services. Authorized operators may access data to provide support, investigate problems, handle privacy requests, and monitor how Revisit is used and what it costs to run. That monitoring happens in an internal dashboard that shows per-account counts and recent saves; it is not shared with anyone else. We may also disclose information when required by law or necessary to protect people, rights, or the security of the service. Providers may process data in countries other than yours; available protections depend on applicable law and provider arrangements. We do not promise storage in a particular country.

6. Payments

Paid plans are not enabled yet. When they are, payments will be taken on the Revisit website by a third-party payment processor, which collects your card, UPI or other payment details directly. We will receive your billing name, email, country, plan, payment status and the tax information needed for invoices (such as GST details for customers in India), but not your full card number or UPI PIN. We use your approximate location, from your connection, only to show prices in the right currency. We keep billing records for as long as tax and accounting laws in India require.

7. Public and private shares

Your library is private to your account unless you create a public share. Anyone with a public share URL can view its name, description, your display name, and the selected links with their titles and descriptions, without signing in. A private share is visible only to its owner. Public shares are marked not to be indexed by search engines, but recipients can copy or redistribute them. Deleting a share removes access through that Revisit URL; it cannot remove copies others made.

8. Cookies and storage on your device

Revisit uses cookies for sign-in and session security. If you share a link while signed out, a temporary cookie holds the URL and accompanying text for up to ten minutes to finish saving after sign-in. Browser storage remembers appearance preferences, and the service worker caches basic pages for offline fallback. The extension stores your access token and chosen server address locally in your browser and sends the active tab’s URL and title when you choose to save it. It does not upload your browsing history. The iPhone and Android apps store their sign-in credential in the device’s secure storage and tell our server which platform a save came from. You can clear site data or remove the extension through your browser; clearing storage may sign you out or require you to reconnect it. The application does not include advertising trackers or third-party behavioral analytics scripts. The website uses Vercel Web Analytics and Speed Insights to count page views and measure how fast pages load. They don’t use cookies, don’t follow you across other websites, and report aggregated numbers rather than a profile of you; the request still passes your IP address and browser details to Vercel, our host.

To see whether Revisit is working, we keep simple usage records in our own database: when you open a saved link from your library or a reminder email (those links pass through a Revisit address that notes the open and forwards you), whether a reminder email was sent and loaded its images, how a link was saved (web, extension, or app), when a public share is viewed, and the AI request records described in section 3. These records are tied to your account and the link, are not shared with third parties, and are deleted with your account. Email links that pass through Revisit are signed, so they work without signing in but only lead to the link they were made for.

9. Retention and deletion

We keep account data and saved links while your account remains active and the information is needed to provide the service. Removing an item deletes it from the active database, including its share memberships and resurfacing queue entries. You can delete shares and revoke access tokens separately. Account deletion and downloadable export are not currently self-service features; email us to request them. We may need to verify that a request comes from the account owner.

Logs, backups, and provider-held copies can have separate retention periods, and records may be retained where needed for security, dispute resolution, or legal obligations. We have not established a single guaranteed purge period for all such copies and cannot promise instant removal from every backup or provider system. Emails already delivered and copies of public shares held by others are outside our deletion controls. In development, when email delivery is not configured, the recipient address and email subject are logged instead of sent.

10. Your choices and privacy rights

You can edit or remove saved links, delete shares, revoke integration tokens, and turn off resurfacing emails in Settings. Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of your personal data, restrict or object to processing, withdraw consent where processing relies on consent, or complain to your local data-protection authority. Contact us to make a request. We handle requests subject to applicable law, identity verification, and any lawful exceptions. Signing out or revoking Google access does not by itself delete data already stored in Revisit.

If you are in India, the Digital Personal Data Protection Act, 2023 gives you the right to access a summary of your personal data and how it is processed, to correct, complete, update or erase it, to withdraw consent, to nominate someone to exercise these rights on your behalf, and to have grievances addressed. Brijesh Kumar Kushwaha handles grievances at kumarbrijesh9021@gmail.com. If you are not satisfied with our response, you can complain to the Data Protection Board of India. If you are in the European Union, the United Kingdom or another region with its own data-protection law, the rights that law gives you apply as described above.

Where a legal basis is required, we process information as necessary to provide the service you request, for legitimate interests in operating and securing it and responding to support requests, to meet legal obligations, or with consent where required. These bases depend on the processing and the law that applies to you.

11. Security, children, and policy changes

We use account authentication, access checks, and hashed personal access tokens to help protect your information. No storage or transmission system is completely secure. Protect your Google account and integration tokens, and contact us if you suspect unauthorized access.

Revisit is not directed to children under 13 or a higher minimum age required by local law. If you believe a child has provided personal information, contact us so we can investigate and address it.

We may update this policy as Revisit changes. We will update the date above and provide additional notice where required by law. Questions and privacy requests can be sent to kumarbrijesh9021@gmail.com.