1. Two different sets of data
This policy covers two things that look alike and are not, so it is worth being clear at the top.
Your studio's data — your account, your billing, your emails to us. Here we are the controller: we decide what to do with it, and this policy is the answer.
Your clients' data — the people who book with you, their photos, their phone numbers, their appointments. Here you are the controller and we are your processor: we only do what you tell us. The terms of that are in the Data Processing Addendum.
If you are a client who booked a tattoo through a page on inktok.pro, the studio you booked with is who holds your data. Ask them, and they can correct or delete it. We will help them do it.
2. What we collect about your studio
When you register
- Studio name and the address of your booking page
- Your name and email address, and a password we store only as a hash
- Your billing entity: sole trader, self-employed or company, with the registration number, address and VAT number where that applies
- If you arrived from one of our ads or links, which one: the campaign name in that link (for example
utm_source=instagram), the ad platform's click id, or the site that linked to us. It is read from the address you landed on, kept only in the open page — never in a cookie or on your device — and saved with your account when you register. The one exception is a link from one of our sales people (inktok.pro/r/…): its code is kept in theinktok_refcookie for 60 days, so they are credited if you register later, and the cookie is deleted when you do
While you use it
- What you put in: prices, opening hours, portfolio images, artists, bookings
- Server logs — IP address, browser, the page requested and when. Kept 30 days, for security and for working out what broke
- Emails you send us, and what we answered
Payment details
We never see your card. Stripe takes the payment and tells us only that it succeeded, the amount, and the last four digits for your invoice.
What we do not do
There is no analytics script on this site, no advertising pixel, no third-party tracker and no profiling. We do not sell data to anybody, and there is nobody to sell it to.
One thing goes to an ad platform, and only if you came from its ad: if you clicked one of our ads on Facebook or Instagram and then registered, our server tells Meta that this click led to a sign-up, so Meta can show our ads to people like the ones who sign up and stop spending on the rest. It sends the click id Meta put in the link, your email address in hashed form (SHA-256, which Meta can only match against an address it already knows), and the IP address and browser of the registration. Nothing is loaded in your browser and nothing is stored on your device to do this. If you did not come from a Meta ad, Meta is told nothing. To object, write to us and we will stop and ask Meta to delete it.
3. Why we are allowed to
| What | Why | Legal basis |
|---|---|---|
| Account and studio data | To give you the service you signed up for | Performance of a contract |
| Billing details | Invoices, and the tax law that requires them | Legal obligation |
| Server logs | Security, abuse, debugging | Legitimate interest |
| Which ad or link you came from | Knowing which of our ads bring studios, so we stop paying for the ones that do not | Legitimate interest |
| Telling Meta that its ad led to your sign-up (only if you came from one) | So our ad budget goes to ads that bring studios | Legitimate interest — object any time |
| Service emails | Trial ending, payment failed, something changed | Performance of a contract |
| Product news | Telling you about new features | Consent — and one click to stop |
5. Text messages to clients
A client who books gives their phone number on the studio's own booking page and ticks that they are willing to be texted. Nothing is ticked for them, and without the tick no text is sent at all — the client hears from the studio by email only. The number is used for that booking and for nothing else: we do not build a marketing list, and neither we nor the studio can send promotions through it. Usually two to four texts are sent per booking. Message and data rates may apply.
What a client may receive, and nothing besides:
- a reminder the evening before the appointment;
- notice that the studio has sent a price and dates to accept;
- confirmation that a booking is made, or that it has been called off;
- a link to the consent form the studio needs signed before the session;
- if they asked to be told, notice that an earlier slot has come free.
Every one of these is also sent by email, so a client who wants no texts at all loses nothing. They can stop them by replying STOP, by telling the studio, or by asking us — and the studio can switch texts off for its whole client list under Settings → Notifications. Replying HELP returns how to reach us.
Messages are carried by Twilio. They see the number and the text of the message, which is why the text carries no price, no health information and no more of a name than it has to.
6. Google Calendar
An artist can connect their own Google Calendar so that their InkTok diary and their calendar stay in step. Nothing is read until they connect it, and they choose the Google account themselves. InkTok asks Google for access to their calendar (https://www.googleapis.com/auth/calendar) and uses it for this sync only.
What we read, and what we keep:
- Upcoming events, when you connect. We list them so you can choose which are tattoo bookings. Only the ones you choose are imported, as InkTok bookings with the time, the name and the price you confirm.
- Busy times, while you stay connected. Your other events block those times on your booking page so clients cannot book over them. For each we keep its start, its end and its title — or only “Busy” if the event is private. Descriptions, attendees and locations are not stored.
What we write:
- an event for each confirmed booking, which we update or remove if the booking moves or is cancelled;
- we change only events that belong to an InkTok booking, and remove another event only when you ask us to from within InkTok.
InkTok's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Calendar data is used only to provide the sync to the artist who connected it. It is not used for advertising, not sold, not used to train AI models, and not shared with anyone except as needed to run the service, to comply with the law, or with your consent. No person at InkTok reads it unless you ask us to for support, or the law requires it.
You can disconnect at any time in Bookings → Sync. That deletes our access to your calendar and the busy times copied from it. Bookings you imported stay in InkTok as bookings, and events we already added stay in your calendar until you remove them. You can also revoke access at myaccount.google.com/permissions.
7. Data outside the EU
Your database and your uploaded images live on servers in Germany. Some of the companies above are American, which means some data reaches the United States. Where it does, the transfer is covered by the European Commission's Standard Contractual Clauses, or by the provider's certification under the EU–US Data Privacy Framework.
8. How long we keep it
| What | How long |
|---|---|
| Your account and everything in it | While the account is open, then 90 days |
| Invoices and accounting records | 5 years, because Latvian tax law says so |
| Server logs | 30 days |
| Support email | 2 years |
| Backups | Rolling 30 days, then overwritten |
You can ask us to delete the account sooner than the 90 days, and we will — except for the invoices, which we are not allowed to throw away.
9. What you can ask for
Under the GDPR you can ask us to:
- Show you what we hold about you
- Correct anything wrong — most of it you can edit yourself in the panel
- Delete it
- Export it in a machine-readable file
- Stop or limit a particular use, including product emails
- Object to anything we do on the basis of legitimate interest
Write to privacy@inktok.pro. We answer within 30 days, and it costs nothing.
If you think we have got it wrong, you can complain to the Latvian Data State Inspectorate (Datu valsts inspekcija) or to the authority in the country you live in. We would rather you told us first.
10. Keeping it safe
- Everything travels over HTTPS; nothing is served unencrypted
- Passwords are stored as bcrypt hashes — we cannot read yours, and neither can anyone who takes the database
- Each studio's data is separated at the query level: one studio's login cannot reach another's records
- Backups are encrypted and kept apart from the live database
- Access to production is limited to the people who need it
If something goes wrong anyway and personal data is exposed, we will tell the supervisory authority within 72 hours and tell you without undue delay.
11. Children
InkTok is for professionals and is not meant for anyone under 18. We do not knowingly collect data from children. If a studio's client is a minor, that is the studio's responsibility under the law that applies to them.
12. Changes
If we change this policy in a way that matters, we will email you before it takes effect. The date at the top always says which version you are reading.
Who you are dealing with
InkTok is operated by Amare Baltic SIA, a limited liability company registered in Latvia.
- Company
- Amare Baltic SIA
- Registration
- 40203563664 · Commercial Register of the Republic of Latvia
- VAT number
- LV40203563664
- Registered address
- Kluba iela 13A-8, Aloja, Limbaži Municipality, LV-4064, Latvia
- hello@inktok.pro