Privacy
You send us a photo of yourself. That deserves a policy you can actually read, so this one says plainly what we collect, who it goes to, how long we keep it, and how to make us delete it.
Last updated 24 August 2026 · Version 1.1
Who you are dealing with
One small company, reachable by email.
NoRulesTrends is operated by Bong Realty CA LLC ("we", "us"). We are the data controller for the information described here, which means we decide what is collected and why, and we are the ones you hold responsible for it.
For anything in this policy — access, deletion, corrections, or a complaint — write to privacy@norulestrends.com. For everything else, hello@norulestrends.com.
One small company, reachable by email.
What we collect
Your photo, your three quiz answers, whether you liked each look, and — only if you make an account — your email.
We collect the least we can get away with while still producing a styling result. There is no profile to fill in, no name field, and no questionnaire beyond the three taps in the quiz.
- The photo you upload — An image of yourself. It is the input to everything the product does, and it is the most sensitive thing we hold. Section 5 covers where it goes.
- Your quiz answers — Mood, occasion, and weather — three choices from fixed lists.
- Your verdict on each look — Whether you liked a look or not, if you tell us. This steers the next round of styling.
- Your email address — Your free reveal needs a confirmed email address or a Google or Apple sign-in. It is what your looks are saved to, and it is what stops one free reveal becoming an unlimited supply of them. You can browse the site without one; you cannot claim the free reveal without one.
- Approximate country — Derived from your IP address by our hosting provider and used to search for clothes you can actually buy, priced in money you actually spend. We store the resulting country code against your looks.
- The IP address your free reveal was claimed from — Stored once, against your free-reveal record, so that a small number of free reveals per network per day can be enforced and so abuse can be investigated. It is never joined to your photo, your looks, or your styling preferences, and it is deleted with your account.
- Payment status — If you buy reveal credits, we store your Stripe customer reference and a record of what you bought and what you have spent. We never see or store your card number — Stripe handles the payment and we only learn the outcome.
- Ordinary server logs — Our hosting providers keep the usual request logs for security and debugging. We do not mine them.
- Which steps of the product you reached — A short list of milestones — you signed up, you uploaded a photo, a reveal started, a reveal finished, you opened checkout, a payment settled, you made or opened a share card — plus a few notes on what you opened in the app, such as which look you tapped. Each record holds the step’s name, when it happened, a per-visit random key that dies when you close the tab, and at most an internal look or session id. We keep these for 400 days and they are deleted with your account.
- What these records never contain — Not your photograph, not anything you typed, not your styling preferences, complexion, body type or attire tradition. Those are collected to style you and are used for that and nothing else; they are excluded from this counting entirely, by design and not by policy.
Your photo, your three quiz answers, whether you liked each look, and — only if you make an account — your email.
What we do not do
No ad trackers, no third-party analytics, no selling your data. This is a statement about the code, not an aspiration.
The site loads no third-party analytics and no advertising or tracking scripts. There is no Google Analytics, no Meta pixel, no session recorder. We have never sold or shared personal information for money or for cross-context behavioural advertising, and we do not intend to start.
We do count things about the product itself — how many people finish a reveal, how many go on to buy — and we do it on our own servers, in our own database, with no analytics vendor involved. Section 2 lists exactly what those records contain. The distinction we are drawing is not a technicality: a third-party analytics script sees you across other people’s websites, and nothing here ever does.
We do not use your photo to train our own models, and we do not build an advertising profile about you.
No ad trackers, no third-party analytics, no selling your data. This is a statement about the code, not an aspiration.
Why we are allowed to use it
To make the thing you asked for, to keep the free tier honest, and to take payment.
We use your photo and quiz answers to generate your looks, and to find garments to go with them. We use your account details to keep your looks attached to you and to stop a single free allowance being reset by opening a new browser window. We use payment status to know whether to unlock paid features.
Where the UK and EU GDPR apply, our lawful basis is performance of a contract with you for delivering the service you asked for; legitimate interests for keeping the service secure and preventing abuse of the free tier; and your explicit consent for processing your photograph, which you give by uploading it and can withdraw at any time by asking us to delete it.
To make the thing you asked for, to keep the free tier honest, and to take payment.
Your photo, specifically
It goes to Google and to FASHN.ai to be processed, and the finished look is stored somewhere anyone with the link can see.
Producing a look means sending your photograph outside our own systems. There is no version of this product where that does not happen, so here is exactly what happens.
Anonymous originals are stored under a private server/team-only namespace and are never returned as browser-readable storage URLs. Signed-in originals are stored under a private owner namespace and are accessible to that owner through authenticated APIs. A processor URL is minted only immediately before Google Gemini or FASHN.ai receives the image.
Generated try-on images are private by default. You can create a 5-minute grant for exactly one generated object; it is uncached, does not make the bucket public, is time-limited rather than guaranteed single-use, and cannot recall copies someone downloaded.
Separately, you can publish one generated look to a link of its own. That link does not expire: it works until you take it down, or until the look is deleted — by you, or by the retention period you chose. Anyone holding it can see that look, its palette and the occasion it was styled for, without an account. Your original photograph is never published, we store only a fingerprint of the link rather than the link itself, and the page is never indexed by search engines.
- Google (Gemini API) — Receives your photograph and your quiz answers in order to judge what would suit you. Google acts as our processor.
- FASHN.ai — Receives your photograph in order to render you wearing the garments. FASHN acts as our processor.
It goes to Google and to FASHN.ai to be processed, and the finished look is stored somewhere anyone with the link can see.
Who else touches your data
Our hosting, database, payments and search suppliers — each for one job, none of them free to use it for their own.
We use a small number of suppliers to run the service. Each processes data only on our instructions and only for the purpose listed. All of them are based in the United States, so using the service involves transferring your information there; where the UK or EU GDPR applies, those transfers rely on the standard contractual clauses in our agreements with each supplier.
- Supabase — Database, file storage, and sign-in.
- Vercel — Hosting and content delivery.
- Stripe — Payments. Stripe is a controller in its own right for the payment itself; its privacy policy governs that part.
- Tavily — Searching retailers for garments. It receives descriptions of clothing and a country, never your photo, your email, or anything identifying you.
- Affiliate networks — If we have affiliate tracking enabled and you click through to a retailer, that network and the retailer will see the click. They set their own cookies under their own policies. We are paid a commission on some purchases; it never changes what we show you.
Our hosting, database, payments and search suppliers — each for one job, none of them free to use it for their own.
How long we keep it
Anonymous styling data becomes eligible for deletion 2 hours after the session. The purge scheduler runs every 6 hours on a best-effort basis, so the operational outside limit is 8 hours after upload.
Anonymous data is eligible for purge after 2 hours. The configured every-6 hours scheduler is best-effort, so the outside limit is 8 hours after upload. Signed-in users may choose 7, 30, 90, 365 days, defaulting to 365; that setting applies to the selfie, generated looks, quiz answers, feedback, and cached styling data for the session.
Deletion removes Storage objects before database rows. A failed Storage deletion leaves the rows retryable rather than claiming success. Billing, security, and legally required audit records have separate retention and are not styling data.
A share grant lasts 5 minutes and is scoped to one generated object. Expiry is not cryptographic single-use behavior, and deleting our copy cannot recall a file someone downloaded.
A link you have published is removed with the look it points at, so both your retention choice and “Delete everything” take it down, and you can revoke it yourself at any time. As with any share, we cannot recall a copy someone has already saved.
Anonymous styling data becomes eligible for deletion 2 hours after the session. The purge scheduler runs every 6 hours on a best-effort basis, so the operational outside limit is 8 hours after upload.
What you can make us do
Ask for a copy, ask for a correction, or ask us to delete the lot. One email, thirty days.
Write to privacy@norulestrends.com and we will act within 30 days. We will not charge you, and we will not make the service worse for you because you asked.
- Get a copy — Of your photo, your looks, and everything else we hold about you.
- Delete it — Everything we hold, including every generated look. Your uploaded photograph will already have gone on its own. If you have shared a look publicly, tell us and we will remove the stored image, though we cannot recall copies other people already saved.
- Correct it — Fix anything inaccurate.
- Withdraw consent — For processing your photograph. This ends your ability to generate new looks, because the photograph is the input.
- Object, restrict, or take it elsewhere — Where the UK or EU GDPR gives you those rights, you have them here.
- Complain — To your data protection authority — the ICO in the UK, or your national regulator in the EU — if you think we have got this wrong. We would rather you told us first.
Ask for a copy, ask for a correction, or ask us to delete the lot. One email, thirty days.
How it is protected
Encrypted in transit and at rest, and scoped so only you can read your own row.
Traffic is encrypted in transit. Stored data is encrypted at rest by our database and storage providers. Access to your sessions, looks and photographs is enforced at the database level, so one account cannot read another's, and the keys capable of bypassing that never leave our servers.
Authorized support, security, and deletion operations use authenticated server routes, are limited to an exact user or object, and are recorded in an access log. Finished try-on images remain private unless the owner creates a short-lived share grant.
No system is perfect. If we ever suffer a breach affecting your personal data, we will notify the relevant regulator within 72 hours where the law requires it, and tell you directly where the risk to you is high.
Encrypted in transit and at rest, and scoped so only you can read your own row.
Age
Sixteen and over. Do not upload a photo of a child.
This service is not for anyone under 16, and we do not knowingly collect anything from a child. Uploading a photograph of a child is a breach of our terms regardless of who you are.
If you believe a child has used the service or appears in an uploaded photograph, tell us at privacy@norulestrends.com and we will delete it.
Sixteen and over. Do not upload a photo of a child.
Faces
We do not run face recognition, and we do not build a faceprint. Some laws still treat a photo of your face as sensitive, so we treat it that way too.
We do not perform facial recognition, we do not extract or store a facial template or 'faceprint', and we do not attempt to identify who you are from your photograph. The image is used to render you wearing clothes and for nothing else.
Some jurisdictions nonetheless class images depicting an identifiable face as biometric or otherwise sensitive personal information. We handle your photograph on that assumption: on your explicit consent, for a single stated purpose, shared only with the two processors named above, and deleted whenever you ask.
We do not run face recognition, and we do not build a faceprint. Some laws still treat a photo of your face as sensitive, so we treat it that way too.
Changes to this policy
We will date them, and we will not backdate them.
If this policy changes we will update the date at the top and, for anything that materially affects you, tell you in the product before it takes effect. Previous versions are available on request.
We will date them, and we will not backdate them.