Privacy Policy

Effective date: November 19, 2026

1. Introduction

Welcome to 4Stash ("we", "our", or "us"). 4Stash is a personal content-saving app that lets you save links, tweets, TikToks, Instagram posts, Reddit threads, Threads posts, and other media so you can revisit them later. This Privacy Policy explains what data we collect, how we use it, and your rights.

Who is responsible. 4Stash is operated by Fady Erian, an individual carrying on business in the Province of Quebec, Canada, who is responsible for the personal information described in this policy. Fady Erian is also the person in charge of the protection of personal information (responsable de la protection des renseignements personnels). Contact: support@4stash.com, for any question, request, or complaint about your personal information.

2. Data We Collect

Account Information

When you sign in with a supported authentication provider or email/password, we receive basic profile information (name, email address, profile photo) from the authentication provider. We store this in Firebase Authentication.

Content You Save

URLs, titles, descriptions, thumbnails, and metadata of the content you choose to save are stored in Firebase Firestore under your account. Firestore Security Rules are configured to limit app access to the signed-in user who owns the data.

Browser Extension and Bookmarklet

The 4Stash browser extension (for Chrome, Edge, Brave, and Firefox) and the "Save to 4Stash" bookmarklet send the address and title of a page to 4Stash only when you click them to save that page. They open the 4Stash save page, which works as described in this policy. The extension stores nothing, reads no other page, and does not track the sites you visit.

Links, Previews, and Original Media

4Stash saves the link and available metadata; it does not download or archive the original photo, video, audio, or post. Rich previews are available on a best-effort basis for YouTube, X, TikTok, Instagram, Facebook, Threads, Reddit, Vimeo, LinkedIn, Spotify, and Anghami. Other public HTTPS links can still be saved with a generic metadata preview. A preview can stop working if the source is removed, made private, requires a login, changes its embed policy, or is unavailable in your region. Your saved link, title, notes, tags, and collections remain available in 4Stash, but access to the original media remains controlled by its source provider.

Source and preview support
SourceFormatsPreview behavior
YouTubeVideos and ShortsPlayer where supported; external YouTube playback when inline playback is unavailable.
XPosts, images and videosProvider widget or saved metadata and an original link. A saved post does not archive its full thread.
InstagramPosts, carousels and ReelsProvider preview when permitted; metadata and an original link remain when it cannot load.
FacebookPosts, videos and ReelsProvider preview or metadata fallback; login and source restrictions may prevent playback.
ThreadsPosts and attached mediaProvider preview or metadata fallback. Android may offer a poster before showing the preview.
TikTokVideos; other formats as linksVideo embed where supported; photo and unsupported formats retain their original link.
RedditPosts and discussionsProvider preview or saved metadata. Media and nested discussion availability depend on Reddit.
Vimeo / SpotifyVideo / audio linksProvider player where supported, with an original-link fallback.
LinkedIn / AnghamiPost / audio linksMetadata card and original-link access; inline playback is not promised.
Other sitesArticles and ordinary linksAvailable title, description and thumbnail, or a useful link-only save.

These are supported preview paths, not a guarantee of source availability. You can correct a saved media format in Edit; carousel counts are shown only when known. Private, deleted, age-gated and regional restrictions remain controlled by the provider.

Threads Content

4Stash supports saving and previewing Threads posts by URL. When you save a Threads post, 4Stash reads the post's public page metadata (title, description, and preview image) and stores it with your save. Previews are displayed with Threads' public embed. We do not require you to connect or log in to a Threads account, and we do not post, like, follow, or take any action on the Threads platform on your behalf.

Usage Data

If you consent, we use Google Analytics to measure predefined page views and automatically collected technical and session information, such as browser or device type, language, approximate location, engagement, and analytics identifiers. We also record a few app events: saving an item (whether it was shared from another app or added in 4Stash, and the platform it came from, such as YouTube, or simply "website"), opening a saved item, and closing a shared item without saving it. We disable automatic page-view reporting and send a predefined route name with a query-free 4Stash page location. Saved URLs, search parameters, URL fragments, page referrers, and item titles are not included in our analytics events. Firebase Authentication may use essential storage for session management.

