Privacy policy

Trazr is a booking-management service run by Vereon Ltd ("we", "us"). This page says what Trazr holds, why, who else handles it, how long we keep it, and what you can ask us to do. Write to us about any of it at info@vereon.tech. Last updated 18 October 2026.

Who is responsible

For your account and your subscription, we decide how the information is used (we are the "controller"). For what a business puts into Trazr — its services and prices, and its customers' names, contact details, answers and bookings — the business decides, and we handle it on their behalf (we are their "processor"). If you booked something through a business's page, that business is responsible for your details; send requests about a booking to them first, and we help them answer. A business that needs a data processing agreement can ask us for one.

What we hold

• Your account: your name, email address and time zone, and your password (stored only as a one-way scrypt hash; Trazr runs its own sign-in). If you sign in with Google, Google's id for you. Whether your email is confirmed, and which businesses you belong to with what role.
• What your business puts in: services, prices, deposits, schedules and sessions, booking policies, discount codes, your bank details as you choose to show them to customers, and who on the team did what and when.
• Your customers' bookings: the name and contact details they give when booking, their answers to your intake questions, the bookings themselves with their payment and refund records, waitlist entries and enquiries. Every booking snapshots the price and session it was made at, so the record stays true even after you edit your catalogue.
• My bookings: when a customer signs in to a business's My bookings page, the one-time code we email them (kept only as a keyed hash, and usable for 15 minutes), the name and phone number they correct there, and any request they send the business to delete their data.
• Payment-proof images: the bank-transfer receipt a customer uploads. Proofs are stored privately and reached only through short-lived signed links; they are deleted on the schedule below, because a receipt doesn't need to outlive its review.
• Emails we send for you: booking confirmations, payment nudges, reminders before a session, follow-ups, cancellations and moves, waitlist offers and enquiry acknowledgements — each recorded against the booking so nothing sends twice. The same goes for WhatsApp messages when a business has turned WhatsApp on, along with what each one cost.
• A business's sending mailbox: if a business sends its emails from its own address, the sign-in that lets Trazr send as it (Google or Microsoft access tokens, or SMTP details), encrypted.
• Track and connected AI assistants: what you ask Track, his answers and the changes you approve, kept for a short while so a conversation can carry on; and which AI assistants (Claude, ChatGPT, Gemini) you have connected to Trazr. Changes made through them are recorded under your name.
• Running the service: technical logs (time, address, errors) kept to keep Trazr working and secure. We don't track the pages you visit, and there is no advertising or analytics — on the dashboard, the booking pages or the booking code on a business's website.

Why we use it, and on what basis

• To provide the service you signed up for — taking bookings, holding spaces, sending the booking emails and WhatsApp messages, billing the subscription: because it is needed to perform our contract with you or your business.
• To keep Trazr secure, prevent misuse and fix faults: because we have a legitimate interest in a safe, working service, which doesn't override your rights.
• To keep financial records: because the law requires it.

We do not sell your information, use it to advertise to you, or use it to train AI models. Your customers' details are never used to market to them.

Google user data

Trazr asks Google for as little as it can, and only when you choose to use Google:

• Signing in with Google (openid, email, profile): we read your name, email address, whether Google has confirmed that address, and Google's id for you, to sign you in or create your account. We keep no Google token afterwards.
• Sending a business's emails from its Gmail (gmail.send): we send that business's booking emails to its own customers from its address, so they appear in its Sent folder. Trazr can only send: it never reads, searches, changes or deletes anything in the mailbox. The access it needs is stored encrypted, and is deleted when the business disconnects the mailbox or is closed. You can also remove Trazr's access at any time from your Google Account's security settings.

We don't share Google user data with anyone, use it for advertising, sell it, or use it to train AI models, and no person at Vereon reads it unless you ask us to help with a problem or the law requires it. Trazr's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Track and AI

Track, Trazr's assistant, runs on Amazon Bedrock in London: your questions and the parts of your business he needs to answer them stay in the UK under AWS, are not kept by the model provider, and are not used to train any model. AI assistants you connect yourself (Claude, ChatGPT, Gemini) see what you ask them to fetch from Trazr, under their own privacy terms. Neither can reach billing, payment details, passwords, sign-in settings or customers' contact details.

Customer payments

Money for bookings moves directly between a customer and the business — a bank transfer to the business's own account, payment at the venue, or a card payment on the business's own payment page or its own Safepay account. Trazr records what the business confirms (or what Safepay reports) and stores the uploaded receipt; it never holds the money and never sees anyone's card number or bank balance.

Who else handles it

The people in your business see it according to their role. These providers handle it for us, each only as far as their job needs:

Nobody else, unless the law requires it.

Sending data outside the UK

Trazr runs in the UK (AWS London, eu-west-2), so your data mostly stays here. Stripe handles subscription billing in the EU and US, and the optional providers in the table above (Google, Microsoft, Telnyx and Meta) work where it says, only when you or a business choose them; Safepay is a business's own provider, under its own agreement with them. When data leaves the UK it is protected the way UK law requires, by the UK's adequacy regulations (including the UK–US data bridge) or by the International Data Transfer Agreement or Addendum in our contract with the provider. Ask us for details.

How long we keep it

Your rights

• See and take your data: your catalogue, bookings and customers are visible in the dashboard, and the owner and admins can export bookings and customers as CSV. A business's customers see their own bookings in its My bookings page. For a copy of everything we hold about you, write to us.
• Correct it: your own details are editable in Your profile, and the owner and admins edit the business's under Settings. A customer can correct their name and phone number in the business's My bookings page.
• Delete it: you can delete your account from Your profile, and a business owner can close the business from Settings, which deletes it and its records straight away. A business's owner or admins can erase one customer's personal details from that customer's page; the money records stay, without a name, because tax law requires it. A customer can ask the business to do that from My bookings.
• Object, or ask us to restrict how we use it: write to us.

We answer within a month. You can also complain to the Information Commissioner's Office (ico.org.uk) or, in the EU, your own data protection authority. If you are a business's customer, point your request at the business first — the booking is theirs — and we will help them answer it.

Cookies and storage in your browser

Trazr sets no advertising or analytics cookies, so there is nothing to opt into. The dashboard keeps what it needs to work in your browser: your sign-in and which of your businesses you last had open. The public booking pages and the embedded booking page track nothing. The one thing they keep is for a customer who signs in to My bookings: a secure, HttpOnly cookie that keeps them signed in to that one business for up to 30 days, removed when they sign out. Without it, a customer returns to their booking through the private link in their confirmation email.

Security

Everything travels encrypted. Passwords are stored only as one-way hashes, payment-proof images are reachable only through links that expire, and every record carries the business it belongs to, checked on every request. If something ever went wrong with your data, we would tell the Information Commissioner's Office within 72 hours and tell you without delay if it put you at risk.

Children

Trazr accounts are for businesses, and you must be 18 or over to run one. A business's customers book as guests, without accounts; a business that takes bookings for under-18s (a kids' class, say) is responsible for collecting those details lawfully.

Changes

If this page changes in a way that matters, we tell business owners by email first.