Skip to content
Legal

Privacy policy

Last updated

This explains what personal data Runavel handles, why, who else touches it, how long it is kept and what you can ask us to do about it.

Two different roles, and why it matters

Runavel handles personal data in two distinct capacities, and your rights differ depending on which one applies:

  • For studios that subscribe - the account holder's name, email and billing details - Elixon LTD is the controller. This policy describes what we do with it.
  • For a studio's own clients - the people who book tattoos, sign consent forms, and whose payments the studio records here - the studio is the controller and we are its processor. We hold that data on the studio's instructions, and we do not decide what it is used for. If you are a client of a studio and want your data corrected or erased, ask the studio; they can do it inside Runavel, and we will help them if they ask.

What we hold

  • Account: name, email address, password (hashed, never readable) and two-factor secrets.
  • Audit trail: a record of what was done in the account - who did it, when, to which record, and from which IP address and browser - including every sign-in, failed sign-in and change to how someone signs in. Personal details such as a client's name or a note's text are recorded only as having changed, never their value. The full IP address is kept, because it is what shows whether an account was used by somebody it does not belong to.
  • Studio: business name, addresses, opening hours, artist profiles and the photographs you publish.
  • Clients (entered by the studio): name, contact details, appointment history, notes, reference images, and signed consent forms - which may include health information such as allergies, medication or pregnancy, and which the studio collects for its own legal and safety reasons.
  • Payments: subscription status, invoices and deposit records. Card details are handled by Stripe and never reach us.
  • Technical: server logs, and error reports when something breaks. Error reports deliberately exclude request bodies, so form contents are never sent.

Why we hold it

  • Performing our contract with the studio - running the service it pays for.
  • Legal obligation - keeping payment and tax records, and retaining signed consents.
  • Legitimate interests - keeping the service secure, diagnosing faults, and understanding at a coarse level how the public pages are used.

Where a studio relies on consent from its own clients - for example to use a photo of their tattoo for marketing - that consent is recorded per use and can be withdrawn.

Who else processes it

We use a small number of processors, each for one job:

  • Fly.io - hosting and databases. Runavel runs in London.
  • Cloudflare R2 - file storage for photographs and consent documents, in the European jurisdiction.
  • Stripe - subscription payments and invoices.
  • Resend - sending email, such as confirmations and notifications.
  • Twilio - sending text-message reminders, where a studio has them switched on. The message and the mobile number are processed in Twilio's Ireland region.
  • Meta (WhatsApp) - delivering WhatsApp messages, where a studio has that channel switched on. The message and the mobile number reach Meta as well as Twilio, because Twilio hands the message to WhatsApp to deliver it. If a studio has not switched WhatsApp on, nothing is sent to Meta at all.
  • Error monitoring - a service we host ourselves, so crash reports do not leave our infrastructure.
  • Umami - cookieless visitor statistics, self-hosted by us, across this site and the application. It sets no cookies and does not follow you to other websites. While you are signed in it records an internal account identifier - a row id we already hold - together with your plan and your role, so that we can tell whether the product is actually being used. It never receives your name, your email address, your studio's name or anything about your clients, and pages that carry a token in their address are excluded from it altogether.

We do not sell personal data, we do not share it for advertising, and we do not use it to train machine-learning models.

Cookies

Runavel sets a session cookie so you stay logged in, and a cookie remembering whether you chose the light or dark theme. When you sign up, it also marks the browser you signed up in, for up to a week, so that confirming your address there keeps the password you chose; the mark is removed once you confirm. That is all - each is strictly necessary for the site to work as you asked it to.

The visitor statistics on our public pages are cookieless and do not identify anyone, which is why you are not shown a cookie banner. Analytics are never loaded inside the application or on a studio's private screens.

How long we keep it

  • Account data: while the account exists, and a short period afterwards.
  • Signed consent documents: 5 years from signature, which is the retention period configured for the document vault.
  • Payment records: as long as tax and accounting law requires.
  • Audit trail: 12 months for an ordinary action, and 24 months for sign-ins, credentials and other security events, then deleted. A record that belongs to no account - a failed sign-in for an address nobody has, an action by our own staff - stops naming anybody after 90 days: the address and browser are removed and the name is replaced by a code. A studio's history goes with the studio's account.

When a studio erases a client, we anonymise that person's details in place rather than deleting the records wholesale, and reference photographs are removed. Payment records and signed consents survive, because we are required to keep them and because they are evidence of what was agreed. Erasing them would put the studio at risk, not protect the client.

Security

Traffic is encrypted in transit. At rest we encrypt the health answers and signatures on a consent form, the signed consent documents themselves, the notes a studio writes about a client or a booking, what a client wrote when they enquired, dates of birth, and a guardian's details where a client was a minor. Passwords are stored hashed and are never recoverable. Two-factor authentication is available on every account and required for our own staff. Access between studios is isolated: every read and write is scoped to one account.

Our support staff can, in defined circumstances, view an account in order to help - read-only by default, time-limited, and recorded in the audit trail. A studio admin sees each session under Support access, and the record is part of the data export your studio can download. The trail is append-only and sealed so that a changed or deleted record shows, it is checked every day, and a copy of its seal is kept outside the database.

Your rights

You can ask us for a copy of your data, ask us to correct it, ask us to delete it, object to how we use it, or ask for it in a portable form. Write to support@runavel.com and we will respond within one month.

If you are unhappy with how we have handled your data you can complain to the Information Commissioner's Office at ico.org.uk. We would rather you raised it with us first.

Contact

Elixon LTD, 51 Roundmead, Bedford, United Kingdom, MK41 9HY. Privacy enquiries: support@runavel.com.