Service Statistics

To understand whether 4Stash is useful to the people who use it, we calculate totals from dates the service already keeps: when an account was created, when each item was saved, and when each item was first opened. These statistics are counts only (for example, how many people came back during their second week), are visible only to us, never use the content of your saved items, and do not depend on your analytics choice.

Reminders

If you set a reminder on an item, the date and time you chose are stored with that item in your account. The reminder itself is a notification scheduled by the 4Stash app on your Android phone; it is not sent through our servers or any notification service. The app asks for permission to show notifications the first time you set a reminder, and you can turn notifications or "Alarms & reminders" off at any time in Android settings. A reminder is removed from the item once it has rung.

Data Stored on Your Device

The app keeps some data in your browser or on your device so it works smoothly: your sign-in session, your analytics choice, pinned and recent collections, and cached preview images. Clearing the app's or site's data removes it. Your library itself is stored in your 4Stash account.

Advertising Data

The Android app may show clearly labeled Google AdMob ads: an ad card in your library after every six saved posts or collections, styled like the cards around it, and a banner while you read an eligible public 4Stash Learn guide. Google Mobile Ads and Google's consent tools may process device identifiers (including the advertising ID), IP address, general device information, ad interactions, consent choices, and diagnostics according to your region and choices. To place an ad card, the app uses only the card's position and size on the screen and the app's colours. 4Stash does not give Google your saved URLs, titles, notes, tags, searches, collection names, email, or account ID, and does not use them to choose ads. Authentication, settings, save, share, dialog, and error screens do not contain ads. The website and the iPhone app do not show ads.

In Canada, ads are non-personalized by default: functions that could profile you for advertising are off unless you choose to turn them on. Development builds show Google's labeled test ads.

AI Organization Data

When AI suggestions run, 4Stash sends the saved item's title, description or content, URL, source platform, existing tag names, and non-system collection names to our backend. Our backend first sends this information to OpenRouter, which routes the request to the configured AI model. If that is unavailable, it may send the same information to Google Gemini. The returned tags and collection suggestions are used to help organize your content.

3. How We Use Your Data

  • To authenticate you and maintain your session
  • To store and retrieve the content you save
  • If you opt in, to understand overall app usage and improve the product experience
  • To fetch metadata (title, description, preview image) for URLs you save. Saved URLs may be sent to our metadata endpoints and to the third-party sites or services needed to retrieve previews.
  • To display rich previews of Threads posts using the public Threads embed API
  • To generate tags and collection suggestions using OpenRouter, with Google Gemini as a fallback provider
  • To request clearly labeled Google AdMob ads in the Android app's library and on eligible Learn guides, only when the app's ad setting and your Google consent choices allow it
  • To investigate abuse reports and, when the law requires it, to preserve and disclose information to the authorities, for example when reporting suspected child sexual exploitation to Cybertip.ca

We do not sell or rent your data.

