Privacy Policy

Last updated: October 20, 2026 · Version 2026-10-20 · Owner: SIFOR STUDIOS SOFTWARE DESIGNING LLC SPC (Abu Dhabi, United Arab Emirates)

This Privacy Policy explains how SIFOR STUDIOS SOFTWARE DESIGNING LLC SPC (Abu Dhabi, United Arab Emirates) (“SIFOR,” “we,” “us,” or “Platform Owner”) collects, uses, processes, and shares information when you use the SIFOR website, AI assistant integrations (including ChatGPT, Gemini, Grok, Claude, and other compatible assistants), and Snackable generator (the “Platform”).

1. Who we are & Platform Owner

SIFOR is a human-discovery and interactive Snackable platform owned and operated by SIFOR STUDIOS SOFTWARE DESIGNING LLC SPC (Abu Dhabi, United Arab Emirates), a company registered in Abu Dhabi, United Arab Emirates, operating in accordance with UAE Federal Decree-Law No. 45 of 2021 regarding the Protection of Personal Data (PDPL) and applicable international privacy standards.

2. What we collect

• Photos you upload — the photos you choose for a Snackable (up to a few per Snackable). They are uploaded to SIFOR storage when you pick them, resized, and shown on your Snackable and profile only if you consent to share them.
• Social handles and links you add — for example your Instagram, X, TikTok or YouTube handle or link. They are shown on your Snackable and profile and used so people and AI agents can find you.
• Public information from the links you give us — your public display name, bio and profile picture. We read it from the public page or a public avatar service to build your profile, and keep a small mirrored copy of the profile picture so it loads fast.
• Text the AI assistant sends us for you — a short hook and reveal line, a display name and style choices. We do not read your assistant conversations: only what you or your assistant explicitly send to SIFOR reaches us.
• Intros and chat — if someone asks for an intro, or you ask someone, we store the request, the shared interest, a short note, your answer, and, after both people say yes, the contact detail each chose to release and any intro chat messages.
• Prompts, files and generated Snackables — text ideas, reference photos and the HTML, art, audio and metadata of Snackables you create. If you share a Snackable publicly, others can see it.
• Likes and comments — hearts and comments you leave on public snackables. Comments may include an optional display name. We store a hashed visitor id (not the raw cookie) so you can unlike or delete your own comment.
• Consent records — when you ticked or un-ticked a consent, what it covered and which version of this wording was on screen. The browser session is stored only as a one-way hash.
• API keys you paste — Ludo.ai and model-provider keys. By default these stay in this browser only (localStorage) and are sent with your build requests so the providers can generate code or art. We do not want your keys as a product database. If you use “Save in this browser” on a self-hosted deploy, keys may also be written to that server’s key store.
• Technical data — IP address, device and browser type, pages requested, timing and error messages that our servers and hosts record to run, secure and debug the Platform. We do not log raw API key values.
• Optional email — if you ask to be notified when a long build finishes, we use that address only for that notice.
• Anonymous analytics (only if you accept) — page views and clicks measured with Google Analytics. See section 5.
• Optional discovery (adults, off unless you opt in) — see section 8A. Nothing in this item is collected from anyone who has not signed in to discovery and made the explicit choices described there. Creating, playing, sharing, commenting on or remixing a Snackable never enrolls you.

3. How we use information and why (legal bases)

Where the EU/UK GDPR or a similar law applies, we only process personal data when we have a legal basis. Here is each purpose and its basis:

• Show your photos, handles and links publicly on your Snackable and profile, and share them with the AI assistant you pick — your consent (the switch you tick). You can withdraw it any time; withdrawing does not affect what was done before.
• Generate, store and deliver your Snackables and run the features you ask for — performance of a contract (the Terms).
• Intros and optional discovery — your consent, given separately and only by adults.
• Anonymous analytics cookies — your consent (the cookie banner).
• Security, fraud and bot checks, abuse reports, fixing errors, enforcing the Terms — our legitimate interests in keeping the Platform safe and working. You can object (section 8).
• Keeping records of your consents and answering legal requests — legal obligation and our legitimate interest in being able to prove what you agreed to.

We do not use your data for advertising or to build advertising profiles, and we do not sell it.

4. Who we share data with

We share only what each service needs, under contracts or terms that limit how they may use it:

