S
saive.myFREE BETA · OPEN NOWFeaturesPricingLog in →

Privacy Policy

Effective Date: June 17, 2026 Last Updated: October 9, 2026

Saive ("we," "us," or "our") is registered in Ontario, Canada. This Privacy Policy explains how we collect, use, disclose, and protect your information when you use the Saive web application, the Saive iOS app and its share extension, browser extensions, MCP server, AI assistant plugins, and related services (collectively, the "Service").

By using the Service, you agree to the collection and use of information in accordance with this policy.


1. Information We Collect

Information You Provide

  • Account information. When you sign up, we collect your email address and display name. Authentication is handled by our identity provider (Clerk), which may also receive information from Google if you choose to sign in via Google OAuth.
  • Saved content. When you save a bookmark, we store the URL, page title, and the article body text. Our browser extension and the iOS share extension extract that text on your device from the page you are viewing; for some video pages, the share extension fetches the video's transcript on your device and sends it as the article text. When neither captured the text, our servers fetch the page. You may also add personal notes, highlights, tags, and folders to your saves, and import bookmarks from a file.
  • Profile information. If you opt in to a public profile, we collect your chosen display name, username slug, bio, and optional avatar.
  • Communications. If you contact us (for example, through a contact form or the Provide feedback form in the iOS app), we collect the content of that message, your email address, and your account ID.

Information We Generate

  • AI-derived metadata. We use AI services to generate summaries, tags, concept labels, and reading-time estimates from the content you save. We also generate vector embeddings for search.
  • Cross-file insights. We derive emergent concepts ("Map of Content" files) across your saves to surface patterns in your reading.

Information Collected Automatically

  • Usage analytics. On our marketing site, we use Vercel Analytics, which does not use cookies or track individuals across sites. In the web app, we use PostHog to record product events: pages you view, buttons you click, page performance measurements, and actions such as saving or searching. These events are linked to your account and include your IP address. Our servers send PostHog an event when you act through the iOS app, a browser extension, or a connected AI assistant: for example, when you save, star, tag, move, retitle, highlight, or delete a save, or export or import your library. These server events carry your account ID and details of the action, such as the domain of the page you saved. The iOS app contains no analytics code. We use these events to understand how people use Saive and to find problems, never for advertising. We do not record your sessions.
  • Error reports and diagnostics. When something breaks, Sentry receives a technical report of the error. We remove saved content from these reports before they are sent. From the iOS app and its share extension, Sentry receives crash reports, app-freeze reports, and session counts. These carry the device model, the iOS and app versions, and a random identifier that Sentry creates for each installation of the app. We do not send your account ID or email address to Sentry from the iOS app. Sentry receives the IP address of the device that sends a report and may use it to estimate an approximate location, such as the country or city.
  • Device information. When the iOS app talks to Clerk, our identity provider, it sends the device's identifier for vendor (a random ID that Apple assigns to our apps on your device, which resets when you remove them), the device model, and the iOS version. Clerk uses them to manage your signed-in sessions and protect your account. The iOS app does not use the advertising identifier.
  • Authentication cookies. We use strictly necessary session cookies to keep you signed in. We do not use advertising, retargeting, or third-party tracking cookies.
  • Log data. Our hosting infrastructure may collect standard server logs (IP address, browser type, request timestamps) for security and debugging purposes.
  • Connected assistant records. When you connect an AI assistant to Saive (see section 3), we record which assistant connected, the name it reports, and when it first and last connected.

2. How We Use Your Information

We use your information to:

  • Provide, operate, and maintain the Service
  • Process your saved content through our AI pipeline to generate summaries, tags, concepts, and search embeddings
  • Display your public profile and public saves, if you opt in
  • Let the AI assistants you connect read your library and save to it on your behalf
  • Measure which assistants people connect, so we can see how people find and use Saive
  • Respond to your inquiries and support requests
  • Understand how people use the Service, so we can improve it
  • Detect, prevent, and address technical issues and abuse
  • Comply with legal obligations

We do not use your information for advertising, profiling for ad targeting, or selling to third parties.


3. How We Share Your Information

Service Providers

We share information with third-party service providers solely to operate the Service:

ProviderPurposeData Shared
ClerkAuthentication and session managementEmail, auth identifiers; from the iOS app, the device identifier for vendor, device model, and iOS version
AnthropicAI summarization and taggingSaved URLs, titles, and article text (for processing only)
Voyage AISearch embedding generationArticle text (for processing only)
Cloudflare (R2)Vault file storageSaved content (encrypted at rest)
NeonDatabase (derived index)Metadata, embeddings, account data
VercelWeb hosting; marketing analyticsServer logs; anonymous page-view counts
ResendTransactional emailEmail address, message content
PostHogProduct analyticsWeb app: product events, account ID, IP address. iOS app, extensions, and assistants: server-side events with account ID and action details, such as the saved page's domain
SentryError and crash monitoringError reports, with saved content removed; from the iOS app, crash, freeze, and session reports with device model, versions, a per-install random ID, and the sending IP address
RailwayBackground processing of savesSaved URLs and article text (for processing only)

