Style Morph StudioStart morphing!
← Style Morph

Privacy Policy

Last updated 10 September 2026

Style Morph never stores your photo. It is held in your browser, sent to the AI services that restyle it, and gone when you close the tab. This page says exactly who receives what, and how to get any of it deleted.

Who we are

Style Morph (“we”) is operated by Style Morph. This policy covers the Style Morph website and everything you do on it. Questions, requests and complaints all go to [email protected].

Your photograph

Your photo is the most sensitive thing you give us, so it gets its own section.

  • We do not store it. It is held in your browser while you work, and we keep no copy — not on disk, not in a database, not in a file store. Closing the tab ends it.
  • It is sent to the AI services that process it. To read your photo and propose styles, and to generate each restyled look, we transmit it to the providers named below. This is what makes the product work, and it means your photo does leave your browser. Those providers hold it under their own policies, which we link to.
  • Faces are analysed, not enrolled. Face landmarks are detected in your browser to align the looks for the morph. They are never sent to us, and we build no face template, faceprint or biometric identifier and do not use your photo to recognise you anywhere else.
  • We do not train on it. We do not use your photo to train models, and we do not publish, sell or share it with anyone beyond the processing described here.

The finished video is likewise produced in your browser. It reaches our server only if you choose to send it to TikTok or YouTube, and then only to pass it on.

What else we collect

  • A device identifier. A random ID in a cookie, created on your first visit. It is how free daily runs and credits are counted. It is not linked to your name.
  • Your email address, only if you sign in. It identifies your account so credits follow you between devices.
  • Credit history. Purchases and usage, kept as a ledger — required to run a paid service and to settle disputes.
  • Server logs, including IP address and timestamps, kept briefly for security and debugging.

We do not sell personal information, and we never share your photograph or your finished video with anyone for advertising. What we do share for advertising measurement is described in the next section.

Advertising measurement

When we run ads, we need to know which ones brought people here and whether those people found the product useful. That is done with Meta’s pixel and its Conversions API, which run only while an advertising campaign is configured — when none is, no advertising script loads and no advertising cookie is set.

  • What Meta receives. That you arrived, uploaded a photo, started a makeover, opened checkout or bought credits — each as a single event, with no detail of what you made. Alongside it: your IP address, your browser’s user-agent string, Meta’s own advertising cookies if they are present, and, where we know them, your email address and device identifier — both of those hashed before they are sent, so the address itself never leaves us.
  • What Meta never receives. Your photograph, your finished video, the styles suggested for you, or anything else you make here. None of it is sent, in any form, at any point.
  • Half of it runs on our server. The same events are sent from our side as well as from your browser, so that blocking the script changes what we can measure but not what is measured. Blocking it does still stop the cookies and the browser half.
  • How to stop it. A tracker blocker removes the browser half. For the rest, Meta’s own ad settings control how your data is used for advertising, and you can ask us to delete everything we hold using the address at the top of this page.

Under laws that use the word broadly — California’s among them — sending these events to Meta counts as “sharing” personal information for cross-context behavioural advertising. We would rather say so plainly here than rely on a narrower reading of it.

If you connect TikTok

Connecting TikTok is entirely optional and the product works fully without it. If you do connect it:

  • We receive your TikTok account ID, display name and avatar. The name and avatar are shown next to the button so you can confirm which account you linked. That is their only use.
  • We store an access token and refresh token, encrypted at rest with AES-256-GCM. They are used solely to send a video you have asked us to send.
  • We request permission to place videos in your drafts only. We do not hold, and have not asked for, permission to publish to your profile. Every post is completed by you, inside TikTok.
  • Disconnecting deletes the tokens immediately. Use the Disconnect control on the results screen, or revoke access in TikTok under Settings → Security and permissions → Manage app permissions. You can do either at any time, for any reason.

If you connect YouTube

Also entirely optional, and the same shape as TikTok. If you connect a channel:

  • We receive the email address of the Google account you authorised, and nothing else about it. It is shown next to the button so you can confirm which account you linked.
  • We store an access token and refresh token, encrypted at rest, used solely to upload a video you have asked us to upload.
  • Uploads land private on your channel. You publish them yourself in YouTube Studio; we never make anything public on your behalf.
  • Disconnecting deletes the tokens immediately. You can also revoke access at any time in your Google account under Third-party apps with account access.

Who receives your data

Everyone outside Style Morph who handles any of it, and what they get:

WhoWhyWhat they receive
fal.aiGenerates the restyled looks.Your uploaded photo, the reference photo you chose, and the text prompt.
Google (Gemini API)Reads the photo to propose the three style directions.Your uploaded photo.
FirecrawlFinds the reference photographs for each style direction.The search terms — never your photo.
SupabaseStores the account, credit ledger and connection records.Your device identifier, email if you sign in, and credit history.
StripeTakes payment as merchant of record.Your payment details, directly — they never reach our servers.
ResendDelivers sign-in codes.Your email address.
TikTokReceives the video you choose to send, if you connect an account.The video file and your authorisation.
YouTube (Google)Receives the video you choose to send, if you connect a channel.The video file, your authorisation, and your Google account email.
MetaMeasures which ads bring people here.That you arrived, uploaded a photo, started a makeover, opened checkout or bought credits — with your IP address and browser, and your email and device identifier where known, both hashed. Never your photo or video.
RailwayHosts the application.Ordinary server logs, including IP address.

These providers operate in several countries, so using Style Morph involves transferring data internationally. We disclose data otherwise only where the law requires it.

How long we keep things

  • Photos and videos: not retained. Only for the moments a request takes.
  • Account, email and credit ledger: until you ask us to delete the account. Purchase records may be kept longer where tax or accounting law requires.
  • Connection tokens: until you disconnect, you revoke access, or the grant expires.
  • Free-run and usage counters: reset daily.
  • Server logs: a short rolling window.

Your rights

Wherever you live, you can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it and close your account. Depending on where you live you may also have rights to restrict or object to processing, to portability, and to complain to your data protection authority.

Email [email protected] and we will respond within 30 days. There is no charge, and asking costs you nothing else.

Children

Style Morph is not for anyone under 13, and we do not knowingly collect their data. If you are under 18, use it only with a parent or guardian’s permission. If you believe a child has used the service, write to us and we will delete what we hold.

Security

Connections are encrypted in transit. Stored connection tokens are encrypted at rest. Database access is denied to browsers outright and goes only through our server. Payment card details never reach our systems. No system is perfect, and we will tell affected users promptly if something goes wrong.

Changes

If we change this policy we update the date at the top. If a change materially affects how your data is used, we will say so in the product before it takes effect.