Privacy Policy

Last updated: June 29, 2026 (aligned to shipping features; planned integrations clearly marked)

Introduction

rmmbrly is a private search engine for everything you save online. This policy describes what data we collect, how we use it, and your rights as a user.

If you have questions about this policy, contact us at privacy@rmmbrly.io.

What we collect

When you use rmmbrly, we collect the following:

Account info

Email address (for authentication)
Display name if you provide one
Account creation timestamp

Your saved content

URLs you save
Notes, highlights, and annotations you create
Photos, PDFs, and video you upload, plus screenshots and files you import
Audio files you import (if applicable)
AI-generated summaries, tags, and topics derived from your content

Files you upload are stored privately and are visible only to you — they are not shared with other users. Before an uploaded file appears in your library it is screened for objectionable content (images via Google Cloud Vision SafeSearch; PDFs by extracting and screening the document's text). Uploaded files are deleted from storage when you delete the item or your account.

Search and usage data

Search queries you make within rmmbrly
Items you open, save, or interact with
Features you use (collections, spaces, highlights, etc.)
General product analytics (events like screen views, button clicks)

Identifiers

Your user ID (a random identifier assigned by our auth system)
Our analytics SDK (PostHog) generates its own random identifier; once you sign in it is associated with your account ID. We do not collect your device's advertising identifier (IDFA) or any hardware device ID.

Purchase information (planned — not yet active)

Not yet available. rmmbrly does not currently sell subscriptions or process payments, and the iOS app ships without in-app purchases. If we introduce paid plans in the future, we will collect your subscription tier and status, and purchase history would be managed by our payment processor (we would not receive or store your card details). We will update this policy and our App Store privacy disclosures before any billing goes live.

Diagnostic data

Crash reports (via Sentry)
Performance data (page load times, error rates)

How we use it

We use your data to:

Operate the service: authenticate you, save and retrieve your content, search your library, generate AI summaries and tags.
Personalize your experience: rank highlights and recommendations based on your activity.
Improve the product: aggregate analytics to understand which features work and which don't. Product analytics are off until you opt in, and you can turn them off again at any time in Profile settings.
Diagnose issues: investigate crashes and errors.

Planned — not yet active. Paid subscriptions and payment processing are not part of the current release. We do not process payments today; if that changes we will update this section first.

We do not use your data to:

Sell to advertisers or data brokers.
Train machine learning models on your saved content.
Share with third parties for purposes other than the service.

Third-party processors

We use the following services to operate rmmbrly. These are processors — they handle data on our behalf and do not use it for their own purposes:

Service	Purpose
Supabase	Database, authentication, file storage, edge functions
OpenRouter	LLM model routing (for AI enrichment)
OpenAI	Text embeddings (semantic search)
Anthropic	LLM (some enrichment flows)
Google Cloud Vision	Content moderation (SafeSearch) of uploaded images
ElevenLabs	Audio processing
Firecrawl	Web page fetching for saved URLs
Sentry	Error and performance monitoring
PostHog	Product analytics (only after you opt in)
Vercel	Web hosting
Stripe (planned)	Payment processing — not active in the current release
RevenueCat (planned)	Subscription management — not active in the current release

Each of these services has its own privacy policy. Your saved content is sent to AI providers only to generate enrichments (tags, summaries) — it is not retained by those providers for training.

Instagram integration (Meta Platforms) — planned

Not yet available — planned. The Instagram account connection described below is not live in the current release. The app does not connect to Instagram, request OAuth access, or read anything from Instagram's servers today. You can already bring in your Instagram saves by uploading your own Instagram data export — see How you can save below. The section that follows describes how the planned account connection would work if and when it ships; we will update this policy before enabling it.

If you choose to connect your Instagram account, rmmbrly uses the Instagram Login API (operated by Meta Platforms, Inc.) to read posts and reels you have authored. We request only the instagram_business_basic scope. We do not request, read, or store posts authored by other Instagram users on your behalf.

What we receive from Meta when you connect:

Your Instagram username and Instagram-assigned user ID.
A long-lived OAuth access token (valid for 60 days, automatically refreshed before expiry).
For posts you save to rmmbrly that you have authored: the post's caption text, media URL, timestamp, and permalink.

How we store and use it:

Access tokens are encrypted at rest using AES-256-GCM with a per-deployment key. They are never returned to the client and never logged in plaintext.
Captions are stored alongside your other saved items and are subject to the AI processing described above.
We do not share Instagram data with advertisers, data brokers, or any third party other than the AI processors listed above.

Disconnecting:

You can disconnect Instagram at any time from Profile → Integrations → Instagram → Disconnect. Disconnecting immediately deletes your access token from our database.
You can also revoke access from Instagram itself at accounts.instagram.com/accounts/manage_access. When you do, Meta sends a deauthorize webhook to rmmbrly which automatically removes your token.
Per Meta's Data Deletion Callback requirements, requesting full data deletion through Instagram's settings will cause rmmbrly to delete your stored Instagram token within 24 hours.

Other connected accounts — planned

Not yet available — planned. Direct account sync for the services below is not live in the current release. The app does not connect to X, Reddit, or YouTube, hold OAuth tokens for them, or sync from their servers today. As with Instagram, you can already import your saves from these services by uploading their data exports — see How you can save. The section below describes how the planned sync would work; we will update this policy before enabling it.

Beyond Instagram (above), you would be able to optionally connect other accounts so rmmbrly syncs items you have saved on those platforms into your library. Each integration is opt-in — nothing is synced unless you connect it.

Account	What we read (your own activity only)
X / Twitter	Your bookmarked posts
Reddit	Your saved posts
YouTube	Your liked videos (the YouTube Data API does not expose the Watch Later playlist, so we sync liked videos)

How we store and use it:

For each connected account we store an OAuth access/refresh token encrypted at rest. Tokens are never returned to the browser and never logged in plaintext.
Synced items (post/video text, captions, media URLs, timestamps, and permalinks) are stored alongside your other saves and are subject to the same AI enrichment described above.
We read only your own saved/bookmarked/liked content. We do not post on your behalf, read your direct messages, or access other users' private content.
You can disconnect any integration at Profile → Integrations → [service] → Disconnect, which deletes the stored token. You can also revoke access from the provider's own account settings.

How you can save (import methods)

You can add items to rmmbrly in several ways. Whichever you use, the resulting item is stored in your library and enriched as described above.

In the app: paste a URL, write a note, or upload a file/screenshot/audio clip.
iOS Share Sheet: share a link or text from another app into rmmbrly.
Bulk import from a data export: upload an export file (JSON, CSV, or HTML) from another service — including your Instagram saved posts, TikTok, X/Twitter bookmarks, YouTube Takeout, Reddit, Pocket, Raindrop.io, Instapaper, or browser bookmarks. The file is parsed in your browser/device and we store only the resulting items (URLs, titles, text). We do not connect to those services or read anything from their servers — you provide the file yourself.
Save by email: if you forward an email to your personal rmmbrly save address, we parse it to create a saved item (subject, body text, and any links it contains). The resulting item is stored in your library; we do not use forwarded email for any purpose other than creating your save.
Browser extension (planned): a one-click browser extension to save the page you're on is planned and is not part of the current release.

Cookies and local storage

rmmbrly is a logged-in product, not an ad-supported one. We use cookies and browser storage only for the minimum needed to keep you signed in, remember your in-app preferences, and understand which features work. We do not set advertising cookies, third-party tracking cookies, or social-media pixels.

Cookie / storage	Set by	Purpose	Retention
`sb-*-auth-token` (and related)	Supabase	Strictly necessary — keeps you signed in across page loads. Without it you would be logged out on every refresh.	Session + refresh window (rotated by Supabase Auth)
`ph_*` cookies + `localStorage` entries	PostHog	Product analytics — feature-funnel and retention metrics, in our own PostHog instance. First-party; no cross-site tracking.	Up to 1 year (PostHog default); reset when you clear browser data
`theme`, `library-view`, and similar UI preferences	rmmbrly (localStorage)	Strictly necessary — remembers your dark/light mode and last-used filters so the UI doesn't reset between visits.	Until you clear browser data

We do not set or allow:

Advertising cookies, retargeting pixels, or programmatic-ad SDKs.
Social-media tracking pixels (Meta Pixel, TikTok Pixel, X Pixel, etc.).
Third-party data brokers or audience-segmentation cookies.

You can clear all rmmbrly cookies and localStorage at any time from your browser's site settings (signing out via Profile → Sign out revokes the auth token server-side as well). On iOS, the app uses native secure storage instead of cookies for the auth session.

Data retention

Your account and content remain in our systems for as long as your account is active.
When you delete your account, we delete your data within 30 days. This includes any files you uploaded — they are removed from file storage as part of account deletion.
Backups may retain copies for up to 90 days.
Aggregate, de-identified analytics may be retained longer.

Your rights

You can:

Access your data: everything you save is visible in your library.
Export your data: use the in-app export feature to download your library as JSON or CSV.
Delete your account: contact us at privacy@rmmbrly.io or use the in-app delete account flow.
Restrict processing: disable optional integrations (sync, enrichment) from your settings.

Children's privacy

rmmbrly is not intended for children under 13. We do not knowingly collect data from children under 13. If you believe a child has provided us with data, contact us at privacy@rmmbrly.io.

rmmbrly's App Store rating is 17+, reflecting the unrestricted web content users can save.

Changes to this policy

We will update this policy when our data practices change. The "Last updated" date at the top reflects the most recent change. We will notify users of material changes via in-app notification or email.

Contact

For privacy questions, requests, or complaints: privacy@rmmbrly.io