Privacy Policy

Last updated November 6, 2026. This policy explains how the hosted Currents service collects, uses, and shares information.

1. Scope

The hosted Currents service is operated by Matteo Marjanovic (VAT: IT05179170237), who is responsible for the personal data processing described in this policy. You can contact us at privacy@currents.is.

This policy applies to the hosted Currents web app, iOS and Android apps, browser extension, APIs, appview, and related search and inference infrastructure that we operate. It covers how we obtain and use public AT Protocol records, including records published through other clients. Self-hosted forks and third parties such as your Personal Data Server (PDS), account provider, and linked websites have their own policies for the processing they control.

2. Information we collect

We collect or process the following categories of information:

  • Account and profile data such as your DID, handle, display name, avatar, description, pronouns, website, and related public AT Protocol profile fields.
  • Public content you create or interact with, including images, collections, saves, alt text, captions, notes, source URLs, attribution, and references to source AT Protocol records. We also index public follows and favourited collections linked to your account.
  • Derived metadata used to operate discovery features, including image embeddings, dominant-color palettes, image dimensions, save clustering signals, and collection embeddings. Automated image analysis also produces content scores and labels for moderation, AI-generated content, and discovery-feed filtering.
  • Authentication data needed to keep you signed in, including a signed currents-session cookie in the browser, an equivalent session token kept in your device's secure storage in the mobile apps, and server-side OAuth session records. On iOS, the app also shares authentication data locally with its share extension so you can save without signing in again.
  • Search and interaction data you submit to the service, such as text queries for semantic search, query colors, and collection filters. Free color-search trials store the colors used, your account identifier, and when each trial was used.
  • Account preferences and interaction state stored on our servers, including pinned collections, feed and moderation settings, hidden feed images, saving preferences, and which feature announcements and notifications you have dismissed or seen.
  • Pinterest import information, including the public boards you select, destination collections, source image URLs, progress, errors, and import history. Imports use anonymous Pinterest sessions and do not require your Pinterest password or login cookies.
  • Moderation reports, including the reporter's account identifier, reported content, reason, and review history. If you contact us for support or a privacy request, we also receive your contact details and the information you provide.
  • Request and diagnostic information needed to deliver, secure, and debug the service, such as IP addresses, browser or app information, timestamps, and error details. Infrastructure providers may retain this information in operational or security logs.
  • Local app and browser state, such as your last-used collection, theme, temporary sign-in flow state, and cached content. The extension also stores its save-button settings locally.
  • If you use the browser extension, it may access the current page URL, page title, image URLs or bytes, and Currents session cookie to prepare and create saves. It inspects page images locally to display hover save buttons on enabled sites, including Pinterest by default, and to populate the image picker when you open it. Opening the clipper or selecting an image can also fetch image data and supported source-record metadata. Publishing a save requires your action; local page inspection does not upload your general browsing history to Currents.
  • In the mobile apps, the images you choose to save: pictures you pick from your photo library or capture with your camera. Camera and photo access are used only when you actively select or take an image to save, never in the background.
  • Content shared to the mobile app from other apps (an image or link you send to Currents through the system share sheet), used only to pre-fill a save you choose to create.
  • Subscription and billing data if you become a Supporter. Checkout and billing are handled by Polar, our merchant of record. Depending on the checkout and tax requirements, Polar collects billing contact details, such as your name, email, address and country, and payment information. It may use cookies and process request metadata in the checkout window. We send Polar your DID to associate the subscription with your Currents account. Our subscription database stores your status, plan, relevant dates, and Polar customer and subscription identifiers, not your full payment card details. Billing information may also be available to us through Polar's dashboard or API.
  • Usage analytics collected with Umami on the web and in the mobile apps, including page views and events such as sign-in attempts, feature paywalls, and checkout starts or completions. Events can include the platform, account-provider category, and subscription plan. We do not supply your name, email, DID, or handle as an analytics identifier. Page titles are omitted, search terms and content identifiers are removed from analytics URLs, and external referrers are reduced to their website origin.

Umami uses no analytics cookies, but can group activity using a derived visitor or session identifier based on an IP address, browser information, and a rotating salt. Analytics can include browser, operating system, screen size, language, referral and campaign information, and approximate location derived from the IP address. These records are not necessarily anonymous just because they lack your account identifier.

3. How we use information

We use information to:

  • Authenticate you and maintain your session.
  • Fetch, index, display, and synchronize public AT Protocol content.
  • Provide search, related saves, discovery feeds, and personalization features.
  • Generate technical derivatives like embeddings and image metadata.
  • Synchronize your preferences, follow graph, and library across devices.
  • Run imports, track trial allowances, and provide Supporter access and billing support.
  • Measure feature use, audience size, and sign-in and checkout flows to improve Currents.
  • Detect abuse, secure the service, debug failures, and maintain reliability.
  • Comply with legal obligations and enforce our Terms.

Where EU or UK data protection law applies, we rely on performance of our contract with you for account access and the features you request; our legitimate interests in operating, securing, moderating, and improving the service, including measuring its use; and compliance with legal obligations where applicable. Where processing requires your consent, consent is the relevant legal basis and can be withdrawn. Account identifiers and authentication are necessary for account features; optional profile fields and content are provided at your choice.

4. What is public

Currents is designed around public AT Protocol records. If you publish content through Currents, your profile, images, collections, saves, follows, favourited collections, and related metadata may be visible in Currents, on your PDS, and through other clients or protocol consumers. Unsorted saves on your profile are public too. Content labels we issue can be distributed through public AT Protocol label endpoints.

