REVIEW DRAFT — not effective or published. Draft mine.privacy.draft.2026-10-03.1, prepared September 23, 2026 and revised October 3, 2026. Unresolved items must be completed before the relevant collection or public release; this is not a finished launch notice.
Who is responsible
Solsk, Inc. provides Mine and is the intended controller of personal information used to operate it. I’m Brandon, the person building Mine. Contact me at brandon@solsk.app for privacy questions or requests.
Unresolved before publication: legal contact address; applicable registration, representative, privacy officer or grievance contact; countries actually served. Those details cannot be inferred from an email address or a language setting.
What stays on your device
Mine saves your preferences, saved pages, browsing history, downloads and any earlier on-device history on your iPhone. Your Mine account (Sign in with Apple, orders, wallet and collection) is kept by Mine’s server, hosted by Supabase in the United States.
This does not mean every action is offline. Opening a merchant website, loading a remote product image, downloading a file, following an external link or sending support email contacts the relevant external service. Those services may receive network information such as an IP address and may handle other information you choose to provide.
Data used by the current app
| Information | Why it is used | Current handling |
|---|---|---|
| Display name, chosen profile-cover photograph, appearance, language, region format, sound, motion, haptics and other local preferences | Personalize the app and remember your choices | Saved on the device. A selected cover photograph is resized and saved as a local image; cloud profile-photo storage is not active. Earlier saved avatar preferences may remain, but the redesigned editor no longer offers avatar choices. |
| Saved pages, website addresses, page titles and browsing history | Return to stores and saved pages | Device storage. The current history list keeps up to 80 entries; this is a list limit, not a time-based retention promise. |
| Merchant cookies and website storage | Let real websites load and maintain their sessions and carts | WebKit’s website storage on the device; the merchant and its providers also process website visits under their own policies. |
| Product descriptions, options, quantities, prices, currency and source links; bag and virtual purchase records | Review a product or cart and remember the simulation | On-device storage and account-bound caches, where used. Importing is distinct from submitting a real merchant order. |
| Product photos, model files and opening progress | Display representations and restore the local experience | Device files/caches where available. Loading remote imagery contacts the image host. This does not establish a live generation service. |
| Files you choose to download, their names, source URLs, dates and transfer status | Keep and manage downloads | Device downloads and, after a recovery action, separate preserved copies. Files shared to another app become subject to that destination’s handling. |
| Device app-lock setting and authentication result | Require device authentication when returning to Mine | Apple’s system handles Face ID, Touch ID or passcode verification. Mine uses the result, not biometric templates or your passcode. |
| Support emails and attachments you send | Answer your request and investigate a reported problem | Received through the support email service. The provider, handling locations and retention schedule need confirmation before publication. |
Local files are not all interchangeable. Earlier on-device history, browser data and merchant downloads can remain separate from account-scoped caches. Clearing one category does not necessarily clear another. Some files may also be included in an Apple device backup according to your settings and the file’s configuration; a blanket claim that all Mine data is excluded from backups would be inaccurate.
Account data
For the intended release, Sign in with Apple will support a Mine account and synchronized progress. Current sign-in source requests neither your name nor your email from Apple. It prepares an Apple account identifier and credential token for account verification, with verified session metadata in the device Keychain. This describes the designed flow, not a successful live sign-in.
The planned server records include account identity and eligibility, account preferences, the once-only starter and earned-wallet ledger, simulated orders/installments/receipts, fulfillment, collections, private progression, command-recovery records and relevant permission/policy receipts. They are intended to provide and secure the account, avoid duplicate operations and restore your own progress across devices. Private progression is not a public leaderboard.
Selected cart evidence may include merchant/source identity, product/variant identifiers, selected options, quantities, monetary text and timestamps. When you tap Pay with Mine on a store page, Mine’s server sends that page’s visible text (with email addresses, phone numbers and card-like numbers removed first), a screenshot of your screen, and the page address (without its query), title and product link paths to OpenAI, only to read the cart: items, options, quantities, prices, discounts and charges. A screenshot cannot be redacted and shows whatever is on screen, including what you have typed into visible fields. Mine does not keep the page text or the screenshot; it keeps the reviewed cart in your account and a reading record (the AI’s answer and fingerprints of the text and screenshot) marked to expire after 30 days. The AI-use notice has the details.
Unresolved before activation: the actual fields collected in the release; approved Mine-only Supabase services and project; hosting and processing regions; service-provider agreements; purposes and legal bases; verification and abuse controls; account access and retention schedules. Source schemas are not permission to collect every field they allow.
Optional uses and permissions
By creating an account and using Pay with Mine, you agree to the cart reading described above. You can turn AI cart reading off at any time in Privacy & data; after that, Pay with Mine cannot read carts. Creating an account or acknowledging this policy does not enroll you in research, marketing, optional analytics or tracking. No advertising SDK, connected product-analytics program or research program is active in the inspected development source. The initial release is intended to have no advertising or subscriptions.
Product generation must have its own understandable choice before a relevant external submission. A later research program would require its own specific explanation and enrollment; it must not treat ordinary simulated browsing or a virtual purchase as a declared intention to buy something in real life.
Notifications, camera, microphone, photos and location, if a feature requests them, use the appropriate device permission and contextual explanation. A merchant page may request camera or microphone access within the browser; that is not a general permission for Mine to use those inputs. Planned food-delivery maps do not establish that Mine currently collects your location. System permissions can be managed in iPhone Settings.
Recipients and international handling
Current external recipients depend on what you choose to do: merchant websites and their providers, remote image/file hosts, a destination you share to, the support email service, OpenAI (through Mine’s server, when you tap Pay with Mine) and Supabase (account services). Apple handles system services such as device authentication. These independent services may have their own privacy policies.
Mine’s account and application services are hosted by Supabase in the United States. When you use Pay with Mine, OpenAI receives the page text and screenshot described above through Mine’s server. Mine sends these requests with store: false; that setting alone is not a promise of zero retention by OpenAI, and OpenAI’s processing countries and transfer safeguards are still being confirmed. A consumer product-generation provider has not been finalized or activated; developer preparation for a provider is not a live integration.
Before collection begins, the effective policy and relevant contextual notice must identify actual recipients, processing/storage locations, retention and any applicable international-transfer safeguard, including how to obtain further information. None of those arrangements is confirmed by this draft.
If disclosure is required by law or needed to address a substantiated security or rights issue, the applicable purpose, lawful authority and record handling must be assessed. There is no general permission here to sell personal information or disclose it for unrelated purposes. Any later business transfer involving user data requires its own lawful basis, protections and appropriate notice; no such transfer is currently being announced.
Retention and deletion
Local preferences and earlier on-device history generally remain until changed or removed by available controls; caches may be replaced, and browsing history has the entry limit described above. Downloads and preserved recovery copies have separate removal controls. A completed browser-data clear may be followed by fresh website storage when the page reloads.
Deleting the app is not the same as deleting a future account, files you exported or shared, an Apple backup, merchant records or support correspondence. Keychain data and different backup types also need their own lifecycle treatment. Do not rely on uninstalling as a universal erasure instruction.
No final server retention schedule is approved. Durations or criteria still need to be specified for account/ledger records, cart evidence, permission and agreement records, support messages, security/abuse records, temporary exports, deletion/recovery markers, provider-held data and backups. Pay with Mine page text and screenshots are not kept by Mine; cart reading records are marked to expire after 30 days, but automatic removal of expired records is not yet in place. The deletion work is incomplete, including provider and backup verification. This draft does not promise instant erasure or completed account deletion.
The effective policy must explain what is removed, what lawfully remains, why, for how long and what happens to backup copies. Any record retained to prevent a duplicate starter or abuse needs a specific lawful purpose and a bounded retention decision, not an undisclosed indefinite record.
Your choices and requests
You can change local preferences, remove saved pages/history and manage downloads using the controls available in the build. See Support and account-data help for distinctions and limitations.
Depending on where you live and the information involved, privacy law may give you rights to access, correct, delete, obtain or transfer a copy, restrict use, object to processing, or withdraw consent. Where an applicable right to object exists, you may object by emailing me. Withdrawal does not undo processing that was lawful before withdrawal. Applicable law determines exceptions and response deadlines; this draft does not set a substitute deadline.
Send privacy requests to brandon@solsk.app. Explain the request and the build or account concerned. Do not email passwords, Apple sign-in codes or payment credentials. I may need proportionate information to establish that a request concerns your data. I will not ask you to give me your Apple password. You may also complain to the relevant data-protection authority; local authority contacts and any required request-appeal or grievance process must be added for the actual launch territories.
Before connected accounts launch: publish the working in-app deletion and export/request routes, account-verification approach, withdrawal controls and contact-handling process. The current code does not establish a completed online export or deletion service.
Adults, security and policy changes
Mine is intended for adults 18 or older, subject to any higher local requirement. If you believe a child has provided personal information to Mine, contact me. Age declarations and Apple sign-in do not replace additional age-assurance measures where required.
The source uses protections such as system authentication, account-bound records and selected protected local files. No system can guarantee absolute security, and this draft does not claim end-to-end encryption, a security certification or independently verified operation.
The effective policy will have a version and date, accessible before account entry and from the app and website. Material changes must be explained, and fresh permission obtained where required. New wording does not override a choice you made in Privacy & data; processing that depends on a revised policy starts only after you accept that revision (for example by continuing to Mine).