Privacy policy

SnapLift is built with a simple goal: avoid collecting data we do not need. This page explains what the public marketing site does, and what our app backend may process or store when you use SnapLift on iPhone. If something here does not match how you experience the product, contact us and we will correct it.

Marketing website (this site)

This site is static content. We do not offer accounts or forms here. Whoever hosts the site may process ordinary technical data needed to load pages (such as IP address, user agent, and request metadata) as part of normal delivery. This site does not set analytics cookies by default.

SnapLift app and API

When you use the iOS app, requests go to our backend. Operating the service requires some account and usage records; we keep that scope as narrow as we can.

We do not save or retain your uploaded content or generated images as a lasting archive on our servers. What you send is used to run that request (and may sit in short-lived temporary storage only while a queued job finishes), then it is removed from our systems. Outputs from the model are delivered for you to use in the app; we do not keep a copy for our own gallery, training, or marketing. What stays on your phone is under your control (for example Camera Roll or iCloud if you save it there).

What we may store

• Account and identity. We store technical identifiers needed to recognize your account (for example sign-in provider user IDs). We do not store email addresses. If you use an anonymous flow, we may store a stable anonymous identifier you supply so points and sessions can be tied together.
• Points and usage. We store point balances, holds for in-flight jobs, and ledger entries for usage accounting (route, points, timestamps, and limited technical metadata such as reconciliation references).
• Subscriptions. Paid plans are handled by Apple (App Store). Apple processes payment card data and personal billing details; we do not receive your full payment credentials on our servers. We store only the subscription and transaction identifiers Apple provides to the app (for example product and subscription IDs, transaction references, and renewal state) so we can confirm entitlement and grant included points. For privacy practices related to your Apple ID and purchases, see Apple's privacy policy.
• Async jobs (temporary only). For queued image work, payloads that include your uploaded material may sit in temporary storage until that job completes, then they are deleted. This is not long-term retention. Job status is short-lived and tied to finishing the request.
• Optional debug logging. If a client explicitly enables debug mode, we may store a copy of the request payload to diagnose issues. Normal use does not enable this and does not retain your uploads or generated images for product storage.

What we do not use this site for

We do not sell your personal data. We do not use the marketing site to fingerprint visitors for advertising.

Third parties and AI (Poe and direct providers)

The iOS app shows an in-app disclosure the first time you open a shoot or an asset form, and asks you to agree before any content is sent for AI processing. You can review the same information later from Settings. Tapping Agree records your choice on the device until you reset it in Settings (testing) or reinstall; without consent, AI routes are not used.

When you use AI generation or refinement in SnapLift, our backend sends the data needed to fulfill that request to an AI provider. In many cases, this is Poe (Quora's Poe API, operated by Quora, Inc.), which may route requests to underlying model providers according to its service. In other cases, when you select Google direct models, our backend sends the request directly to Google (rather than through Poe) to run the generation.

Categories of information that may be transmitted for a typical image job include: reference and composition images you provide in the app, text you enter (creative notes, prompts, and related fields), technical request metadata needed to run the job (such as model identifiers and parameters), and identifiers our API uses to authenticate the request and apply points or subscription entitlement. The AI provider you use (Poe, Google direct, and any upstream model provider Poe selects) processes that information under its own terms and privacy policies. For Poe's disclosures, see Poe's privacy policy (opens in a new tab).

On our side, we still do not retain your creative uploads or generated images as a lasting archive after the request path completes, except as noted for temporary job handling or optional debug. Subscriptions are billed and managed by Apple. Other vendors may host infrastructure we use (for example cloud hosting); they process data under their own terms. We describe here what we intend to hold on our side, not every subprocess on the network path.

Retention and your choices

We retain account identifiers, points, usage ledgers, and subscription identifiers only as long as needed to run the service and meet legal obligations. We do not retain your creative uploads or generated images as an ongoing library on our servers. You can ask for access, correction, or deletion of personal data associated with your account by contacting us. Some records may need to be kept for fraud prevention, accounting, or legal compliance.

Children

SnapLift is not directed at children under 13 (or the minimum age in your region). We do not knowingly collect personal data from children.

Changes

We may update this policy when the product or the law changes. The "Last updated" date at the top will change when we do.

Contact

Questions or privacy requests: Discord (opens in a new tab). This is the only channel we use for SnapLift support and inquiries.