Search queries, trial ledgers, account settings, pinned collections, hidden feed images, import progress, authentication data, analytics, and the contents of moderation reports are not published as public user records. Moderators can access reports and review data.

5. How we share information

We may share information in the following ways:

  • With the AT Protocol ecosystem and your chosen identity or hosting providers when necessary to authenticate you, fetch records, upload data, or serve public content.
  • With infrastructure providers that host and deliver the service. Our main application, database, and inference services run on Scaleway in the Paris region, and Bunny delivers images through our CDN. Image delivery providers receive the requests needed to serve you content, including network metadata such as your IP address.
  • With the infrastructure hosting our Umami analytics instance, currently served through Netlify, to process the usage analytics described above. This is separate from your Currents account database. See Umami's data documentation.
  • With Polar, our payments provider and merchant of record, when you purchase or manage a Supporter subscription, including your DID and selected plan. Polar processes your billing details and checkout activity under its own privacy policy.
  • With other users and the public when the information is part of public AT Protocol content.
  • If required by law, to protect users or the service, or as part of a reorganization, asset transfer, or similar transaction.

We do not sell personal information or use your Currents profile, saves, or interaction data to serve targeted ads. Analytics is used to understand our own service. Third-party checkout and linked services have their own data practices, as described in their policies.

Providers processing personal data on our behalf must protect it in accordance with this policy and applicable data protection requirements. PDS operators, Polar, and other services may also act independently for processing they control. Public AT Protocol content is accessible worldwide, and third-party services and CDN infrastructure may process information outside the European Economic Area. Contact us for information about the recipients, processing locations, and applicable transfer safeguards.

6. Retention

We retain indexed public content and its search metadata to display saves and provide search and discovery. Removing content from your PDS or deleting an account removes the corresponding live account data as described below; changes may take time to reach indexes and caches. Derived metadata for an image may remain when other users still save that image or it is still used by the discovery system.

OAuth sessions are configured to expire after 90 days or 14 days of inactivity, with cleanup performed when sessions are accessed. Account deletion removes sessions except for one temporarily kept to complete an optional PDS deletion job.

Account preferences, trial colors, and import history are retained until account deletion or removal through an available feature. Completed import history is kept to avoid importing the same images again, including images you later move or delete. Trial colors remain on record after the free allowance is used up, until account deletion.

Currents keeps its subscription records while your account exists and removes them on account deletion. Polar keeps its own billing and transaction records under its retention policy, including any accounting, tax, fraud-prevention, or dispute requirements.

Moderation reports, labels, and review or audit history are not automatically removed by account deletion. They are retained to maintain moderation history, prevent abuse, and handle disputes or legal obligations. Analytics and infrastructure logs are stored separately and follow their configured retention settings; deleting an account does not automatically erase those records. Contact us about retention or deletion of these data.

Routine database backups in our Scaleway backup bucket are configured to expire after 30 days. Account deletion does not edit existing backup copies. Browser and app storage can remain until you clear it or the app replaces it; logging out clears the active local authentication data.

7. Your choices

You can request account deletion from Settings → Account → Delete account. This removes your profile, collections, saves, outgoing follows, favourites, preferences, trial ledger, import history, and Currents' subscription records, and stops indexing your account. Other users' records, such as their follows of your account, favourites, or copies of images, remain theirs. Moderation and audit history is retained as explained above.

By default, your original Currents records remain on your PDS, and signing in again can restore them to Currents. Select the additional option to delete Currents records from your AT Protocol repo if you want those removed too. That deletion runs in the background, can take longer for large libraries or when your PDS limits requests, and requires a working authorization. Signing in again while it runs stops the remaining deletion. It does not delete your AT Protocol account or other apps' records, and cannot erase copies already held by other users or independent services.

The current self-service deletion flow is unavailable while a Supporter subscription still grants access, including a canceled subscription through the end of its paid period. Manage billing under Settings → Subscription. If you need help with deletion, including while a subscription is active, email privacy@currents.is.

  • Review or change your public profile and records through your AT Protocol account.
  • Log out to clear the active Currents session: the cookie on the web, or the stored session token on mobile.
  • Change feed, saving, and moderation preferences in Settings.
  • Clear local browser storage or app data through your device's settings.
  • Web analytics is configured to honor your browser's Do Not Track preference. There is currently no separate in-app analytics switch. Contact us with analytics privacy requests or to object to processing.
  • Avoid posting private, sensitive, or confidential material to Currents.
  • Control the sites where extension hover buttons appear in the extension's settings, or disable the extension through your browser.

8. Your privacy rights

Depending on the law that applies to you, you may request access to, correction of, deletion of, or a portable copy of your personal data, restrict processing, or object to processing based on legitimate interests. Where processing is based on consent, you can withdraw that consent without affecting processing that occurred before withdrawal. Send requests to privacy@currents.is. We may need to verify that you control the relevant account. You can also lodge a complaint with your local data protection authority; in Italy, this is the Garante per la protezione dei dati personali.

9. Children's privacy

Currents is not intended for children under 13 or the higher minimum age required by local law. If you believe a child has provided personal information in violation of this policy, contact us using the method below.

10. Changes to this policy

We may update this policy from time to time. When we do, we will post the revised version here and update the date at the top of the page. Where a change requires notice or consent, we will provide that notice or request consent as required by law. Continued use alone does not replace consent where consent is required.

11. Contact

For privacy questions or requests related to the hosted Currents service, including data deletion requests, email privacy@currents.is. For general product issues, you can also use github.com/matteomarjanovic/currents/issues .

GitHub issues are public. Please use email for personal data or account details.