Privacy notice

Your right to object

If we use your data because we have a legitimate interest, you have the right to object at any time, on grounds relating to your situation. We will then stop, unless we have compelling legitimate grounds that override your interests, rights and freedoms, or we need the data to bring or defend a legal claim.

You can also object at any time to our use of your data for direct marketing, and we will then stop using it for that.

Section 2 shows which uses rest on a legitimate interest. They include the records our server sends to PostHog, the click records of audit report pages and Cloudflare Web Analytics, which your cookie choice does not switch off. To object, contact us as section 1 explains.

1. Who we are and how to contact us

Tamazia Ltd is the controller of the personal data described in this notice. We are a compliance-first SEO and AI search agency for regulated firms.

Tamazia Ltd is registered in England and Wales, company number 17295579. Registered office: 124 City Road, London, EC1V 2NX.

To ask about this notice, use your rights or complain, email contact@tamazia.co.uk or write to Tamazia Ltd, 124 City Road, London, EC1V 2NX. For a complaint, put "Complaint" in the subject line.

2. What we collect and why

With the contact form, the booking page form, an audit request and the briefings sign-up we also record the time, the full address of the page you sent it from, your browser type, the country your connection comes from, a shortened IP address (the last part removed) and the result of our email check. In our database the IP address is kept only as a scrambled code made with a secret value, or not at all. With the plan enquiry form we record the country your connection comes from, your browser type and the page you came from, but no IP address.

Our legal basis for the contact form, the booking page form, audit requests, plan enquiries, bookings and the emails you send us is our legitimate interest in replying to people who contact us about our work and giving them what they asked for (UK GDPR Article 6(1)(f)). Our legal basis for the briefings is your consent (UK GDPR Article 6(1)(a)).

When you pay us, we use your details to take the payment and deliver what you bought, because that is needed for our contract with you (UK GDPR Article 6(1)(b)). We keep the payment record because the law requires a company to keep accounting records of the money it receives (UK GDPR Article 6(1)(c)).

Our legal basis for dealing with a rights request or a complaint is that the law requires us to (UK GDPR Article 6(1)(c)). Keeping your address on our do-not-email list after you object to direct marketing is how we meet our legal duty to stop (UK GDPR Article 6(1)(c) and Article 21(3)). Keeping a record of each unsubscribe, which for our outreach emails includes your IP address and browser type, rests on our legitimate interest in being able to show that we stopped (UK GDPR Article 6(1)(f)).

Our legal basis for the records our server sends to PostHog and for Cloudflare Web Analytics is our legitimate interest in knowing which pages and campaigns lead to enquiries and bookings and how fast our pages load (UK GDPR Article 6(1)(f)). Our legal basis for the click records of audit report pages is our legitimate interest in knowing which reports lead to bookings (UK GDPR Article 6(1)(f)). The details in them are about a firm's own report, but they can point to the person we prepared the report for, so we treat them as personal data. Our legal basis for Google Analytics and PostHog in your browser is your consent (UK GDPR Article 6(1)(a)). Our legal basis for the security data is our legitimate interest in keeping the site and our forms secure (UK GDPR Article 6(1)(f)).

You do not have to give us any personal data. If you do not give us an email address, we cannot reply.

No decision that has a legal or similarly significant effect on you is made by automated means alone. Our forms check whether an email address can receive mail, but that check never refuses a form. If your message contains certain words, such as "budget" or "urgent", the alert we receive is marked as high priority; that changes only how the alert is shown to us.

3. What happens when you send a form

When you send the contact form, the booking page form (with the services or packages you tick there), an audit request or the briefings sign-up:

1. Cloudflare receives it, and our form store, which runs on Cloudflare, keeps a copy.
2. Our server asks an email checking service whether your address can receive mail (section 5 names them).
3. A copy goes into our database, run by Neon: into the table of form submissions and into our table of leads. The table of leads is the same one our outreach emails are sent from.
4. Resend sends you an acknowledgement from an address ending @tamazia.in. Resend also sends us an alert with everything you entered, to a personal Gmail mailbox that our founder reads.
5. An alert goes to our founder's Telegram chat with your name, company, email address, sector, country, shortened IP address, device type, the page you sent the form from and the first 800 characters of your message.
6. Our server sends Slack, our team chat service, an alert with the same details and the full form.
7. For the contact form, the booking page form and audit requests, our server sends PostHog a record that a form was sent (section 4).

When it is switched on, a copy of the contact form, the booking page form or an audit request (your name, email address and, where the form asks for them, company, sector and message) also goes into our enquiries database in Notion.

When you send the plan enquiry form on an audit report page, it goes into a table of plan enquiries in our database, and an alert with what you entered, your country and your device type goes to the Gmail mailbox, the Telegram chat and Slack. The form also sends the address of the report it was sent from, so the enquiry can be linked to that report and to the record of the person we prepared the report for. This form does not ask for your email address and sends you nothing. Once it is saved, the page loads the booking calendar with your firm name and your answers passed in, so you can book the call without typing them again.

