Privacy Policy
Last updated 7 September 2026
Wrapture lets you build a private 3D world as a gift — photos and things you have written — and send it to someone with a link. That means we hold two kinds of personal information: yours, because you signed up and paid, and the recipient's, because your gift is about them. This page explains both, in the order that actually matters.
Who runs Wrapture
Wrapture is a service for creating and sharing digital worlds and media. Questions or privacy requests may be sent to hello@wrapture.app.
For UK and EU data protection law we are the controller — for your account and payment data, and also for the gift content you upload about someone else. Building a private gift for one person is close to a purely personal activity, and for you it may well be one. It does not follow that we are exempt: the rules are explicit that a company providing the means for that kind of processing is still covered, and a page published at a link that can be forwarded to anyone is not a private household matter. We take the responsibilities of a controller for everyone whose data ends up here, including people who never signed up.
What we collect, and why
There is no marketing list, no data broker relationship, and no advertising network in Wrapture. Everything below is here because the product does not work without it.
- Your Google account details
- Signing in with Google is the only way to create an account. Google passes us your email address, your name, and a Google account identifier, which Supabase stores as your user record. We never receive or store your Google password.
- The gift itself
- Everything you put in a world: photos, headings and written messages, dates, and the theme you choose. Stored as a JSON document in our database, with the photo files in a separate storage bucket.
- Answers to the setup questions
- The occasion, the recipient's first name, their pronouns, and depending on the occasion a birthday, an anniversary date and duration, or two city names. These are used to write the page's opening screen.
- Page password (if you set one)
- Stored only as a bcrypt hash, never as readable text. If you also write a password hint, the hint is stored as plain text, because the recipient has to be able to read it — so do not put the password in the hint.
- Payment records
- Stripe processes the payment. Card numbers never touch our servers. What we store is a Stripe Checkout session identifier against your page and a true/false flag saying it was paid. Stripe separately holds the full transaction record, including your card details and billing information, under its own privacy policy.
- Product analytics
- PostHog records that a draft was created, that checkout was started or completed, and that a page was published, unpublished or deleted, each tied to your account identifier. Your email and name are attached to your PostHog profile. See cookies and analytics for what the browser library captures on top of that.
- Error reports
- When something breaks, Sentry receives the error, the stack trace, the URL, and browser and device information. This includes errors thrown on published pages, which means a recipient's browser can generate a Sentry event even though they have no account.
If someone made a page about you
This section is for people who did not sign up for anything. Someone built a Wrapture page about you, and you have rights over that content even though you never agreed to our terms and we have no account for you and no way to contact you.
The person who created the page chose what to include. We did not collect it from you, and in most cases we know nothing about you beyond a first name typed into a form — we have no email address for you and no way to reach you. Under UK and EU law, when data is obtained from someone other than the person it describes, Article 14 says we should normally notify you directly. We cannot, because we hold no contact details for you, so this page is how we give that notice instead. We are not going to pretend that is a perfect answer: the person who built your page could reach you, even though we cannot, which is why our terms put the duty to get your permission on them, before they upload anything.
You can have it taken down. Email hello@wrapture.app with the link, and tell us you are the person it is about. We will unpublish it and delete the stored content, including the photos, as quickly as we can. You do not need to give a reason. If you are objecting under Article 21 of the UK or EU GDPR, or exercising a deletion right under a US state privacy law, say so and we will treat it as a formal request, but plain English is enough.
We may need to ask one or two questions to check you are who you say you are, because "delete this page" from a stranger is also how a gift gets destroyed maliciously. We will not ask for identity documents unless we genuinely cannot resolve it any other way.
Companies that process data for us
We do not sell personal information, and we do not share it for cross-context behavioural advertising. Under California law that means we do not "sell" or "share" as those words are defined there, and there is no "Do Not Sell or Share My Personal Information" link on this site because there is nothing for it to switch off.
Below is every company that handles data for us, named individually rather than described as “categories of recipients”. Naming them is what you would be entitled to ask for anyway, so it may as well be written down. Each is bound by a contract limiting them to processing data for us:
- Supabase
- Database, file storage, and the authentication system. Holds your account record and every piece of gift content. Runs on Amazon Web Services infrastructure in US West.
- Sign-in only. Google knows you authenticated to Wrapture; Google does not receive the contents of your pages.
- Stripe
- Payment processing. Stripe is an independent controller of the payment data it collects, not merely our processor, and it holds the card and billing details we never see.
- Vercel
- Hosting and content delivery. Server logs, including IP addresses, are generated in the ordinary course of serving the site.
- PostHog
- Product analytics, on its US cloud. Receives the events and profile data described above.
- Sentry
- Error monitoring. Receives crash reports and diagnostic context.
We will also disclose information if the law requires it — a subpoena, a court order, a genuine legal obligation — and if Wrapture is ever sold or merged, account and page data would transfer to the buyer, who would be bound by this policy until they told you otherwise.
How long we keep things
The honest version, which differs from what most policies claim:
- Published pages are kept indefinitely. That is the product promise — you pay once and the page stays up. There is no expiry date and no automatic clean-up.
- Drafts are also kept indefinitely unless you delete them.
- Deleting a page removes the page record and takes the link offline immediately.
- Payment records are retained by Stripe and by us for as long as tax and accounting rules require, which in the US is generally seven years.
- Analytics and error data are kept for PostHog's and Sentry's standard retention periods.
How public a published page really is
We would rather be precise about this than reassuring, because people make decisions about what to upload based on it.
A published page lives at a random seven-character link. It is not listed anywhere, not indexed by us, and not guessable in any practical sense — roughly thirteen billion combinations. But it is a link, not a login. Anyone who has it can open the page. Forwarded links keep working.
Adding a password puts the page contents behind a check performed on our server, so the text and media of a locked page are not sent to the browser until the password is right. One thing is still readable before the password: the recipient's first name, which the unlock screen needs in order to greet them.
The important caveat: the uploaded files themselves live in public storage buckets with permanent URLs. The password protects the page; it does not protect a photo from being viewed by someone who has that file's direct URL. Those URLs contain a random component and are not published anywhere, but they are not secret in the cryptographic sense. Do not upload anything to Wrapture that would cause real harm if a link leaked.
Cookies, local storage and analytics
Wrapture uses required cookies and local browser storage to keep you signed in, save your drafts as you work, and run the site securely. These are not optional extras: without them the builder cannot tell who you are, and a draft you were halfway through would be lost on refresh. Using Wrapture indicates your agreement to them, which is what the notice on the site says.
Supabase sets the sign-in cookies. Your browser's own local storage holds draft state and small interface preferences, and stays on your device.
PostHog sets its own cookies and, with its default configuration, automatically captures page views and interactions such as clicks in addition to the specific events we send. It is initialised for everyone who loads the site, including recipients opening a gift. If you want no analytics at all, a browser-level tracker blocker will stop PostHog loading and the site will work normally without it.
Your rights, and how to use them
Wherever you live, you can ask us to give you a copy of your data, correct it, or delete it. Some of it you can do yourself: pages can be deleted from your home screen, and a published page can be unpublished within thirty days of first publishing.
There is currently no self-service account deletion. To close your account and have everything removed, email hello@wrapture.app and we will do it manually. We aim to complete requests within 30 days, and 45 where a US state law sets that as the deadline.
We will not charge you for a request, refuse it because you complained, or degrade your service for having made one.
US state privacy rights
Around twenty US states — California, Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland and others — now give residents rights over their personal information. Most of them only bind companies above a size threshold, measured in revenue or in tens of thousands of residents' records, and Wrapture is a small operation well underneath those lines. California's law, for instance, starts at roughly twenty-six million dollars of annual revenue.
Some do not work that way. Texas and Nebraska apply without any revenue floor. We would rather not have our answer to a person asking about their own data depend on an argument about which statute reaches us.
Rather than argue about which ones technically reach us, we extend the same rights to everyone: know what we hold, get a copy, correct it, delete it, and not be discriminated against for asking. Email hello@wrapture.app. An authorised agent may submit a request on your behalf with written proof.
California residents specifically: we do not sell or share personal information and we do not use it for cross-context behavioural advertising. California treats biometric information as “sensitive” when it is processed in order to identify someone in particular. We do not do that: we store the photographs you upload and serve them back when your page is opened, and we run no facial recognition or any other biometric matching on them. There is no separate right to limit for us to offer you.
If we ever decline a request you can appeal by replying to our decision, and several states additionally let you complain to your state Attorney General.
UK and EU rights
If you are in the UK or the European Economic Area, our lawful bases are:
- Contract — for your account, your drafts, publishing your page, and taking payment. We cannot provide Wrapture without these.
- Legitimate interests — for analytics, error monitoring and security, balanced against your interests, which is why the analytics are limited to product events rather than tracking people across the web.
- Legal obligation — for keeping financial records.
You have the right to access, rectify, erase, restrict and port your data, and to object to processing based on legitimate interests. Where a recipient asks us to erase a page about them, we act on it as described above.
Content you upload could include special category data under Article 9 — a photograph revealing religious dress, say, or a message about someone's health. Wrapture does not ask for it and does not process it deliberately. If you choose to include it, you are asking us to publish it, and we treat that as your explicit consent under Article 9(2)(a), which you can withdraw at any time by deleting the page.
You may complain to your supervisory authority — in the UK, the Information Commissioner's Office at ico.org.uk; in the EEA, your national data protection authority. We would rather you came to us first.
Children
Wrapture is not for children. You must be at least 16 to create an account, and if you are under 18 you need a parent or guardian's permission. We do not knowingly let under-16s sign up. We also do not currently ask your age at sign-up, so this rule depends on you being honest about it.
Wrapture is built for couples: one partner making a gift for the other. It is not a service for or about children. A photograph you upload may still happen to include one — a family picture, a child at a wedding — and it is worth being clear about what that means. The US children's privacy rule, COPPA, is about services collecting information directly from children under 13. No child signs in to Wrapture, and a photo like that reaches us from an adult account holder, not from the child in it. We do not build profiles of anyone who appears in a page or use their content for advertising.
If you are a parent or guardian and a page contains your child, you can have it taken down without explaining yourself: email hello@wrapture.app and we treat it as a priority.
Where data is stored and sent
Wrapture is operated from the United States and its data is stored there. If you are in the UK or EEA, using Wrapture means your information is transferred to the US. We rely on the EU and UK Standard Contractual Clauses together with the UK International Data Transfer Addendum as the primary safeguard, and some of our processors are additionally certified under the EU–US Data Privacy Framework. We lead with the contractual clauses deliberately: the Framework survived its first annulment challenge in 2025 but is under appeal to the EU's top court, and we would rather not have our lawful basis for transfers depend on the outcome.
Security
Everything travels over HTTPS. Page passwords are hashed with bcrypt. Database access is governed by row-level security policies, so one account's query cannot reach another account's pages. Payment is handled entirely by Stripe. The keys that bypass those protections are held server-side and never sent to a browser.
None of that makes a system perfectly safe, and we would rather you read the section on how public a page really is than take a general assurance from us. If you find a security problem, email hello@wrapture.app and we will take it seriously.
Changes to this policy
When this policy changes, the date at the top changes with it. If a change materially affects what happens to data we already hold, we will tell account holders directly rather than quietly editing the page.
Contact
Privacy questions, deletion requests, takedown requests and complaints all go to the same place: hello@wrapture.app. A person reads it.
