Privacy
Last updated: 19 November 2026
Previewer is made by d2 Studio in the Netherlands. This page says what Previewer stores about people, why, where, and for how long. Questions, or a request about your data: hello@previewer.agency.
The short version
- We store what it takes to run your account: your email address, your name if you fill it in, a hashed password and a log of what was done in the account.
- Your clients can open a preview without an account. We don't store their name, IP address or browser details, and the preview page sets no cookies unless the campaign has a password.
- No analytics, no advertising, no tracking cookies, and we never sell or share data for marketing.
- Everything is stored in the EU (Frankfurt).
Two roles
For your account, d2 Studio decides what is stored and why: we are the controller of your login details and the account's activity log.
For what you upload (banners, images, videos, client names and logos, notes, approvals), you decide what goes in and who sees it. We store and show it on your behalf, as your processor, and only to run Previewer for you. If you need a data processing agreement for that, ask us and we'll send one.
What we store
| What | Why | How long |
|---|---|---|
| Your email address, your name if you or the person who invited you filled it in, a scrypt hash of your password, your role and access level | To sign you in and decide what you can do | Until your login is deleted |
| When you last signed in | So your account owner can see who is active | Until your login is deleted |
| The activity log: who did what and when (for example "uploaded 300x250"), with the name or email address of the person who did it | So your account owner can see what changed | 3 months; deleted sooner when the account is deleted |
| API tokens: their name, when they were last used, and a SHA-256 hash of the token (never the token itself) | To let your own tools upload | Until the token or your login is deleted |
| A command line sign-in: the device name you gave and the IP address it came from | To show you on the approval page where the request came from | Deleted a day after the request expires (it expires after 10 minutes) |
| Which campaigns you follow | To send you one email when a client approves creatives in them | Until you unfollow, or the campaign or your login is deleted |
| Invite and password reset links: which login they're for, who sent them, when, and a SHA-256 hash of the link (never the link itself) | So someone invited can choose their own password, and anyone can reset a forgotten one | An invite works for 7 days, a reset link for 1 hour; deleted a day after it expires or is used |
| Failed sign-in and preview password attempts and requests for a password reset link, as a SHA-256 hash of the IP address and email address (never in clear) | To slow down password guessing | Deleted after a successful sign-in, or after about a day |
| Error reports: the page address, browser type and what went wrong | To find and fix bugs | 90 days at most |
Your clients, on the preview link
Someone you send a preview link to doesn't need an account, and we keep no profile of them.
- Views. When the page loads in a browser, the campaign's view count goes up by one and its "last viewed" time is updated. Nothing about the visitor is stored.
- Approvals. An approval stores the time, on the banner, and a line in your activity log that says "Client (preview link)". After approving, the person can add their name; that is optional. A name they add is stored with the approval, shown to you (in the campaign, the approval email and the activity log) and to others who open the same preview link, and kept until the approval is undone, the banner is replaced or removed, or the campaign is deleted. Their browser remembers it (local storage) so they aren't asked again. No IP address or other detail about the person is stored.
- Passwords. If a campaign has a password, a wrong guess counts toward a limit as described above (a hash of the IP address, gone within about a day).
- The layout a visitor picks is kept in their browser for that tab only (session storage). It never reaches us.
- While you choose a password from an invite or reset email, the link's code is kept the same way (session storage, that tab only), so a reload still works. It is removed once the password is set.
Banners themselves are your agency's code. They run in a sandbox, apart from Previewer, but a banner can load scripts or images from elsewhere if its author built it that way. That is part of the banner, not of Previewer.
Cookies
Previewer sets no analytics, advertising or tracking cookies, so there's no cookie banner. It sets two cookies, both strictly needed for what you asked to do:
| Cookie | What it does | How long |
|---|---|---|
banner_preview_admin | Keeps you signed in | 8 hours after your last activity, 7 days at most |
bp_unlock_<campaign> | Remembers that you entered a preview's password | 30 days, or until the password changes |
The admin also keeps a few small notes in your own browser (whether you hid the getting-started tips, and an unsaved campaign draft for that tab), so they don't have to be stored with us.
Who else handles data
We use a few companies to run Previewer. Each only gets what it needs, under a data processing agreement:
| Company | What for | Where |
|---|---|---|
| Supabase | Database and file storage | Frankfurt, Germany |
| Vercel | Hosting: runs the app and serves pages | App runs in Frankfurt, Germany; pages are delivered from the server nearest the visitor |
| Sentry | Error reports, with cookies, request contents and your account details removed before they're sent | Frankfurt, Germany |
| Resend | Sending invites, password reset links, approval emails and security notices about your own login (an email change, a new terminal sign-in): the recipient's email address and the email itself | Ireland |
| Google Workspace | Email, if you write to us | EU and US |
Vercel, Supabase, Sentry, Resend and Google are US companies. Where data could reach the US, the EU's standard contractual clauses and the EU-US Data Privacy Framework apply.
We don't use analytics or advertising services, and we never sell data. The emails we send contain no tracking pixels or tracked links.
Security
Passwords and preview passwords are stored as scrypt hashes, API tokens and sign-in counters as SHA-256 hashes. Everything travels over HTTPS. Sessions end when you log out, when your password changes and when your login is deactivated. Preview links use a random address that can't be guessed from another one; add a password when a campaign needs more than that.
Your rights
You can ask us to see the personal data we have about you, to correct it, to delete it, to hand it over in a usable format, or to stop or limit using it. Write to hello@previewer.agency and we'll answer within a month. An account owner can also delete a login in the admin.
When you delete a login, its name or email address stays in the account's activity log, in the lines about what it did, until those lines are 3 months old. Ask us if you want it taken out sooner.
For content you uploaded as an agency, a request from one of your clients goes through you, and we'll help.
If you think we're getting it wrong, you can complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens.
Changes
If we change what we store or who we share it with, we'll update this page and the date at the top, and tell account owners by email before it takes effect.