When the booking calendar tells our server about a booking, we keep a record in our form store with your name, email, the call you chose, its start and end time, whether it was booked, rescheduled or cancelled, and the booking details the calendar sends, including each attendee's time zone. An alert with your name, email, the call and its times goes to the Gmail mailbox, the Telegram chat and Slack, and our server sends PostHog a record of the booking (section 4).

When Stripe tells our server about a completed payment, we record in our database the payment and customer references Stripe gives us, your email, what you bought, the amount and the currency, and the company name and audit website if Stripe passes them on. An alert with your email, what you bought, the amount, and the company name and audit website if given, goes to the Telegram chat and Slack.

If you use the unsubscribe link in one of our outreach emails, your address goes on our do-not-email list in our database, and our form store keeps a record of the unsubscribe as described in section 2.

4. Analytics

In your browser, only with your consent

We use two analytics tools in your browser, and only if you choose Accept all or switch Analytics on in the cookie banner:

• Google Analytics 4, from Google. It counts visits and which pages are read. We tell Google that advertising storage and advertising use of the data are refused.
• PostHog, run in PostHog's EU cloud. It records page views, clicks, when a form is started or sent, and session replays of how pages are used with every typed field hidden. It does not receive your email address, your name or the website you enter. After a Compliance Radar purchase, it links that browser's visits to the Stripe customer number of the purchase.

If you choose Reject all, or make no choice, neither loads. If you withdraw consent later, we tell them to stop and delete what they stored in your browser. If your browser sends a Global Privacy Control signal and you have not yet made a choice, we record Reject all. The cookie policy lists every item by name.

On our main site pages, whatever you choose

Cloudflare Web Analytics loads on every page built from our main site template, whatever you choose in the cookie banner. It stores nothing in your browser. It sends Cloudflare a record of each page load and how long the page took to load.

Records our server sends to PostHog

Separately from your browser, our server sends PostHog a record when you send the contact form, the booking page form or an audit request, and when the booking calendar tells us about a booking. The record uses a random identifier, not your email address. For a form it carries which form you sent, your sector, where the form asks for it, and whether you gave a company name; for a booking it carries the call you chose, its start time and, when you booked from an audit report page, which report. Nothing is stored in or read from your browser for this, so your cookie choice does not switch it off.

When an audit report page we prepared is opened, our server adds one to the count of openings and records the time of the latest opening, in the table of audit reports in our database. Where we prepared the report for a named person, that table links the report to the record we hold about that person, so we can see whether and how often the link we sent was opened, and when it was last opened. The count does not show who opened the link. Our server also sends PostHog a record of each opening, identified by the firm's website address.

On audit report pages

Audit report pages show no cookie banner, and your browser sends nothing to PostHog from them. When you send the form on an audit report page, our server records the request as described above.

When you click a booking button or an add-on button on an audit report page, your browser also sends a short record of the click to our own server, which keeps it in our form store for 90 days. Section 2 lists what it holds. It holds no cookie, IP address or visitor ID. Nothing is stored in your browser for this, so your cookie choice does not switch it off. We keep it to know which reports lead to bookings. You can object to it, as explained at the top of this notice.

5. Who receives your data

Service providers

These companies provide services to us and receive your data in doing so. They act only on our instructions, under data processing terms in our contract with each of them. The booking calendar acts for us when it collects your booking.

• Cloudflare hosts the site, runs our form store, loads the Cloudflare Turnstile check on our pages, routes email sent to @tamazia.co.uk and runs Cloudflare Web Analytics.
• Resend sends our acknowledgement, alert and data request emails.
• Neon runs our database: the tables of form submissions, leads, plan enquiries, audit reports and payments, our do-not-email list and the record of the outreach emails we have sent. The database is held in Frankfurt, Germany.
• Google runs Google Analytics 4, only with your consent.
• PostHog runs the analytics in your browser, only with your consent, and receives the records described in section 4.
• Slack receives our internal alerts about forms, bookings and payments.
• Hunter and NeverBounce check whether an email address can receive mail. Our code can also send the address to Reoon or ZeroBounce for the same check, when we switch them on.
• Cal.com runs the booking calendar on our booking and contact pages and on audit report pages, and tells our server about each booking.
• Notion holds our enquiries database, when the copy described in section 3 is switched on.

Email sent to our @tamazia.co.uk addresses passes through Cloudflare and is forwarded to a mailbox run by an email provider.

When you book, Cal.com collects what you enter and sends it to us. Its own privacy policy covers its calendar and its cookies; our cookie policy names those cookies.

Other companies that receive your data

Alerts about forms, bookings and plan enquiries go to a personal Gmail mailbox run by Google. Alerts about forms, bookings, plan enquiries and payments go to a Telegram chat run by Telegram Messenger Inc. Both are read by our founder. Google and Telegram handle these copies under their own terms as independent companies, not under our instructions.

