Legal

Privacy Policy

Last updated: September 11, 2026

Rawback ("we", "us", "our") provides an AI-powered platform that helps photographers organize, tag, and share their photo libraries. This Privacy Policy explains what information we collect, how we use it, and the choices you have. Using Rawback does not by itself authorize optional AI data sharing. We request separate permission before enabling that processing.

See our AI processing and data-sharing terms for optional AI benefits, shared data, recipients, and account-wide controls.

1. Information We Collect

We collect information you give us directly, information generated as you use the service, and information from a small number of third parties that help us run Rawback.

Account information

  • Identifiers such as your email address, display name, and profile image.
  • Authentication data when you sign in through Apple, Google, or Adobe, limited to what those providers expose to us.
  • Billing details processed by our payment provider when you subscribe to a paid tier. We do not store full card numbers on our servers.

Photo content you upload

  • The original photo files you upload, including any embedded metadata (EXIF) such as camera, lens, capture time, and GPS coordinates when present.
  • Derived data we generate to power features: thumbnails, perceptual hashes, AI-generated tags, scene descriptions, face detection data (see section 3, Face Recognition and Face Data), and similarity vectors.

Usage and device data

  • Logs of requests to the service (timestamps, IP address, user agent, referrer) used for security, abuse prevention, and debugging.
  • Aggregated product analytics (which features are used, error rates) used to improve the product.
  • Cookies and similar storage used to keep you signed in and remember preferences such as language and theme.

2. How We Use Your Information

  • To operate, secure, and improve the Rawback service.
  • To run AI features only after you explicitly consent to AI data sharing and while your account’s AI features preference is enabled, including automatic tagging, scene recognition, search interpretation, and face grouping. Face grouping is described in detail in section 3, Face Recognition and Face Data.
  • To process payments and manage your subscription, credits, and storage quotas.
  • To communicate with you about your account, billing, security events, and material changes to the service.
  • To comply with legal obligations and to enforce our Terms of Service.

We do not sell your personal information, and we do not use your uploaded photos to train foundation models that we publish to third parties.

AI Features and Your Choices

AI features are off until you explicitly consent, for both new and existing accounts. A previous default-enabled setting is not consent. Before you enable AI, Rawback displays the data categories, recipients, and uses described below, including your active custom endpoint when present. Choose Enable AI to permit sharing, or Not now to continue without AI. Accepting our Terms or this Privacy Policy alone does not enable AI.

We record the accepted disclosure version, acceptance time, and active AI endpoint with your account. These are collected when you confirm the consent screen and are used to enforce your choice across devices, uploads, and background jobs. A changed disclosure or active provider requires renewed consent. An inactive custom endpoint (for example, after losing paid-plan access or removing its key) does not authorize fallback under the old custom-provider consent. Older clients cannot enable AI without completing this disclosure in a supported client.

To stop new AI processing, turn off AI features in Preferences in the iOS app, or Settings → Privacy → Visibility on the web and save. The setting applies to your account across devices and upload methods. It overrides individual AI settings, including face recognition, and custom AI provider settings. Uploading, browsing, manual organization, and ordinary text search remain available.

When off, new AI requests and queued AI work are blocked before processing. Requests already transmitted cannot be recalled. Existing AI results and previously transmitted data are not deleted by this switch. Re-enabling requires reviewing and accepting the disclosure again, then restores normal processing triggers without automatically replaying work skipped while disabled.

Data sent and recipients

Rawback sends the content needed for each enabled feature:

  • OpenAI: photo thumbnails or selected images and editing instructions for analysis, ratings, tags, generation, editing, and profile-photo selection; search text and relevant library vocabulary for search interpretation; conversation messages and relevant library/tool results for the assistant; article text for translation; audio chunks for transcription; and photo descriptions, dates, places, camera information, and previous summaries for recollections and photographer summaries. Content may include people, location information, or other personal information contained in your uploads or messages.
  • Google Gemini: selected images and prompts when a Gemini image-editing feature is used.
  • Tencent Cloud Image Analysis and Identification (IAI): photo thumbnails or face crops, person names, and account-specific face-library identifiers for face detection, grouping, and matching, as detailed below.
  • Stripe AI gateway: requests routed through this gateway include the model input and output and a Stripe customer identifier for attribution and billing. Some calls go directly to the model provider instead. Rawback also operates an OpenAI-compatible proxy used by its processing workers.
  • Your configured AI provider: when you configure your own endpoint or API key, supported requests use that endpoint or key. Its operator receives the request content and its own terms, retention, and security practices apply. Review these before configuring a provider. The AI features switch still blocks new processing.

On supported iOS devices, photo-search interpretation can use Apple's Foundation Models before falling back to the server. Turning AI features off also disables this local interpretation; ordinary text search remains available.

Protection, retention, and deletion