These providers process data on our behalf under contractual obligations and do not use your data for their own purposes. Each of them provides the same or equal protection of your data as this Privacy Policy states.

AI Assistants You Connect

You can connect an AI assistant, such as ChatGPT, Codex, or Claude, to your Saive account through our MCP server and its sign-in screen. Once you approve the connection, that assistant can read your saves, notes, highlights, and saved article text, and can save new links to your library when you ask it to. Saive sends content to the assistant only in response to requests the assistant makes on your behalf.

The assistant's provider (for example, OpenAI or Anthropic) handles what it receives under its own terms and privacy policy, not this one. These providers are not our service providers: you choose and authorize them, and they act for you.

Saves an assistant makes follow the same rules as your own. They are private by default, and a save filed into a shared folder becomes visible to that folder's audience.

You can end a connection at any time by removing Saive from the assistant. Deleting your Saive account ends every connection and deletes our connection records.

Your Consent to AI Processing

In the iOS app, a screen appears after you sign in and before your library. It says that Saive sends the text and web address of each page you save to two AI companies: Anthropic, which writes a summary of each save and suggests tags, and Voyage AI, which builds the search index. It also says both process your saves for Saive under contract and do not use them for their own purposes, and it links to this policy.

  • Agree and continue records your consent on your account. It covers every device you sign in on and the web app, and it survives a reinstall.
  • Not now signs you out. Saive cannot save pages without these two services.
  • Withdraw consent is in the iOS app under Settings > Account, in the "AI processing" section. Withdrawing clears the stored consent and signs you out. The next time you sign in, the consent screen appears again.
  • Until the app has confirmed your consent with our servers, the iOS share extension does not upload a save. It tells you to open Saive to finish setup.

Sharing With Other People

You can share a folder with a specific person, and other people can follow your public profile or a public folder. What they see depends on the route:

  • A preview, never your full text. A person you share with, or who follows you, sees the save's title, source site and domain, image, short description, a short AI-written summary of what the page is, the date, your name, and the note you attached when you shared it. They never see your saved article text, your highlights, or your personal notes. To read a save inside Saive, they add it to their own library, which captures their own copy.
  • Blocking. Anyone who sees your shares can block you, and you can block anyone who appears in your Shared with me or Following lists. Blocking removes any follow between the two of you in both directions, stops a new follow, and hides each of you from the other in these lists. To undo a block in the iOS app, open Settings > Account > Blocked people. On the web, email support@saive.my.
  • Reporting. On a shared or followed save, a person can report the save or its sharer. They pick a reason (spam, harassment, hateful content, sexual content, violence, illegal content, or other) and may add a note of up to 1,000 characters. A report hides that item from the reporter's lists at once. Each person can file up to 20 reports a day.
  • How reports are handled. Each report goes by email to Saive's moderation inbox, which is staffed by Saive's operator, and appears on an admin review page. We read the report and either hide the save, hide the user, or dismiss it. A hide removes the item from every Shared with me and Following list and from public profile and folder pages for everyone. A dismissal leaves the reporter's own hide in place. We keep reports and blocks until you delete your account, which removes the moderation records tied to you.

Shared Content Layer

When multiple users save the same URL, AI-generated metadata (summary, tags, concepts) may be reused to avoid redundant processing. This sharing is anonymous — no article body text crosses user boundaries, and no user is identified to another user through this mechanism. Aggregate counts (e.g., "N users saved this") are only displayed when N ≥ 5 to prevent re-identification.

Public Profiles and Saves

If you create a public profile and mark individual saves as public, the following becomes visible to anyone: your display name, username, save title, source domain, save date, and original URL. Public pages also show a short description and a short AI-written summary of what the page is. Article bodies, the longer AI summary, highlights, and personal notes are never exposed on public saves.

Legal Requirements

We may disclose your information if required by law, legal process, or governmental request, or to protect the rights, safety, or property of Saive, our users, or the public.


