Privacy
Your information, explained.
What SeeSell keeps in cloud services, what stays on your device, and how support and beta testing use information. This policy covers the current iPhone beta and website, not a fully shared or transactional marketplace.
US privacy policy · Version 3 · Effective date:
Version 3 applies to the current iPhone beta and website. Bundled policy copies update with app releases; reading this policy does not record legal acceptance.
Read the proposed beta safety privacy additions. Version 3 below is preserved; these additions need separate approval and publication.
1. Who operates SeeSell
SeeSell is operated by RICHFAR Company, a general partnership doing business as SeeSell. Contact [email protected] for privacy and support inquiries. Contact address: 1224 Mariners Drive, Lathrop, CA 95330.
SeeSell’s intended nationwide United States service is for adults aged 18 or older (18+), with no supervised-minor exception. Before first marketplace access, including guest browsing, SeeSell asks for an adult self-declaration. An explicit confirmation is saved as a local preference on this installation so it is not requested on every launch, including after signing out or changing accounts. It is not sent to the backend or linked to an account. No birth date or ID is collected. Another device or cleared app data requires confirmation again; reinstalling may also require it, while restored device backups can retain the preference. Privacy, support and essential existing-account recovery and deletion access remain available without confirming. The current app does not verify age or residency; it uses no ID check, age estimation or Declared Age Range API.
The website is a public demo catalogue and has no age-confirmation screen. Reading Privacy or Help does not sign you in, submit information or record legal acceptance.
2. Cloud accounts and seller profiles
Accounts: creating an account, signing in or resetting a password sends your email and the credentials needed for that action to Superapp Cloud’s Supabase-backed authentication service. It manages account IDs, authentication and sessions. Saved session and secure recovery credentials use the iPhone Keychain with this-device-only accessibility; passwords are not saved in SeeSell’s local app files.
Seller profile: display name, handle, seller-entered city, biography, account ID and profile update date are saved locally and sent to the cloud profile service. A local edit can succeed while cloud synchronization is pending. City is information you enter, not a GPS reading. Selected profile photos and the optional storefront website link currently remain device-local.
The website’s password-reset page sends a temporary recovery token and new password to the same authentication service over HTTPS. It removes tokens from the address bar and keeps them only in page memory, without saving a browser session or the new password. The website does not create accounts or provide media uploads or delivered messaging.
3. Device-local data and purposes
Recordings, clip audio, voiceovers, captions, text, stickers, editing settings, draft and listing details, pending-post records and posted videos stay on this device for the signed-in account. Posting is installation-local: it does not upload your listing or video to a shared marketplace or share it with other testers. Inbox conversations and item context are account-scoped local demonstrations, not messages delivered to other people.
Saved item IDs, followed seller IDs, sound preference, feed position and one non-transactional checkout selection are stored locally, separately from your account. Cash records are account-scoped local examples, not funds, a payment account or real purchases. Neither the app nor website collects payment details or completes purchases, shipping or payouts.
The current website does not save favorites or checkout selections. It remembers dismissal of the get-app banner in browser local storage, not in your account. Local app metadata backups, safety records, necessary file references and limited technical reports/checkpoints support restoration, editing, troubleshooting and recovery. Reading preferences remember only fixed FAQ topic IDs, not policy acceptance.
Information is used to run account/profile features, protect account access, create and restore local work, remember shopping choices, troubleshoot problems and improve app reliability. SeeSell has no paid promotions or advertising/analytics SDK, and does not use or share user information for advertising, marketing, advertising tracking or data brokerage.
4. Public visibility and independent copies
Cloud access rules permit public reads of available seller-profile fields: display name, handle, city, biography, account ID and profile update date. Profile editing is restricted to the owning account; owner-only editing does not make these fields private. Do not put private or sensitive information in public seller fields.
The current catalogue, reviews, storefront statistics and Inbox include demo content. Local videos, drafts, profile photos/link, shopping choices and demo conversations are not currently shared between devices by SeeSell. Public demo videos on the website are approved catalogue copies, not private drafts or device-created posts.
Independent copies are different: a Photos download, screenshot, email attachment or copy held by another person may remain outside SeeSell’s control. Account deletion cannot erase those copies remotely.
5. Providers, backups and service logs
Superapp Cloud provides Supabase-backed account, authentication/recovery and seller-profile services. The provider confirms daily database backups with seven days retained. It also confirms logs are retained since project creation and are accessible through the project’s agent. Seven-day backup retention is not seven-day log retention.
The service provider confirms that retained service logs include IP addresses and approximate country/city derived from them, user-agent information including app and iOS version, account and session identifiers, and email addresses in sign-in logs. Logs also contain request URLs and query parameters, response codes and timing, server and database errors that can include the failed query, and function runtime and memory information. Request bodies are not logged. These service logs do not contain device identifiers such as IDFA or IDFV, app crash reports, screen views or in-app analytics events; they do record API calls such as sign-in, profile updates and account deletion.
Log entries can be linked to an account and an IP address. They are used only to operate, debug and secure the service, not for analytics, advertising or cross-service tracking. Supabase and Cloudflare, which sits in front of the API, process these logs to operate and protect the service. The provider confirms that logs are not sold or shared for other purposes.
Logs are not anonymous and are not promised to expire when an account is deleted. This policy does not promise a processing location, US-only storage or a verified backup-restore erasure guarantee.
The app bundles its current demo videos. The website serves optimized copies from the same site; website hosting processes requests and ordinary connection information, including IP addresses. User-opened seller websites can navigate to other HTTPS sites in an embedded browser, with their own privacy, cookies and tracking practices. HTTPS-only navigation is not content filtering.
Microsoft 365 Business hosts support email. Apple provides TestFlight beta distribution and reports. These providers process information to supply their services; Apple and Microsoft have their own privacy practices. The website has no analytics scripts, advertising tracking or third-party embeds. SeeSell’s statements about its own data use do not guarantee the practices of third-party websites you choose to visit.
6. Permissions and choices
Camera access supports recording. Microphone access is optional for sound and voiceovers; video-only recording remains available when microphone audio cannot be used. Profile images come from the photo/file you select, not a scan of your whole library. Eligible video downloads request add-only Photos access.
Automatic captions request speech permission and supported on-device recognition, with no server-recognition fallback. Manual captions remain available. Manage permissions in iPhone Settings → Apps → SeeSell. You can browse as a guest, adjust autoplay sound, edit your profile and remove eligible local content. Reading policy/support does not request permissions.
7. Retention and account deletion
Local files remain while available on this installation. Preview storage can be temporary; SeeSell does not synchronize local listing media to cloud storage. Device or operating-system backups may contain local data and follow separate settings and retention. There is no general timed expiry promised for all local records.
Use Profile → Settings → Account → Delete Account and the separate final confirmation for permanent account deletion through the supported process. Opening, rechecking or canceling the screen does not request deletion. Signing out or uninstalling is not deletion of the remote account. Accepted, pending or interrupted is not confirmed completion. The app distinguishes server confirmation from unfinished local cleanup and offers recovery.
The supported process removes the account and cloud seller profile. Verified, accessible account-owned local content is considered for cleanup after server confirmation. Guest saves, follows, preferences and checkout selections are intended to remain. Other accounts’ data, shared or uncertain media, inaccessible local data and independent Photos copies are not treated as exclusively yours to erase.
Account deletion does not promise immediate removal from logs, database backups or independent copies. Database backups follow the provider’s daily/seven-day rotation; logs are retained since project creation. Rotation is not a promise of immediate erasure or a verified guarantee about data restored from backups.
Limited server recovery records retain account/operation IDs, status, dates and hashed recovery credentials, not profile or listing content. Recovery credentials are valid for 30 days after confirmation; this is not proof that stored recovery hashes are erased after 30 days. No scheduled hash-erasure process is established here. ID-only access-blocking records can remain to reject stale sessions. Local recovery can retain necessary file references. Reading this policy is not confirmation that deletion was requested or completed for you.
8. Support and TestFlight information
Emailing [email protected] sends sender information, message text and chosen attachments through your email provider and Microsoft 365 Business. SeeSell uses voluntarily supplied screenshots and technical reports to investigate support and privacy inquiries; it does not request video or audio attachments. Other people have mailbox access or administration rights. Their precise roles, permissions and inquiry handling have not been specified; access is not exclusive to one operator.
No support-email cleanup process is currently set up. No automatic 12-month cleanup or fixed erasure deadline is promised for support emails, attachments or SeeSell’s copies of beta reports. Deleting a visible email does not establish immediate erasure from recoverable items, archives, holds or provider backups. Contact support about removal requests; applicable legal obligations still apply.
For TestFlight testing, Apple shares beta feedback, submitted screenshots, crash logs and related tester/device and technical information with the app provider. These reports may link to a tester’s identity or device; a public invitation link does not make every report anonymous. SeeSell uses feedback and crash reports to investigate issues and improve reliability. It does not have a separate in-app crash-upload SDK or ask you to upload diagnostics from these screens.
Apple separately controls its TestFlight collection and retention. Apple’s published policy describes one-year feedback retention and possible crash/usage retention until bugs are resolved; that is not SeeSell’s own deletion schedule. SeeSell does not share TestFlight personal reports with third parties, including forwarding them into third-party agent tools. SeeSell’s retained copies have no established fixed deletion deadline.
9. Security and privacy requests
Account/profile requests use HTTPS and secure saved credentials use Keychain. Account-scoped storage and recovery checks are designed to prevent mistaken access and cleanup. No system is absolutely secure. Storage warnings may restrict actions; reading policy does not clear them. Never email passwords, reset links, tokens, recovery credentials or identity documents. Redact screenshots before sharing.
Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of information. Email [email protected] with the subject ‘SeeSell privacy request’ and a brief description. Proportionate verification of account control may be needed before information is disclosed or changed. Ask for a safe verification method rather than sending credentials.
Requests can involve legal limitations and information held only on your device. This version has no automated data-export or request tracker, no operational appeals process and no fixed response-time commitment stated here. Any required authorized-agent routes, appeals and response procedures must comply with applicable law; this policy does not remove obligations under applicable law.
10. Children, changes and contact
SeeSell is not intended for anyone under 18. The self-declaration does not establish that underage use is prevented. If you believe a minor has provided information, contact SeeSell without including unnecessary details about the minor.
This is Version 3, effective October 21, 2026. Bundled copies update with app releases. Reading this policy and saving FAQ preferences do not record legal acceptance.
For privacy questions or support, contact SeeSell at [email protected]. Contact address: 1224 Mariners Drive, Lathrop, CA 95330.
Beta safety privacy changes — proposed additions
Draft for owner approval · New collection is not activated
SeeSell’s published Version 3 policy remains the dated public policy. These proposed additions describe the safeguarded beta. They have no assumed effective date and are not a claim of Apple or legal approval. New profile submissions, account blocks, and reports remain server-gated until the operator approves and publishes matching disclosures.
Public profile text is separated from owner-private copies. New and edited display name, handle, city, and bio are submitted as immutable revisions for human review. Only the approved, unsuspended version is publicly readable. The last approved text may stay visible while edits await review. Existing profiles are not automatically approved. Device-created listings, videos, draft artwork, and profile photos are exact-owner-only during this beta. Seller website opening is paused without deleting stored addresses.
If you submit a report, SeeSell collects your account ID, the reason, optional explanation, text already visible to you, seller/content identifiers, and timestamps. Reports about bundled demo content include its catalogue version and content ID. No screenshot, image, video, audio, private file path, password, or token is included. Submission is acknowledged only after the server confirms receipt. Failed forms remain in the current session for explicit retry; they are not silently sent later.
Authenticated seller blocks are stored for that exact signed-in account. Guest hiding is separate and lasts for the current app session only; it is never attributed to the next account. Blocking hides otherwise visible seller content and Follow/Message actions without deleting favorites, follows, checkout references, conversations, or media. Unblocking restores only otherwise eligible content. Blocks last until unblocked or the owning account is deleted.
Only permission-authorized SeeSell moderators can read the private queue, approve or reject profile revisions, handle reports, withdraw public content, or suspend and restore public participation. The operator checks the queue daily and acts on urgent concerns; no fixed public response deadline is promised. Necessary case actions and bounded reasons are recorded. For a mistaken decision or correction, contact [email protected]. Do not forward private reports to third-party agent tools.
Ordinary access to closed report details and case history ends 90 days after authoritative closure, unless a documented necessary safety/legal hold applies. The daily retention task removes expired unheld reports and their case history from the live database; daily scheduling is not instantaneous erasure at the deadline. Expired unheld cases cannot be reopened or given a new hold. Open reports remain while needed. Holds have a restricted reason and are reviewed at least every 30 days; overdue holds retain necessary records but hide case text, identifiers and history until the need is explicitly reviewed. Removing a hold after the deadline removes the report and its case history immediately. An eligible explicit reopening removes the closure date; closing again starts a new server-timed deadline, while repeating Close cannot extend it. The current approved profile, private profile revisions, and their bounded review reasons remain until account deletion; editing or withdrawing public text does not erase older private revisions. Block preferences and access roles have separate purposes.
Account deletion removes profile submissions, the public profile, the moderator role, and owned block preferences using compatible account-linked cascades. Reports needed for case handling may remain until their disclosed deadline; unnecessary reporter/subject account links are removed. Retained visible case text can still identify people. Public suspension is not global Auth-token revocation and does not delete private content or remove Privacy, Support, sign-out, recovery, or account-deletion access.
Cloud storage here means structured text/records in the existing Supabase service, not media uploads. The existing service-log descriptions, project-lifetime log retention, daily database backups retained for seven days, agent access, and separately handled Microsoft 365 support/TestFlight reports remain as disclosed in Version 3. Purging live rows is not proof that backups or service logs were erased. New user content and interaction records are for app functionality and safety—not advertising, sale, or cross-app tracking. Apple privacy answers must be reassessed rather than treating the prior category approval as approval of these new practices.