If you pay for an add-on from an audit report page, you pay on a page run by Stripe, and Stripe's own privacy policy covers that page. Stripe acts for us in taking the payment and also as an independent company for its own security, legal and fraud checks, under that policy. We never see your card number.

We do not sell your data and we do not share it for advertising. We disclose it to public authorities only when the law requires us to.

6. Data sent outside the UK

Several of the companies in section 5 are based in the United States or hold data there, so your data leaves the UK. You can ask us how each transfer is protected, using the contact details in section 1.

Transfers to countries in the European Economic Area, which hold our Neon database (Frankfurt), PostHog's EU cloud (Frankfurt) and Hunter's servers (Belgium), are covered by UK adequacy regulations. Transfers to a US company certified under the UK Extension to the EU-US Data Privacy Framework are covered by UK adequacy regulations as well: Cloudflare, Google, Resend, Slack, Stripe, Cal.com and Neon (through its parent company Databricks) are certified. Resend's contract with us also includes the UK Addendum to the EU standard contractual clauses, and for PostHog's support staff in the United States we rely on the UK Addendum in our contract with PostHog. NeverBounce, a ZoomInfo company in the United States, checks whether an email address can receive mail, and we confirm the safeguard for that transfer on request. You can ask us for a copy of any of these safeguards (see section 1).

Google holds Gmail data on servers around the world, including the United States. Telegram Messenger Inc. says that the data of accounts opened from the UK or the EEA is stored in its data centres in the Netherlands.

7. How long we keep it

Our systems delete these records at fixed times:

• Each contact form, booking page form, audit request, briefings sign-up and booking record in our form store: 2 years after it is stored or last updated.
• The index records that let us find your briefings sign-up or booking by your email address, which hold the address: 2 years.
• The record of an unsubscribe in our form store: 13 months.
• The record that we erased your data: 7 years. It holds a shortened code made from your email address, not the address itself, but anyone who knows the address can match the code to it.
• If the email confirming an erasure fails to send, a record for retrying it, which can hold the first 16 characters of your email address: 7 days.
• Reports your browser sends us about blocked content and network errors: 30 days.
• The record of a click on a booking button or an add-on button on an audit report page: 90 days.
• The link to an audit report we prepared stops working at the expiry date set when we prepared it.

The other copies are the rows in our Neon database (form submissions, leads, plan enquiries, audit reports and the record of their openings, payments and the do-not-email list), the alert emails in the Gmail mailbox, the Telegram chat and Slack, and the records in PostHog. Our website code does not delete these; we delete them ourselves on this schedule:

• Enquiries, audit requests and plan enquiries that do not lead to work: 2 years from our last contact with you, in every copy.
• Audit reports we prepared for a named person, and the record of how often and when each was opened: the same 2 years from our last contact with that person.
• Records about clients and their staff: 6 years after the engagement ends.
• Payment records: 6 years after the end of the accounting period the payment falls in.
• Briefings subscription: until you unsubscribe, then deleted within 30 days except for your place on our do-not-email list.
• Your address on our do-not-email list: for as long as we send marketing email, so that your objection keeps working.
• Rights requests, complaints and our replies: 6 years after we close them.
• We keep no logs of visits ourselves. Cloudflare handles request data under its own retention terms.
• Google Analytics event data: 2 months, the shortest setting Google offers.
• PostHog event data, from your browser and from our server: the period of our PostHog plan, which PostHog publishes as one year on its free plan and seven years on a paid plan.

8. Your rights

You have the right to ask for a copy of your data, to have it corrected or erased, to restrict our use of it, and to receive it in a portable form. Some of these rights depend on the legal basis we rely on, and we will tell you if one does not apply. Your right to object is set out at the top of this notice.

You can withdraw your consent at any time. Withdrawing does not make what we did before unlawful. To stop the briefings, reply with the word UNSUBSCRIBE to the email that confirmed your subscription, or contact us as section 1 explains. Each briefing has an unsubscribe link at the bottom. For analytics, use "Manage cookies" in the site footer.

To use any right, contact us as section 1 explains. We may ask you to confirm who you are before we act, and the time limit then starts when you have done so. We reply within one month of receiving your request. If a request is complex, or you send several, we can extend this by two more months, and we will tell you why within the first month.

9. Complaints

You can complain to us. We will acknowledge your complaint within 30 days of receiving it, look into it and tell you the outcome. To complain, contact us as section 1 explains.

You also have the right to complain to the Information Commission (the ICO), the UK data protection regulator. You can do this online at ico.org.uk/make-a-complaint.

If the EU GDPR applies to our use of your data, you can also complain to the data protection authority in the EU or EEA country where you live or work.

10. Security

tamazia.co.uk is served only over HTTPS, and browsers are told never to load it any other way. A content security policy limits the places our pages can load scripts from. Our contact, booking page, audit and briefings forms screen out automated submissions with hidden trap fields and a timing check. Form records are seen only by people who work for Tamazia and by the companies named in section 5 that hold them.

11. Changes to this notice

When we change how we use personal data, we update this notice and the date at the top.