4. Data Storage and Security

  • Vault storage. Your saves are stored as Markdown files in Cloudflare R2 object storage, isolated by your user ID as a key prefix. No other user can access your vault files.
  • Encryption. Data is encrypted in transit (TLS) and at rest (Cloudflare R2 server-side encryption).
  • Index. A PostgreSQL database serves as a derived search index. It is reconstructible from your vault files and does not contain data that doesn't originate from them.
  • Access controls. R2 is accessed server-side only. You never receive raw storage credentials; content is served through application-issued signed URLs.
  • iCloud Drive copy. When iCloud Drive is available on your device, the iOS app writes a Markdown copy of your saves to a Saive folder in your own iCloud Drive (shown as "iCloud vault" in the app's settings). Apple stores that copy under your Apple account, and Apple's privacy policy governs it. We do not receive it.

We implement reasonable administrative, technical, and physical safeguards. However, no method of electronic storage or transmission is 100% secure, and we cannot guarantee absolute security.


5. Data Retention

  • Active accounts. We retain your data for as long as your account is active.
  • Account deletion. When you delete your account, we delete all vault files under your user ID prefix and all associated rows in our database. Shared content records (AI metadata keyed to a URL, not attributable to any individual user) may be retained.
  • Backups. Deleted data may persist in encrypted backups for up to 30 days before being purged.

6. Your Rights

All Users

You may at any time:

  • Access your data by exporting your vault (your saves are portable Markdown files)
  • Correct your data by editing your saves or account information
  • Delete your account and all associated data
  • Withdraw public visibility on any save or your profile
  • Withdraw your consent to AI processing in the iOS app (Settings > Account)

European Economic Area, UK, and Switzerland (GDPR)

If you are in the EEA, UK, or Switzerland, you have additional rights under the General Data Protection Regulation:

  • Legal basis. We process your data on the basis of: (a) contract performance (providing the Service you signed up for), (b) legitimate interest (security, abuse prevention, product improvement), and (c) consent (where applicable, e.g., marketing communications).
  • Right to access. Request a copy of the personal data we hold about you.
  • Right to rectification. Request correction of inaccurate data.
  • Right to erasure. Request deletion of your personal data.
  • Right to restriction. Request that we limit processing of your data.
  • Right to data portability. Receive your data in a structured, machine-readable format. Your vault is already stored as portable Markdown files, which you can export at any time.
  • Right to object. Object to processing based on legitimate interest.
  • Right to withdraw consent. Where processing is based on consent, you may withdraw it at any time.
  • Right to lodge a complaint. You may file a complaint with your local data protection authority.

Data transfers. Your data is processed in North America (Canada and the United States). We rely on Standard Contractual Clauses and our service providers' data processing agreements to ensure adequate protection for international transfers.

California (CCPA/CPRA)

If you are a California resident, the California Consumer Privacy Act provides you with specific rights:

  • Right to know. You may request the categories and specific pieces of personal information we have collected, the sources, the business purposes, and the categories of third parties with whom we share it.
  • Right to delete. You may request deletion of your personal information.
  • Right to correct. You may request correction of inaccurate personal information.
  • Right to opt out of sale/sharing. We do not sell your personal information or share it for cross-context behavioral advertising.
  • Right to non-discrimination. We will not discriminate against you for exercising your CCPA rights.

To exercise any of these rights, contact us at support@saive.my.

Canada (PIPEDA)

As a Canadian organization, we comply with the Personal Information Protection and Electronic Documents Act. You have the right to access, correct, and challenge the accuracy of personal information we hold about you. Contact our privacy officer at support@saive.my.


7. Cookies

We use two kinds of cookies:

  • Session cookie (set by Clerk): Maintains your authenticated session. Expires when you sign out or after the session timeout. Cannot be disabled without breaking sign-in functionality.
  • Analytics identifier (set by PostHog, in the web app only): A cookie and a browser storage entry holding a random ID, so PostHog can group the events from one browser. We do not use it for advertising or to follow you across other sites.

We do not use advertising cookies, tracking pixels, or fingerprinting technologies.


8. Children's Privacy

The Service is not directed to children under 16. We do not knowingly collect personal information from children. If you believe we have collected information from a child, contact us at support@saive.my and we will promptly delete it.


9. Publisher and Copyright

Saive's browser extension and iOS share extension capture web content from pages you have personally accessed and are authorized to view. We respect publisher rights. Publishers who wish to request removal of cached content may contact support@saive.my.


10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of material changes by posting the updated policy on this page and updating the "Last Updated" date. For significant changes, we will provide notice via email or an in-app notification.


11. Contact Us

If you have questions about this Privacy Policy or wish to exercise your privacy rights:

Email: support@saive.my Mail: Saive 2727 Steeles Ave West Unit 103-906 Toronto, Ontario M3J 3G9 Canada


This privacy policy is provided for informational purposes. You should consult a qualified legal professional to ensure it meets all applicable legal requirements for your specific circumstances.

← Back to saive.my
© 2026 saive.myMade in Canada, on the shore of Lake Ontario
AboutFeaturesPricingBlogDocsChrome extensionEdge extensionFirefox extensionContactPrivacyTermshello@saive.my