• AI assistants you choose (ChatGPT / OpenAI, Grok / xAI, Gemini / Google, Claude / Anthropic and others). When you tap “Create with …” your handles, photo links and instructions go to that assistant. The assistant company is an independent controller of your chat under its own privacy policy.
• Art, animation and audio generation — Ludo.ai, plus model providers you authorize (for example Google Gemini, OpenAI, OpenRouter, Kimi). They process the prompt, images and keys you send under their own terms.
• Hosting and storage — our hosting provider (for example Railway or similar) and object storage (for example Cloudflare R2-compatible storage) process traffic and store files for us as processors.
• Profile picture lookup — a public avatar service (for example unavatar.io) receives the public handle you added so it can return that handle’s public profile picture.
• Email — our email provider (Resend) delivers build notices, sign-in links and introduction emails you ask for.
• Analytics — Google Analytics, only if you accept analytics cookies.
• Fonts — pages load fonts from Google Fonts, which means your IP address is sent to Google when a page loads.
• Other people — what you publish is public. Contact details are shared with someone only after both of you say yes to an intro.
• Authorities and advisers — where the law requires it, or to protect rights, safety and the Platform. If SIFOR is sold or reorganised, data may move to the new owner under this Policy.

5. Cookies and local storage

Strictly necessary (no consent needed):

• sifor_session — keeps your private drafts, consent choices and ownership of your Snackables for this browser.
• sifor_vid — a random visitor id (kept up to 1 year) so likes, comments and play progress work and to stop duplicate counts. It does not identify you by name.
• Sign-in cookie — only if you sign in to discovery.
• Browser storage (localStorage) — your handle, draft social handles, your cookie choice, onboarding state and, if you paste them, your API keys.

Analytics (only with your consent): Google Analytics 4 sets _ga cookies to measure anonymous usage. It is off by default: nothing is sent to Google Analytics until you tap Accept. “No thanks” keeps it off. We also treat your browser’s Global Privacy Control / Do Not Track signal as a “no”. We switch off IP storage, Google signals and ad personalization. Change your mind any time with Cookie settings (also in the page footer and in Settings); choosing “No thanks” removes the analytics cookies.

We do not use advertising or cross-site tracking cookies. Clearing site data in your browser removes locally stored data and keys.

6. Sharing, selling and the public gallery

We do not sell personal information and we do not “share” it for cross-context behavioural advertising (as those terms are defined by California and similar laws). We share data with the providers listed in section 4, and with the public when you publish a Snackable or tick the share-publicly switch. You can unpublish or delete at any time.

7. How long we keep data

• Your Snackables, photos, handles and profile — until you delete them or delete your data.
• Browser keys and storage — until you tap Forget keys or clear storage.
• Unanswered intro requests — expire after 30 days.
• Consent records — while your consent is active, and afterwards only as long as needed to evidence it. They contain no photos, handles or names.
• Server and error logs — only as long as needed for security and operations.
• Analytics — according to Google Analytics retention settings, and only if you accepted.

8. Your choices and rights

• Withdraw consent any time, as easily as you gave it: untick the switch, use Withdraw in the Privacy & Consent Dashboard, or change Cookie settings.
• Access, correct, download, delete your data, and restrict or object to processing based on legitimate interests. The dashboard lets you do this without signup. Anything else: email support@sifor.app.
• Do not paste a key you do not want sent to that provider. Keep Snackables private by not sharing them publicly. Use Forget keys in Studio settings to wipe the browser vault.
• Open the Privacy & Consent Dashboard to inspect your Personal Context Manifest, see which facts came from user-provided sources vs. assistant inferences, control public fields on each Snackable, toggle optional discovery, withdraw any consent receipt, or delete all personal data for your session.

If you are in the EEA, UK or Switzerland (GDPR / UK GDPR / FADP) you also have the rights of portability and to lodge a complaint with your local data protection authority. If you are in California or another US state with a privacy law (CCPA/CPRA and similar) you have the right to know, access, correct, delete and port your data, to opt out of sale or sharing (we do neither), to limit use of sensitive data (we do not use it for inference) and not to be discriminated against for using these rights. If you are in Brazil (LGPD), Canada (PIPEDA and provincial laws), the UAE (PDPL), Australia (Privacy Act), Singapore (PDPA), Japan (APPI), South Korea (PIPA), India (DPDP Act), South Africa (POPIA) or elsewhere you have the equivalent rights your law gives you; we honour them for everyone, wherever you live.

We reply within one month (45 days where US state law applies), and we may ask you to confirm who you are. Authorized agents may act for you with your written permission. Exercising a right is free unless a request is clearly excessive.

8A. Meeting people (optional discovery)

Discovery is a separate, optional feature. It is switched off unless you explicitly opt in, and it only ever involves adults (18+) who sign in or explicitly grant consent.