We require third parties processing personal data on our behalf to provide the same or greater protection as described in this policy, including purpose-limited processing, confidentiality, appropriate security safeguards, and assistance with deletion requests. Providers must meet these requirements before receiving personal data; consent does not waive these protections. Provider handling and retention depend on the service, endpoint, and account configuration. OpenAI states that API data is not used for training by default and documents endpoint-specific retention and exceptions in its API data controls. Google distinguishes paid and unpaid service data handling in its Gemini API terms. See also Stripe's privacy policy and Tencent Cloud's data processing and security terms. These policies do not constitute a promise that every provider has zero retention or identical practices.

Rawback retains generated results with the corresponding account or content so you can use them later. Use content, conversation, person, or account deletion controls to remove the associated records. Turning AI off alone does not delete those records, remove provider-side copies, or change retention required by a provider's applicable terms or law. Contact us for help with deletion requests concerning previously transmitted data. We do not promise immediate deletion from provider systems.

3. Face Recognition and Face Data

Rawback includes an optional face recognition feature that groups photos of the same person so you can browse and search your library by the people in it. Face data is sensitive, so we describe how we handle it separately here.

What we collect

After you consent to AI sharing, when both AI features and face recognition are enabled, we automatically detect faces in the photos you upload. This produces:

  • Face detections: the region of each detected face within a photo (a bounding box), together with attribute estimates such as approximate age or expression.
  • Person matches: records linking a detected face to a person you have created, so that photos of the same person can be grouped together.
  • Face crops: cropped images of a face, stored for the people you explicitly create in the People feature.

Why we use it

We use face data solely to organize your own library: grouping photos of the same person, and letting you search and filter your photos by the people in them. We do not use face data for advertising. We do not use it to identify people outside of your account. We do not use it to train models.

Who processes it

Face detection and face matching are performed by Tencent Cloud's face recognition service (Tencent Cloud IAI), acting as our data processor. We send it photo thumbnails so that it can carry out these operations on our instructions. Its handling is governed by the applicable Tencent Cloud processing terms.

Where it is stored

Face detection and person-match records are stored in our database. Cropped face images are stored in our object storage. For each person you create, a face template is stored in a private face library at Tencent Cloud that belongs to your account alone.

Your control

You can turn face recognition off at any time in Settings, both on the web and in the iOS app. When it or the account-wide AI features setting is off, new photos you upload are not sent for face detection or face recognition. Turning it off stops new processing; it does not delete face data that already exists. Use the deletion controls described below to remove that.

Deleting face data

  • Deleting a photo removes the face detections and person-match records derived from it.
  • Deleting a person removes that person's face templates from Tencent Cloud, the stored face crops, and their match records.
  • Deleting your account removes your entire face library from Tencent Cloud, the face crops in our object storage, and the face records in our database.

Retention

We keep face data only for as long as the photo, person, or account it belongs to exists. We do not retain face data independently of them.

4. How We Share Information

We share information only in the following situations:

  • Service providers: infrastructure, storage, CDN, email, payment, and analytics vendors that process data on our behalf under contractual confidentiality and security obligations.
  • People you choose: photos and albums you explicitly share through public links, restricted shares, or collaboration features are delivered to the recipients you designate.
  • Legal requirements: when required by law, subpoena, or to protect the rights, property, or safety of Rawback, our users, or the public.
  • Business transfers: in connection with a merger, acquisition, or sale of assets, in which case we will provide notice before your information is transferred.

5. Data Storage and Security

Your data is stored on infrastructure operated by reputable cloud providers, with encryption in transit (TLS) and at rest where the underlying provider supports it. Access to production systems is limited to authorized personnel and protected by authentication and audit logging. No system is perfectly secure, so we cannot guarantee absolute security; if we become aware of a breach affecting your data, we will notify you in line with applicable law.

6. Data Retention

We retain your account data and uploaded content for as long as your account is active. When you delete content or close your account, we remove the associated data from production systems within a reasonable period and from backups within their normal rotation cycle. We may retain a limited subset of information longer when needed to comply with legal obligations, resolve disputes, or enforce agreements.

7. Your Rights

Depending on where you live, you may have the right to access, correct, export, or delete the personal information we hold about you, to object to or restrict certain processing, and to withdraw consent. You can exercise most of these rights from your account settings, or by contacting us at the address below. We will not discriminate against you for exercising these rights.

8. International Transfers

Rawback is operated globally and your data may be processed in countries other than the one where you live. Where required, we rely on appropriate safeguards such as standard contractual clauses for cross-border transfers.

9. Children

Rawback is not directed to children under 13 (or the equivalent minimum age in your jurisdiction), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us so we can delete it.

10. Cookies

We use a small number of first-party cookies and equivalent local storage to keep you signed in, remember preferences, and protect against abuse. You can clear or block these through your browser, though doing so may break parts of the service that require authentication.

11. Changes to This Policy

We may update this Privacy Policy from time to time. When we make material changes, we will update the date above and, where appropriate, notify you through the product or by email. Your continued use of Rawback after the changes take effect constitutes acceptance of the updated policy.

12. Contact Us

If you have questions about this Privacy Policy or want to exercise your rights, please email us at [email protected].