Legal
Snaza Privacy Policy
What Snaza collects, why, where it goes, how long we keep it and how to use your rights.
Effective date: [Effective date] · Last updated: September 28, 2026
1. Who we are
Snaza is a digital wardrobe app and the website snaza.app. Both are run by Backo, Inc., a Delaware corporation ("Backo", "we", "us"). Backo decides how and why the personal information described in this policy is used, which makes it the controller under European and UK data protection law.
- Postal address: Backo, Inc., [Backo, Inc. mailing address]
- Privacy questions and requests: privacy@snaza.app
- General support: hello@snaza.app
- Safety reports: abuse@snaza.app
- EU representative (GDPR Article 27): [EU representative name and address]
- UK representative (UK GDPR Article 27): [UK representative name and address]
- Data protection officer: Backo has not appointed a data protection officer. privacy@snaza.app reaches the person responsible for privacy at Backo.
2. The short version
- Your wardrobe is stored in your Snaza account so it is there on every device you sign in to. It is private unless you choose to share part of it.
- Photos of you stay on your device. For a try-on, the photo you pick is sent once for processing to OpenAI, and Snaza does not store it. The result comes back to your device only.
- When you add clothes on a plan with AI, the photo you confirm is sent once for processing and Snaza does not store it. Your original photos stay on your device; we keep the clean clothing cover.
- AI requests go through Vercel AI Gateway to OpenAI only to do what you asked. Our AI providers may keep request data for a limited time under their own terms, for example for abuse monitoring. Under their terms, our AI providers do not use your data to train their models.
- We use de-identified usage data to analyse and improve Snaza.
- We do not use face recognition and do not create face templates.
- We do not sell your personal information, share it for advertising or track you across other companies' apps and websites.
- You can delete your account in the app. You have 14 days to change your mind, and we erase your data within 30 days of the request.
3. What this policy covers
This policy covers the Snaza app, links to shares that Snaza users create (for example snaza.app/@handle/name), and the snaza.app website, including its waitlist. It does not cover other companies' websites or services, even when Snaza links to them or you sign in with them. How the website uses cookies and similar technologies is explained in the Cookie Policy.
4. What we collect
| Category | What it includes | Where it comes from |
|---|---|---|
| Account and sign-in | An internal account ID. For Sign in with Apple, a hashed form of your Apple identifier. For Sign in with Google, a hashed form of your Google identifier and the email address Google has verified; if Google shares your name, it is passed to your device to prefill your profile and is not stored on our servers. For email sign-in, your email address, and a password stored only as a salted hash if your account has one. Session credentials, stored hashed | You, Apple, Google |
| Terms acceptance | The versions of the Terms of Use and of this Privacy Policy that applied when you signed in, and when you accepted them | Created when you sign in |
| Handle and sharing profile | Your unique handle, earlier handles for a limited hold period, and any display name you give when you follow a share | You |
| Wardrobe | Clothing covers, item details (such as name, category, color, brand, size, season, price and notes), whether a piece is owned or on your wishlist, looks, day plans and reminder times you chose to sync, and on the Wardrobe plan without AI the photo you choose for each piece | You |
| Care labels | Up to three photos of a garment's care label, the text read from them and your notes | You |
| Family profiles | On a Family plan, the name, relation and color you set for each household member, and their clothing | You |
| AI permission record | That you allowed AI features, which version of the notice you saw, and when | You |
| AI processing records | For each AI request: the feature, model, prompt template and settings, a shortened copy of the prompt with your notes and family names replaced by placeholders, credits, token counts, timing, status, error code and a reference to the result. Never a photo | Created when you use AI features |
| Membership and credits | Plan, renewal and expiry status, product purchased, family flag, monthly credit allowance, purchased credit balance, top-up purchase records and a ledger of credits used. We never see your card details | Apple, RevenueCat |
| Sharing and following | What you shared, its name and address, the type of share and its expiry, the fields you chose to show, the people you invited, who follows your shares (or that an anonymous follower exists) and the shares you follow | You, and people who follow your shares |
| Reports and blocks | Reports you send or that concern you (reason, optional note, basic details about the share or account), accounts you block, and our decisions | You, other users |
| Feedback and support | Messages you send in Feedback, up to five screenshots, and for bug reports your app version, device model, system version, language and recent app activity lines that are redacted on your device before sending | You |
| Privacy requests | Requests to access or delete your data, their dates and status | You |
| Location for weather (optional) | A city you type, or coordinates rounded to two decimal places (about 1 km) with your time zone | You, with permission |
| Security and abuse prevention | Short-lived request counters keyed by your account and by a hash of your network address | Your device's connection |
| Website and waitlist | For the waitlist: your email address, when you joined, the page you joined from, the country your connection came from, the version of the notice shown next to the form and a one-way fingerprint of your network address. For all visitors: aggregate, cookieless visit statistics | You, your browser |
Kept only on your device, never collected by us: your portrait photos for try-on (up to five), try-on and AI sticker results, your profile photo, a name you share through Sign in with Apple, your birth year answer, optional gender, self-description, height and weight, trip plans with their notes and photos, events and to-dos you create in Snaza, laundry lists, and the calendars and Apple Reminders lists you connect. On plans with AI, your original clothing photos also stay on your device (section 6).
We do not ask for, and ask you not to add, sensitive details such as health information, government ID numbers or payment card numbers in notes or feedback.
5. Photos, AI processing and face data
5.1 Adding clothes and studio covers
When you confirm an import, the photo you selected is resized on your device to at most 2,048 pixels on the long side and re-encoded, which removes embedded metadata such as location. It is then sent once for processing, through our server and Vercel AI Gateway, to OpenAI, which identifies the clothing in it and, if you asked for covers, creates a clean image of each piece on its own. Snaza does not store the photo it sends. We keep the clothing cover and the item details in your account. If your connection drops, a finished clothing-only cover is held privately for up to four hours so the app can collect it; that copy is then removed.
5.2 Care labels
When you ask Snaza to read a care label, the one to three label photos you chose are sent the same way to OpenAI, which reads the text and symbols. The label photos, the text that was read and your notes are stored with the garment in your account. Snaza explains only what the label says. It never guesses how to wash a garment from its fabric or appearance.
5.3 Try-on and AI stickers
Try-on and AI stickers use a portrait you saved on your device. When you confirm one, the resized portrait and the clothing images are sent once for processing, through our server and Vercel AI Gateway, to OpenAI. The result is streamed straight back to your device. Neither the portrait nor the result is written to our database, storage, cache or logs. To avoid charging you twice, our server keeps a short receipt made of a request ID from the app, a digest of the clothing details and timing, with no image and nothing computed from an image. Results are saved only on your device, in a folder that belongs to your account, and go to Apple Photos only if you tap Save to Photos.
5.4 We ask before any photo is processed
Before your first import, studio cover, care label or try-on, the app shows one full-screen notice that names OpenAI, explains what is sent and what is kept, and asks for your permission. Choosing Not now sends nothing. We record your choice with the notice version and time. When we change what the notice says about where photos go or what happens to them, we ask again. You can withdraw your permission in Settings, under Privacy & data. Each paid action also shows its credit cost before you confirm it.
5.5 What AI providers keep, and training under their terms
Every AI request is sent through Vercel AI Gateway to OpenAI only to process what you asked for. Snaza does not store the original photos it sends. Our AI providers may keep request data, which can include those photos, for a limited time under their own terms, for example for abuse monitoring. OpenAI's terms also allow it to keep content that its safety systems flag, such as suspected child sexual abuse material, for review. Under their terms, our AI providers do not use your data to train their models. We cannot control how our providers run their own systems, so we rely on these terms, and we will update this policy if a provider's terms change what it does with your data. Snaza does not use your photos to train AI models. Sharing something with other people does not change any of this.
We use de-identified usage data, such as AI processing records that are no longer linked to your account, to analyse and improve Snaza (sections 8 and 11).
5.6 Labels on AI images
Every image Snaza generates (studio covers, look covers, AI stickers and try-ons) carries a machine-readable label in its metadata (the IPTC digital source type for AI-generated media, with "Snaza (AI generated)" as the creator tool) and is marked as AI-generated in the app. When we add this label, the image is re-encoded, and any Content Credentials (C2PA) data supplied by the AI provider is not kept.
5.7 Face data
Snaza does not use face recognition, does not identify anyone in a photo and does not create faceprints, face geometry scans or other biometric identifiers or templates. Depending on where you live, a photo of your face may still be treated as sensitive information, so we ask for your explicit permission before the first try-on, use the photo only to make the image you asked for, and never sell, rent or trade it. Backo does not collect, capture, store or use biometric identifiers or biometric information as those terms are defined by the Illinois Biometric Information Privacy Act, the Texas Capture or Use of Biometric Identifier Act, the Colorado Privacy Act or the Washington My Health My Data Act.
App lock, if you turn it on, uses Face ID, Touch ID or your passcode through iOS. Snaza never receives any biometric data from it.
5.8 Features that are not available
The styling chat, AI outfit recommendations and live video try-on are not available in this version, so no conversation text, recommendation request or video is sent to any AI provider. If we switch one of them on, we will update this policy first and, where the law requires it, ask for your permission.
6. What your plan and membership change
- Plans with AI (Studio and Family). Your original photos of a piece, full outfit photos used to find pieces and photos saved with a look stay on your device. Only the generated clothing covers and care-label photos are backed up to your account. A piece whose cover is not ready yet backs up its details only. Photos that were backed up before this rule applied stay in your account until you remove them.
- Wardrobe plan without AI. There are no generated covers, so the photo you choose for each piece, and photos saved with a look, are backed up to your account, resized to at most 2,048 pixels on the long side and compressed. Choose photos of clothes, not of people.
- If your membership ends. We do not delete anything because a membership ended. Your wardrobe stays readable on your device, and signing in on another device downloads it from your account. You can still delete pieces, plan days, use trips and laundry, sign in, restore purchases, make privacy requests and delete your account. Adding pieces or looks, AI features and syncing new changes to your account need an active membership.
7. Handles, sharing and what others can see
- Private by default. Nobody else sees your wardrobe unless you choose to share part of it. Family profiles are never shared.
- Your handle. Every account has a unique handle. It is part of the address of your shares, and it is shown to people when you share something, invite someone or follow a share without choosing to be anonymous.
- What a share shows. A share shows clothing covers and look covers, with each piece's name, category and color, plus only the fields you switch on (brand, price, size, season or notes). Original photos, portrait photos, care-label photos, wishlist items and family members' pieces are never shown. Links are removed from shared text, and text that fails our filter is left out.
- Who can open a share. A link share (open until you end it, or expiring after the time you chose) can be opened by anyone who has its address, and the address can be passed on. The address is made of your handle and the name of the share (for example snaza.app/@anna/summer), so someone who knows your handle could guess it. Web pages for share links ask search engines not to index them. An invite-only share can be opened only by the Snaza users you added, signed in to their own accounts. For anything you want only specific people to see, use an invite-only share.
- Who follows you. You can see who each share is shared with and who follows it. Someone who follows a link can choose to show you their handle and name, or to follow anonymously, in which case you see only that an anonymous follower exists. People you invite by handle are always visible to you. You can remove any follower at any time.
- When you follow someone. The owner sees your handle and the name you give, unless you follow a link anonymously. When the share ends or the owner removes you, the shared wardrobe disappears from your app.
- Stopping. You can pause or end a share, remove a follower or block an account at any time. We cannot pull back copies that someone saved or screenshotted before you stopped sharing, so share only what you are comfortable with others seeing.
- Reports. If you report something, we do not tell the person you reported who you are, unless the law requires it (a copyright notice, for example, must identify the person making it).
8. Why we use information, and our legal bases
The table gives the legal bases we rely on under the GDPR and UK GDPR. People elsewhere get the same protections in practice.
| Purpose | Information used | Legal basis (EEA and UK) |
|---|---|---|
| Create and secure your account, sign you in and sync your wardrobe | Account, wardrobe, care labels, family profiles | Performance of our contract with you |
| Record which Terms and Privacy Policy you accepted | Terms acceptance | Contract; legitimate interests in being able to show what was agreed |
| Run the AI features you ask for (recognizing clothes, covers, care labels) | Photos you confirm, item details | Contract. We also ask your permission first, as Apple requires |
| Try-on and AI stickers with a photo of you | Your portrait and clothing images, in transit only | Your explicit consent, and contract |
| Charge credits, prevent double charges and manage your membership and top-ups | Membership, credit ledger, purchase records, receipts | Contract; legal obligations for accounting |
| Keep Snaza secure and prevent abuse, fraud and overload | Request counters, hashed network addresses, processing records | Legitimate interests in a safe, working service |
| Handles, sharing and following | Handle, shares, follows, invites | Contract |
| Handle reports, blocks, moderation, notices and legal requests | Reports, blocks, the reported content, decisions | Legal obligations (for example the EU Digital Services Act); legitimate interests in keeping people safe |
| Analyse and improve Snaza using de-identified usage data | De-identified processing records | Legitimate interests. You can object at any time (section 14) |
| Weather for your plans | City or rounded location | Consent through the iOS location permission, and contract |
| Answer feedback and support requests and fix bugs | Feedback, screenshots, diagnostics | Legitimate interests; contract |
| Give you a copy of your data and handle other privacy requests | Privacy requests and the data they cover | Legal obligation |
| Send the one launch email to the waitlist | Waitlist email address | Consent |
| Count website visits in aggregate | Cookieless visit statistics | Consent for visitors in the EEA, UK and Switzerland; legitimate interests elsewhere |
| Prove that an account was erased and stop old handles being taken over | Deletion record, held handle text | Legal obligation; legitimate interests in preventing impersonation |
| Keep accounting and tax records | De-identified credit ledger and purchase records | Legal obligation |
We do not make decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you. Some safety checks are automated: for example, try-on is refused for certain garment types, and shared text is filtered.
9. Who we share information with
9.1 Service providers
These companies process personal information to provide Snaza. Our service providers process it for us, under contract, only to provide Snaza. Apple and Google also act under their own privacy policies when you sign in with them or buy through the App Store (section 9.2). We update this table before a new provider starts processing personal information for us, and tell you about material changes as section 17 describes.
| Provider | What they do for us | Information involved | Location | Their terms |
|---|---|---|---|---|
| Vercel Inc. | Hosts our servers and scheduled jobs; runs Vercel AI Gateway, which passes AI requests to OpenAI; Vercel Blob private storage for wardrobe images, covers, care-label photos and feedback screenshots | All requests from the app, including photos in transit to AI; stored images | United States | Vercel Privacy Policy |
| OpenAI, through Vercel AI Gateway | Recognizes clothing, makes studio and look covers, reads care labels, makes try-ons and AI stickers | Resized photos you confirm, portraits in transit for try-on, clothing descriptions and settings | United States | OpenAI enterprise privacy |
| Neon (a Databricks company) | Hosts our database | Account, wardrobe details and the other records described in section 4 | [Neon database region] | Neon Privacy Policy |
| Cloudflare, Inc. | R2 private storage for wardrobe images, covers, care-label photos and feedback screenshots; hosting of snaza.app; the waitlist database; the Turnstile bot check; cookieless Web Analytics | Stored images, waitlist details, website traffic including network addresses | Cloudflare's global network; stored data in [Cloudflare storage location] | Cloudflare Privacy Policy |
| RevenueCat, Inc. | Tracks subscription and credit purchases made through the App Store | Your Snaza account ID as the app user ID, purchase and subscription records, and the device and app information its software collects | United States | RevenueCat Privacy Policy |
| Resend | Sends sign-in code emails | Your email address and the code | United States | Resend Privacy Policy |
| Apple Inc. | WeatherKit weather forecasts; also Sign in with Apple and the App Store (section 9.2) | For forecasts: coordinates rounded to about 1 km and your time zone, sent by our server without your account ID | United States | Apple Privacy Policy |
| Google LLC | Sign in with Google, if you choose it (section 9.2) | Your Google identifier, the email address Google verified and, if Google shares it, your name | United States | Google Privacy Policy |
| OpenMeteo GmbH (Open-Meteo, with GeoNames data) | City-name search for weather | The city name you type, sent by our server without your account ID or network address | Switzerland | Open-Meteo terms and privacy |
Wardrobe images are kept in one private store at a time: new uploads go to Vercel Blob or Cloudflare R2, whichever we use, and images already stored stay where they are until deleted.
9.2 Companies you connect directly
Apple (Sign in with Apple, and the App Store, which is the seller of your subscription and credits) and Google (Sign in with Google) process your information under their own privacy policies when you use them. We receive only what is described in section 4. When you use weather, your device may also contact Apple directly to turn your location into a place name and to show Apple Weather's logo.
9.3 Other people
When you share, we show the content you chose to the people who can open the share (section 7). We may also disclose information when the law requires it, to respond to valid legal process, to protect the safety of any person, to report suspected child sexual abuse material to the National Center for Missing & Exploited Children, to enforce our terms, or to professional advisers under confidentiality. If Backo is involved in a merger, acquisition, reorganization or sale of assets, information may be transferred as part of that transaction, and the recipient must continue to honor this policy.
9.4 What we never do
We do not sell personal information, share it for cross-context behavioral advertising or targeted advertising, or let advertising networks collect it in the app or on our website. We do not use your content for our marketing, and we do not send marketing email. We send email only for sign-in codes and, where needed, for notices about your account, your content, safety or legal matters. Reminders are scheduled on your device by its operating system; we do not use a push notification service.
10. International transfers
Backo is based in the United States and our providers mostly process data there. When we transfer personal data from the EEA, the UK or Switzerland, we rely on the EU-US Data Privacy Framework and its UK Extension and Swiss-US framework where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses, with the UK International Data Transfer Addendum where UK data is involved, together with the additional safeguards in our providers' data processing terms. You can ask privacy@snaza.app for a copy of the relevant safeguards.
11. How long we keep information
| Information | How long |
|---|---|
| Account, wardrobe, care labels, family profiles and day plans | While your account exists, including while a membership is lapsed. Erased as described in section 12 |
| Terms acceptance | While your account exists |
| Session credentials | Up to 30 days, or until you sign out or they are revoked |
| Email sign-in codes | 10 minutes, stored only as hashes |
| Photos sent for AI processing | Not stored by Snaza. Our AI providers may keep request data for a limited time under their own terms, for example for abuse monitoring (section 5.5) |
| Clothing-only covers waiting to be collected | Up to four hours |
| Duplicate-charge receipts | Up to four hours, then removed on later requests; always removed when your account is erased |
| AI permission record | While your account exists |
| AI processing records | Linked to your account for 90 days, then de-identified with a salted hash. Deleted after 24 months |
| Credit ledger and top-up purchase records | Linked to your account while it exists. De-identified when the account is erased and kept for [Accounting record retention period] for accounting and tax purposes |
| Handles | While your account exists. After you change handle, the old one is held for you for 30 days. After account deletion, only the handle text is held, linked to nobody, for 12 months so no one can take over your old links |
| Share addresses | When you end a share, its address is held for 12 months so it never opens something else |
| Shares, follows and invites | While the share exists. All of them end as soon as you confirm an account deletion request and are erased with your account |
| Blocks | Until you unblock, or until your account is erased |
| Reports and moderation decisions | 12 months after the decision, or 12 months after the report if no decision was made, then deleted. If an account involved is erased sooner, the report is kept until then without that account's identity, note or context |
| Feedback, screenshots and diagnostics | 24 months after the issue is closed, or 24 months after it was sent if it was never closed. Erased sooner with your account |
| Copy of your data (Download my data) | The file and its image links can be downloaded for 7 days |
| Privacy requests | While your account exists |
| Record that an account was erased | Kept without any readable account details, as proof of erasure |
| Server and hosting logs | [Hosting log retention period] |
| Database backups | [Database backup retention period], after which backups are overwritten |
| Waitlist | Until 90 days after the launch email is sent, or sooner if you unsubscribe or ask us to delete it |
| On your device | Until you delete it, delete your account on that device (which removes your portrait folder right away) or remove the app |
12. Deleting your account
You can delete your account in the app under Settings, Privacy & data. When you confirm:
- Your shares, follows and invites end at once, and your portraits and try-ons are removed from that device.
- You have 14 days to cancel in the app. Signing in again does not cancel the request.
- After that, our systems revoke your sessions, ask Apple to revoke Snaza's Sign in with Apple token if you used it, delete your customer record at RevenueCat, delete your stored images and delete or de-identify your account records. The whole process finishes within 30 days of your request.
A few things are kept after erasure, none of which identify you: AI processing records, the credit ledger and top-up purchase records, de-identified as described in section 11; reports, de-identified, until their retention period ends; the text of your handle, held for 12 months and linked to nobody; and a record that the erasure happened. Copies in database backups are overwritten within the period in section 11. Blocks and reports stay in place during the 14 days so that people you blocked stay blocked. Purchased credits are lost when the account is erased.
Deleting the app does not delete your account, and deleting your account does not cancel a subscription, which you manage in your Apple ID settings.
13. How we protect information
Data is encrypted in transit. Account credentials and sign-in codes are stored only as hashes, session credentials expire, and the app keeps its credential in the iOS Keychain. Every request is checked against the signed-in account, so one account cannot read another's data. Wardrobe images sit in private storage reached only through our authenticated server; the app never receives a storage link. AI provider keys stay on our servers. Photos are re-encoded before upload to remove hidden metadata. Access by our staff is limited to what they need. No system is perfectly secure; if a personal data breach affects you, we will notify you and the relevant authorities as the law requires.
14. Your rights and choices
14.1 In the app
- Delete pieces, looks, portraits and try-ons at any time.
- Withdraw AI permission, download a copy of your data and delete your account in Settings, under Privacy & data.
- Turn off location, camera, photos, calendars, reminders and notifications in iOS Settings.
- Pause or end shares, remove followers and block accounts in Settings, under Sharing.
- Object to the use of de-identified processing records to improve Snaza by writing to privacy@snaza.app.
14.2 Making a request
Download my data, in Settings under Privacy & data, gives you a copy of your account data at once, as a file with links to your stored images; the file and the links can be downloaded for 7 days. For anything else, write to privacy@snaza.app. We may need to confirm that a request comes from the account holder, for example by asking you to make it from the app while signed in. We answer within one month in the EEA and UK and within 45 days in the US, and tell you if we need an extension the law allows. Requests are free unless they are manifestly unfounded or excessive. We will not discriminate against you for using your rights.
14.3 EEA, UK and Switzerland
You have the right to access your personal data, correct it, erase it, restrict or object to its use, receive the data you gave us in a portable format, and withdraw consent at any time without affecting the lawfulness of processing before the withdrawal. You can also complain to your local data protection authority. In the UK this is the Information Commissioner's Office (ico.org.uk). We would appreciate the chance to help first.
14.4 United States
This section describes rights under the California Consumer Privacy Act and the comprehensive consumer privacy laws of other US states. We honor these rights for residents of every US state, whether or not a particular state's law applies to Backo.
Notice at collection. In the last 12 months we collected the following categories of personal information, for the purposes in section 8, from the sources in section 4, and kept them for the periods in section 11.
| Category | Examples | Disclosed for a business purpose to |
|---|---|---|
| Identifiers | Account ID, handle, email address, hashed Apple or Google identifier, purchase app user ID, network address (used transiently and stored only as a hash) | Vercel, Neon, RevenueCat, Resend, Cloudflare |
| Customer records | Name (if you give it), email address | Vercel, Neon, Resend |
| Commercial information | Membership, purchases and credit use | Apple, RevenueCat, Neon |
| Internet or other electronic network activity | Feature use, diagnostics you send, aggregate website visits | Vercel, Neon, Cloudflare |
| Approximate geolocation | A city or coordinates rounded to about 1 km | Apple (WeatherKit), Open-Meteo |
| Audio, electronic, visual or similar information | Photos you send for processing, clothing covers, care-label photos | OpenAI, Vercel, Cloudflare |
| Sensitive personal information | Account log-in credentials. Photos of you, in transit only | Vercel, Neon, OpenAI |
We do not collect precise geolocation or biometric information. We do not sell or share personal information, do not use it for targeted advertising or for profiling in furtherance of decisions that produce legal or similarly significant effects, and do not use or disclose sensitive personal information to infer characteristics about you. We have not done so in the last 12 months and have no actual knowledge of selling or sharing the personal information of consumers under 16. We honor Global Privacy Control signals, although there is nothing to opt out of.
You have the right to know what we collect and disclose, to access and receive a portable copy, to delete, to correct, and to opt out of sale, sharing, targeted advertising and profiling (which we do not do). You can use an authorized agent; we may ask the agent for proof of authority and ask you to confirm your identity. If we deny your request, you can appeal by replying to our answer or writing to privacy@snaza.app with the subject "Appeal". We will respond within the time your state's law sets, and if the appeal is denied you can contact your state attorney general.
We do not disclose personal information to third parties for their direct marketing purposes (California Civil Code section 1798.83). We keep height, weight and self-description only on your device and do not collect consumer health data as defined by the Washington My Health My Data Act.
14.5 Other countries
If you live elsewhere, for example in Brazil, Canada or Australia, you may have similar rights under your local law. Write to privacy@snaza.app and we will honor them as that law requires.
15. Children
Snaza is not for children. You must be at least 16 to use it, and at least 18 to use try-on or save portraits. The app asks for your birth year once per account; the answer stays on your device and is never uploaded. If we learn that someone under 16 has an account, we will delete it. A Family plan lets an adult organize clothes for the household, children included, but family profiles hold only a name, a relation, a color and clothing; do not add photos of children, and family profiles are never shared.
16. The website and the waitlist
The snaza.app website sets no advertising or tracking cookies and uses no social media pixels. Visits are counted in aggregate with Cloudflare Web Analytics, which does not use cookies or identify you. Visitors in the EU, the EEA, the UK and Switzerland are asked first, and analytics loads only if they allow it; everyone can change the choice with Cookie settings at the bottom of every page. The details, including the one item the site stores in your browser to remember that choice, are in the Cookie Policy.
If you join the waitlist, we keep the details listed in section 4 and use your address only to send one email when Snaza launches. We never keep your network address itself, only a one-way fingerprint that helps stop abuse, and a Cloudflare Turnstile check keeps automated signups out. The launch email has an unsubscribe link that works at once, and we delete the waitlist within 90 days after sending it. Before we send it, we add the email provider we use for it to section 9.1.
17. Changes to this policy
If we make a material change, we will tell you in the app, or by email if we have your address, at least 30 days before it takes effect, and show the new effective date at the top. When you next sign in, we record the version that then applies (section 4, Terms acceptance). We will not start using information already collected in a materially different way, including for AI training, without telling you first and, where the law requires it, getting your consent. Changes that do not affect your rights, such as correcting a typo or updating an address, may be made without notice.
18. Contact
Backo, Inc., [Backo, Inc. mailing address] · privacy@snaza.app