• Who it is for. Only people who sign in with an email link and then tick each choice themselves. Signing in does not make you discoverable. Nothing is pre-ticked.
• What we store. Your email address (a keyed hash for lookup and an encrypted copy used only to send you sign-in and introduction emails), an optional display name, your 18+ confirmation, a log of the choices you made (what, which version of the wording, when), and for each kind of connection you join: the interests, skills, offers and wants you typed, a collaboration style, an optional short note, which of your items SIFOR may mention in an explanation, and a contact detail you chose to release after a mutual yes (encrypted).
• What we do not use. Health, religion, politics, sexual orientation or gender identity, ethnicity, exact location, age or contact details are removed from what you enter and are never used for matching. We do not read your AI assistant conversations: only what you or your assistant explicitly send appears here, and an assistant cannot enroll you or act on your behalf.
• How matching works. A transparent rule-based comparison of the items two opted-in people typed for the same kind of connection. It never invents people and never claims that two people are destined, compatible or a guaranteed match. A suggestion is only a reason to say hello.
• What other people see. An anonymous suggestion with a plain-language reason. Your answers, name and contact are not shown unless both of you say "interested". Then each of you receives the display name (if you allowed it), note and contact detail the other chose to share, by email. We never give anyone your email address.
• Your controls. Pause, leave a kind of connection, withdraw any choice, block or report someone, download your data, or delete everything, any time on the discovery page. Deleting removes your profile, choices, introductions and email address; the database is overwritten and compacted. We keep only a hashed tombstone (no email, no answers) proving a deletion was carried out. Someone who had said "interested" in you sees only that an introduction is no longer available.
• Retention. Introductions you do not answer expire after 30 days. Everything else stays until you remove it.
• Operators. Administrators see counts and safety reports with pseudonymous ids. They do not see answers, names, emails or contact details.

8B. Personal Context & Data Deletion Scope

When you trigger Delete My Personal Data in the Privacy & Consent Dashboard or via DELETE /api/privacy/data:

• Deleted immediately from primary storage: Your session’s rows in context_fact, context_manifests, consent_receipt, publication_policy, discovery_preference, and snackable in privacy.db; associated snack_drafts, snack_versions, and snack_assets rows in sifor.db; entries in games/registry.json; and local generated asset directories under games/{id}/ on disk. SQLite runs with PRAGMA secure_delete = ON and performs a WAL checkpoint truncation on the primary database files.
• What primary database deletion does not cover:
  • Pseudonymized deletion tombstone: A single personal_data_deleted audit row containing only a one-way SHA-256 hash of the session identifier and item counts (zero fact values or personal content).
  • Operational server logs & infrastructure backups: Standard HTTP access/error logs and automated host volume snapshots are managed by the hosting infrastructure and age out on the operator’s standard log-rotation and backup-retention schedule.
  • Browser & CDN caches: Cached public responses expire according to standard HTTP cache headers; private endpoints send Cache-Control: no-store.
  • External generation providers: If a build invoked third-party APIs (such as OpenAI, Google Gemini, or Ludo.ai) during asset or code generation, those external providers process and retain request data under their own independent privacy policies and retention schedules.

8C. International transfers

SIFOR is run from the United Arab Emirates, and the services in section 4 may process data in other countries, including the United States and the European Union. When data leaves your region we rely on an adequacy decision, the standard contractual clauses approved by the European Commission and the UK addendum, or your consent where the law allows, together with the safeguards described in the provider’s terms.

8D. Automated checks and AI

Snackables are made with the help of AI. Outputs can be wrong or surprising and are not professional advice. SIFOR runs automated checks (for example fake or bot account detection on links, and safety filters). They are used to protect people, not to decide anything with legal or similarly significant effects about you. If a check wrongly filters you out, email support@sifor.app and a person will review it.

8E. Security

We use encryption in transit, hashed identifiers, encrypted contact details, access limits and secure deletion. No system is perfectly secure. If a breach is likely to put you at risk we will tell you and the regulator as the law requires.

9. Children

SIFOR is not for anyone under 16, and we do not knowingly collect personal data from them. If you are 16 or 17, you confirm that you have your parent or guardian’s permission where your local law requires it. Optional discovery (section 8A) is for people aged 18 and over only. If you believe a child has used SIFOR, email support@sifor.app and we will delete the data.

10. Changes

We may update this Policy. The “Last updated” date and version at the top change when we do. If a change affects what you consented to or how your data is used, we will tell you in the product and ask for your consent again where the law requires it.

11. Contact & Data Controller

The Data Controller is SIFOR STUDIOS SOFTWARE DESIGNING LLC SPC (Abu Dhabi, United Arab Emirates). For any privacy question or request, email support@sifor.app or use the Privacy & Consent Dashboard. Where the law requires us to have an EU or UK representative or a Data Protection Officer, you can reach them through the same address. You may also complain to your local data protection authority at any time.