Privacy Policy

What runs where, plainly

GIFs and stickers are entirely local. When you drop in a photo to make a GIF or a sticker, the image is processed by your own browser. The AI models run on your device. The photo is not sent to us, we cannot see it, and no account is required.

3D is local on Pro, and split on Free. See the next section — this is the one place the two plans genuinely differ in what we receive.

Publishing uploads. If you choose to publish a 3D scene so it has a shareable link and an embed, the finished files are uploaded to our storage, and this is the one point at which your photo itself is sent to us. On the free plan one other thing is sent earlier — the intermediate data for the depth step, described next — but never the image.

How 3D depth is calculated

Making a 3D scene needs a depth map. The model that produces it is split in two halves, and which half runs where depends on your plan.

• Free. Your browser runs the first and larger half of the model on your photo. The result is a set of intermediate numbers (machine-learning “activations”) which are sent to our server, where the second half turns them into a depth map that is sent back. Your photo is never sent — only these intermediate numbers, which are not an image and cannot be viewed as one. We process them in memory to produce your depth map and do not store or log them. We do record that a generation happened, so we can count it against your free allowance.
• Pro. You receive both halves of the model and everything runs on your device, exactly like GIFs and stickers. No image data and no intermediate data reaches us at all, and it works offline.

We should be straightforward about one caveat: intermediate activations are derived from your photo. They are not a picture and we do not attempt to reconstruct anything from them, but published research shows that approximate reconstruction from data of this kind is possible in principle. If that matters for a particular image, use Pro (fully local) or stick to GIFs and stickers.

What we receive when you publish

• The processed colour image, its depth map, the cut-out subject layer, and a generated background — the files the viewer needs to draw your scene.
• A database record: the scene's ID, the account that owns it, your chosen scene settings, whether it carries the Gifsy badge, and a view counter.

Published scenes are public. That is the point of them — they are made to be shared and embedded on other websites. Their files are served from public URLs, so anyone with the link, or with the page the scene is embedded in, can view them. They may also be cached by browsers and content networks for up to a year. Please do not publish a photo you would not put on a public web page.

The background-cleanup step

At the moment you publish, your image and its subject mask are sent to our server once, so a model can paint in a clean background behind the subject. That data is processed in memory to produce the result and is not stored or logged by us. Together with the depth step described above and the upload of the finished scene, this is the complete list of times anything derived from your image leaves your device.

Accounts

You do not need an account for GIFs or stickers. You need a free account to generate a 3D scene, and to publish. If you sign up, we store your email address, your plan, and a count of the 3D generations you have made — that last one is how the free allowance is enforced, so it is kept on our servers and is not affected by clearing your browser data. We do not store the images those generations were made from. Authentication is handled by Supabase.

Payments

Payments are handled by Dodo Payments, which acts as the merchant of record. Your card details go to them, never to us — we never see or store them. Pro is a single payment with no subscription and no renewal date, so what we keep is a record of that payment and the plan it granted, which is how we know to give you Pro.

Analytics

We use Vercel Analytics to count page views and a small number of product events — for example that a scene was published, or that a visitor interacted with a demo. It is aggregate and is not used to build a profile of you or to track you across other websites.

Services we rely on

• Vercel — hosting, file storage for published scenes, and analytics.
• Supabase — accounts and our database.
• Dodo Payments — payments.
• jsDelivr and img.ly — your browser downloads the inference runtime and the background-removal model from these content networks the first time you use a feature that needs them. They receive the request for those files, as any website you load a file from would. Your photo is not part of that request. The depth model's two halves come from our own storage, not a third party.

Keeping and deleting your data

Published scenes stay up until you or we remove them. Because their files are served with long cache lifetimes, copies may persist in caches for a period after deletion.

Self-serve deletion of a published scene is not available yet. To delete a published scene, or your account and everything attached to it, email us at aman@metamemory.tech from the address on your account, and we will action it.

Children

Gifsy is not directed at children under 13, and we do not knowingly collect their personal information.

Changes

If this policy changes in a way that affects you, we will update the date at the top of this page. Continuing to use Gifsy after a change means you accept the updated policy.

Contact

Questions, or a deletion request: aman@metamemory.tech. See also our Terms and Refund Policy.