4. Third-Party Services

  • Firebase (Google) — Authentication and database hosting. Firebase Privacy
  • Google Analytics — Used to understand app usage and improve product performance. Google Analytics Privacy
  • Google Mobile Ads and User Messaging Platform — Used in the Android app for consent choices, ad cards in the library, and a banner on eligible public Learn guides. How Google uses information
  • Meta Threads Embed API — Used to render Threads post previews when you save a Threads URL. No account connection or login is required. Meta Privacy
  • Google Gemini — Fallback processor for AI-generated tag and collection suggestions when OpenRouter is unavailable. Item and library context described above is included in the request. Google Privacy Policy
  • OpenRouter — Primary processor for AI-generated suggestions. OpenRouter may route the request to the configured model provider. OpenRouter Privacy Policy
  • Content and preview providers — To retrieve metadata or display a preview, a saved URL may be sent to its destination site, platform APIs (such as Meta's oEmbed endpoints), or Jina AI's reader service. Loading an embedded preview can connect your device directly to services such as YouTube, X, TikTok, Meta services, Reddit, Vimeo, Spotify, or Anghami. Those providers may receive network information such as your IP address and user agent and apply their own privacy policies. In the Android and iOS apps, the page of a Facebook, Instagram, or Threads link is read from your phone first, so Meta sees your phone's IP address; the request identifies itself as 4StashBot. Our server, which identifies itself to Meta the same way, reads the page if that fails, follows share links when looking for duplicates, and downloads the preview picture so it can be shown.
  • DiceBear — Generates profile avatars using a pseudonymous Firebase user ID as the image seed. DiceBear Privacy Policy

5. Data Retention

Your saved content and account data are retained while your account exists. A successful account deletion removes your authentication account, profile, saved items, collections, collection-name claims, and collection-cleanup records. A minimal deletion-barrier tombstone containing your Firebase user ID, deletion status, and update timestamp is retained to prevent future writes under that deleted account ID. It does not contain saved URLs, item content, your email address, or collection names. To prevent abuse, our servers also keep short-lived request counters that are identified only by a one-way hash and contain no saved content.

You can download a JSON copy of your collections, active and archived saves, URLs, titles, personal notes, source descriptions, tags, and timestamps from Settings > Backup. You can restore a version 1 JSON export there after reviewing its record counts. Restore adds missing library records to the signed-in account, keeps existing records, reuses matching collection names, and does not import credentials or account settings. Keep the downloaded file in a secure place. Contact support if you need help obtaining your data before deleting your account.

When the law requires us to preserve data connected to an abuse report, we keep that data for the period the law requires, even if the account is deleted, and then delete it.

6. Security

Data is protected by Firebase Authentication for account access, Firestore Security Rules for user-owned documents, HTTPS/TLS in transit, Google-managed encryption at rest, and Firebase/GCP IAM controls for administrative access. These controls help protect your data from other app users, but they are not zero-knowledge or end-to-end encryption. Authorized Firebase/GCP administrators may technically view user data in Firebase or GCP tools when there is a controlled support, security, operational, or legal need.

4Stash no longer offers new client-side passphrase encryption setup. If your account has legacy encrypted saved items, your old passphrase is used only in your browser to decrypt those items and migrate them into the current Firebase-protected model. The legacy passphrase is not sent to or stored by 4Stash.

We may add additional server-managed field encryption in the future, but that is not part of the current Service unless we announce it in an updated policy or product notice.

Where Your Data Is Stored

Your library (saved items, collections, tags, and notes) and your profile are stored in Google Cloud Firestore in Google's Montréal, Quebec data center (region northamerica-northeast1). Some processing happens outside Quebec, mainly in the United States: sign-in (Firebase Authentication), our server functions that fetch previews and run AI suggestions, the AI providers (OpenRouter and the model providers it routes to, and Google Gemini), Jina AI, DiceBear avatars, and, if you opt in, Google Analytics. Before using these providers, we considered the sensitivity of the information, the purposes, and the protections these providers offer, and concluded that your information is adequately protected. You can ask us for more information at support@4stash.com.

7. Children's Privacy

You must be at least 16 years old to use 4Stash. The Service is not directed to children, and we do not knowingly collect personal information from anyone under 16. In Quebec, personal information about a minor under 14 may not be collected without the consent of the person having parental authority or the tutor. If we learn that we hold information about a user under 16, we will delete the account. Parents or guardians may contact support@4stash.com.

8. Your Rights

You may request access to, correction of, export of, or deletion of your personal data at any time by contacting us. Signed-in users can permanently delete their account from Settings > Account. If you cannot access the app, use our public account deletion request page.

You can turn usage analytics on or off at any time in Settings > Privacy. You can export your library at any time from Settings > Backup.

We respond to requests in writing within 30 days. If you are not satisfied with our answer, you may file a complaint with the Commission d'accès à l'information du Québec (www.cai.gouv.qc.ca) or, where applicable, your local data protection authority.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with a new effective date. If a change is significant (for example, a new purpose or a new category of recipient), we will notify you by email or in the app before it takes effect, and ask for your consent again where the law requires it.

10. Contact

If you have questions about this Privacy Policy, please email us at support@4stash.com.