Last updated 10 November 2026.
What we hold
Everything you put into the builder, which is:
- your name, your title, your company and your email address
- your website, the label you want it shown under, and your LinkedIn address
- the brand colour you picked and the template you chose
- the photograph you uploaded and the logo file, if you sent one
- Bookings a visitor makes on a card: their name, email, phone and notes, kept with the booking.
- Messages a visitor sends from a card: their name, email, phone and the message, kept for the card owner. Archiving one puts it out of sight and does not delete it.
- Details a visitor shares from a card: their name, email, phone and note, kept for the card owner to read and download.
- Questions asked of Mark, the assistant, and its answers: a visitor's on a card, and your own in the app.
Alongside that we hold the identifiers Stripe gives us for your customer record, your subscription and the checkout that started it, and whether the subscription is currently active. We never see and never hold your card number.
A draft is saved while you are still building, before you pay and whether or not you ever do. It holds the same fields and the same uploads. That is what lets you close the tab, come back to the same address and find your card where you left it.
Your photograph
The face is found and cropped on our own server, by ordinary computer vision code running in the same process that draws your card. The photo is not sent to another company, and it is not used to train anything. The original is kept because rebuilding your card needs it.
Reading your website
If you press Import on the Brand panel, our server opens the address you typed and reads that one page, its stylesheets and one icon, to find your colours and your mark. It happens because you pressed the button, it reads only what a visitor to that page would see, and your web host sees our server arrive the way it sees any other visitor. We keep the mark only if you accept it, redrawn by us rather than stored as it arrived, and we keep the address so the field opens on it next time. Nothing else from the page is kept.
Mark, and the words written for you
Some of the service is written or answered by an AI model run by Anthropic. What is sent depends on what is being asked.
- Words for your card: your name, title, company, bio and services, with the change you asked for, the address your button opens, and the brand rules and answers you gave Mark.
- Suggestions for your card: the same, with counts of your views, bookings and messages.
- A visitor's question to Mark on your card: the question, what your card and booking page say in public, and the instructions you gave Mark about its tone and what it must not claim.
- Your own question to Mark in the app: the question, with your recent bookings, the names of the people who made them and your recent messages, so it can answer about them.
- A brief before a booking: that booking, the same person's earlier bookings and the questions they asked Mark.
- A drafted reply: the message it answers, the name of whoever sent it, and the brand rules and answers you gave Mark.
Your photograph is not sent.
What the hosting can see
Your signature is made of images served from our server, so when somebody opens an email carrying it, their mail client asks us for those files. Our web server records that request the way any web server does: a time, an address and a browser string. We use it to serve the file and to see whether the service is up.
We do not turn that into read receipts. We do not tell you, or anyone else, who opened your mail or when. There is no tracking pixel in your signature: every image in it is a visible part of the card. And most mail clients fetch images through their own proxy, so what usually reaches us is the proxy rather than your recipient.
What we count
When an image in your signature is loaded, when a link in it is followed, and what somebody does with your card: opening it, pressing a button, saving your details. We never keep the address, the browser string, the name or the email of whoever did it. Each record holds the time, the day, which link or button, the family of mail client it looks like, and a scrambled code for "the same browser, today", made with a key thrown away at midnight. It holds a country only as the hosting in front of us reports it, from the network edge that took the request, which is approximate.
Your dashboard says views, never opens or reads. A view is an image being fetched: providers prefetch and cache, so it is a trend and not a headcount. It says when your signature was last fetched, never who fetched it. Your own visits are filtered out where we can tell they are yours. You can switch the counting off, leave out visitors in the EU, EEA, UK and Switzerland, or keep the detail for a shorter time; the switches are on Settings.
Connecting your Gmail
If you press Connect Gmail, Google gives us one permission
— gmail.settings.basic, which can write the
signature in your Gmail settings — and your address, so the
screen can say which mailbox is connected. We cannot read your mail
with it, and we do not ask for a permission that could. What we store
is that address and the two tokens Google issues, encrypted on our disk
with a key that is not kept in the database. We write your signature
into the send-as address you pick and nothing else. Press Disconnect,
on your signature or on Settings, and we take the connection off your
account and ask Google to cancel the permission. A signature update
that was already under way at that moment may still finish. If Google
does not answer we ask again, about once an hour, 24 times; the tokens
are deleted when Google confirms and stay encrypted on our disk if it
never does. You can cancel the permission yourself at any time from the
security page of your Google account, which does not depend on us.
The signature already in your Gmail stays there until you change
it.
SelfMark's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Payments
Stripe takes the payment. Card details go from your browser to Stripe and never touch our server. What we keep is the set of ids Stripe hands back, which is what lets Manage billing open your own billing page. Stripe holds its own record of the payment under its own privacy notice.
Cookies and tracking
Cookies, and only if you sign in. One keeps you signed in for 30 days and holds nothing else. Signing in with Google sets one for ten minutes that carries only what proves the trip through Google came back to the browser it left. When that Google address still has to be confirmed through its mailbox, another holds the address and Google's id for it, signed, for fifteen minutes. Pressing Connect Gmail sets a second one for ten minutes, of the round-trip kind. Nobody who receives your mail or opens your card is ever given one. No analytics script, no tag manager, no advertising pixel. Your draft lives on our server against the address in your browser bar, which is why that address is worth keeping.
How long we keep it
The records above keep that detail for 400 days. A customer who chose 30 or 90 days on Settings gets that window instead. Every hour a job sums each finished day into a plain count and deletes detail older than 400 days; the scrambled code and the country go with it. Your order and its files stay while your subscription runs, because they are what your signature is made of. An unpaid draft that was never saved to an account goes after two days; one saved to your account stays until you ask.
Questions asked of Mark go after 30 days. A question Mark handed on to you as a message is kept as a message. Bookings, messages and shared details stay until you, or the visitor they came from, ask us to delete them. The record of changes made to an account, and the drafts Mark wrote for you, are kept for as long as the account is, because they are what lets a change be traced and undone. Backups of the disk are kept for five days. For anything you want gone sooner, the next part is the fix.
Getting it deleted
Write to support@selfmark.io from the address on your card and ask. We delete the order, the uploads and the rendered images. Your signature stops working at that point, in the same way it does when a subscription ends, except that this one does not come back.
A visitor who booked, wrote or shared details through somebody's card can write to the same address, and we delete what they sent. While your plan includes them, your contacts and your numbers can be downloaded as files from the app. After a subscription ends, write to us and we send them to you.
Who else gets it
Nobody. We do not sell it and we do not share it for anybody's advertising. A few companies touch it because the service cannot run without them. Stripe takes the payment and holds what it needs for that; when you charge for a booking, the payment goes to your own Stripe account, and Stripe, not us, holds your visitor's payment details. The AI model behind Mark and the words written for your card is run by Anthropic; what is sent there is listed under Mark above. Google is involved only if you sign in with Google or connect Gmail. Receipt pages load their typeface from Fontshare, so a browser opening a receipt asks that service for the font file, and it sees that request the way any web server does. The service itself runs on hosting rented from Fly.io, in the United States, so that company holds the disk everything sits on, which is true of every website you have ever used and is worth saying rather than leaving out.
Talking to a person
One address, read by a person: support@selfmark.io.
See also Terms, which covers what the subscription pays for and what happens when it ends.