Sift Privacy Policy — mindgameapps

Last updated: 7 September 2026

This policy covers Sift by mindgameapps. For questions or a privacy request, email s.m.aliabidy@gmail.com. Sift is preparing for its first public release; this page describes the local app and its connected account, AI and Apple subscription features.

Your local library

Links, thoughts, comments, saved AI findings, preferences and completion information are stored on your device. Screenshots you choose are copied into the app’s private storage. Selecting an image does not give Sift permission to upload your entire photo library.

You can capture and browse locally without an account. Signing in does not synchronize or back up your library to the cloud. Local saves remain on the device after sign-out or account deletion. The library uses the app sandbox and device protections; it is not a separately encrypted vault. Avoid saving passwords, payment details or content that needs stronger confidentiality protections.

Accounts

Registration sends your email address, password and display name to Supabase Auth to create and secure your account. We use the account identifier to provide AI access, verify trial eligibility, associate subscriptions and respond to account requests. Confirmation and recovery emails support account security. Native session credentials use secure platform storage; browser sessions use browser storage.

Optional AI processing

In the current app, Enrich with AI starts off, including after sign-in or an upgrade. Selecting it opens a disclosure when you save; you must choose Send to Google Gemini before this item is sent for analysis. Choosing Keep local, going back or dismissing the disclosure does not authorize sending the item.

Permission is recorded on your device for the signed-in account and that version of the save. It covers retries of unchanged content, not your whole library or future saves. Older queued items without matching permission wait for review. Requests from older app versions that do not include the Google-specific consent confirmation are rejected; update the app to use AI.

With AI enabled and confirmed, the selected URL or thought, selected screenshot and filename where applicable, optional comment, item identifier and revision, locale and timezone are sent to Sift’s backend on Supabase. The backend sends the content needed for analysis, including locale and timezone, to Google Gemini. For a public link, Gemini’s URL context tool is asked to retrieve the submitted page; Sift requires successful retrieval evidence for that page before accepting a summary. The current integration does not use Google Search grounding. The AI request does not intentionally include your account email or display name, but anything personal visible in your selected content or comment can be included.

Sift stores the structured AI result and job information in Supabase to return results reliably, retry requests and meter usage. A result may contain details derived from the original content. This is separate from the local library: marking a local save done does not delete its server-side AI job. The current AI job tables do not store a separate uploaded screenshot file.

Sift uses Google’s paid Gemini API service for customer AI processing. Under Google’s paid-service terms, prompts and responses are not used to improve Google’s products, but Google retains limited records for safety, security and legal purposes. Sift sends a single analysis request without creating a stored conversation, uploaded Files API object or explicit context cache; this does not mean zero provider retention. Do not send confidential information or another person’s data unless you have permission and understand this processing.

Apple purchases and the no-card trial

Apple processes paid subscriptions and payment details. Sift receives signed transaction identifiers, product and subscription status, and dates needed to verify Pro access, restore purchases and handle renewal or revocation. We do not collect your payment-card details.

The separate 7-day Sift trial requires an eligible verified account and no payment card. To prevent repeat trial redemption, the backend keeps a protected hash derived from your normalized verified email and the trial grant time even after account deletion. The hash is not used as a mailing list, but it still serves as a retained identifier for eligibility checks.

Notifications, diagnostics and support

The optional weekend snapshot is scheduled locally for Saturday at 9:00 AM in your device timezone. Notification permissions and the in-app setting control it. Device settings may show the notification on a lock screen. The app does not require an advertising or analytics SDK for its current features.

Connected services process technical request information needed to deliver, secure and troubleshoot the service. Sift’s application error logs record limited operational fields such as request identifier, route, error code and duration; hosting and service providers can maintain their own operational records. If you email support, your address and message are used to investigate and respond. Do not send passwords or verification codes.

Service providers and external links

Supabase supplies authentication, backend execution and database storage; Google Gemini supplies enabled AI analysis; Apple supplies App Store billing. These services can process information in countries other than your own. Their roles and applicable service terms differ; our policy explains Sift’s use of them.

Opening a saved link takes you to a third-party website whose own privacy practices apply.

Retention and deletion

Local saves remain until removed from the app or device. Account-linked profiles, AI jobs and results, usage records and active subscription bindings are removed when account deletion completes. The current service has no automatic age-based deletion for AI results while an account remains active.

There are exceptions: the trial-eligibility hash and grant time remain to prevent repeated trials, and billing replay-protection events retain provider references and timestamps with their Sift account link removed. These retained records do not currently have a configured automatic expiration. Apple purchase history, copies you exported or shared, device backups, and provider operational records are not erased by Sift’s in-app deletion action. We cannot promise immediate removal from provider backups or logs.

Read Delete account and data for the separate steps. Contact us about access, correction, deletion or other rights available in your location; we may need to verify account ownership before acting. We will explain applicable retention restrictions for your request. We will update this page when Sift’s data practices materially change.