Privacy notice
This notice describes what personal data the site collects today, what it is used for and on what legal basis, how long it is kept, who it is shared with, and what rights you have. The description follows the code that actually runs: what the code does not do is not described, and what it does is described even where it is unflattering.
Updated:
Who is the controller?
The controller is AURÉLIA HOLDING Kft. (registered seat: 1025 Budapest, Szalamandra út 44. Fsz. 1., Hungary; company registration number: 01-09-431118; tax number: 32568783-2-41). The full set appears on the legal notice page. For data protection matters you can reach us at support@aureliadigitalsystems.com, or by telephone on +36 30 985 7727.
What we collect
There are two forms on this site that send us personal data: the free digital assessment form and the contact/quote form. Aurelia AI, the chat assistant, has its own section below. Simply browsing the site creates no entry in our own database. Two things happen beyond that: our hosting provider, Vercel, keeps logs of the requests it serves (see "Who we share the data with"), and — only if you allow it — we measure visits, as described under "Measuring visits" below. The lists below are the actual fields, not a summary of them.
The digital assessment form
- Your name
- Company name
- Email address
- Phone number — optional
- Your company website address, or an indication that there isn't one
- Industry
- Employee size band
- The business goals you select
- The assessment modules you request
- The services you are interested in
- Your indicated digital investment band
- Your timeframe
- A free-text description of your situation — up to 2,000 characters, optional
- Preferred contact method
- The fact that you acknowledged the privacy notice
- Whether or not you gave marketing consent
- Your return-on-investment scenario — only if you explicitly click to attach it. The calculator sends us nothing on its own.
The contact and quote form
- Your name
- Company name
- Email address
- Phone number — optional
- Your company website address — optional
- Your message — between 10 and 2,000 characters
- The services the enquiry concerns
- Preferred contact method
- Whether the enquiry is a quote request
- The fact that you acknowledged the privacy notice
- Whether or not you gave marketing consent
What the system records alongside the form
- The time of submission and the language version you used.
- The path you arrived on, the referring page address, and campaign parameters — utm_source, utm_medium, utm_campaign, utm_content and utm_term. These are stored as the browser sent them, capped in length.
- The identifying string your browser sends (the user agent), capped at 300 characters, in the form submission log only.
- A salted, truncated hash of your IP address. The raw address is never stored — see the next section.
- A technical key derived from the content of your submission, which stops a form sent twice from creating two separate enquiries.
- A normalised form of the company name, and the domain inferred from the website address or business email you gave. This is what links a later enquiry from the same business to the earlier one. Free-mail domains are never stored for this purpose.
- In the consent record: the exact wording shown to you, where the consent was given, in which language, and when. Without this a consent could not be evidenced afterwards.
- A short internal timeline entry noting when the enquiry arrived and which form it came from.
The forms contain a hidden field that no person sees. If it arrives filled in, we treat the submission as automated and reject it. Its content is not stored.
Figures you type into the return calculator stay in your browser only. If you click to attach them, they are placed in your browser’s session storage, and they reach us only if you then go on to submit the assessment form.
Why we do not store your IP address
We combine your IP address with a secret value known only to the server (a salt), take a SHA-256 hash of the two, and store only the first 32 characters of that. The raw address never reaches the database. That gives us enough to rate-limit submissions and recognise abuse, while the stored value cannot be reversed by working through the IPv4 space, because guessing gets nowhere without the salt.
If the salt is not configured on the server, no address value is stored at all: the field stays empty. Rate limiting then applies to the whole site collectively, which is stricter but involves less data.
Measuring visits
We count page views with Vercel Web Analytics — and only if you allow it. The first time you visit, a small panel asks. Until you answer, and if you decline, the measurement script is not loaded and nothing is sent. You can change your answer at any time on the cookie notice page, and the change takes effect straight away.
What measurement sends with each page view
- The time of the page view.
- The address of the page, without its query string. The only part of the query string that is kept is the campaign tags: utm_source, utm_medium, utm_campaign, utm_content and utm_term.
- The address of the page you came from, if your browser passes it on.
- An approximate location — country, region and city — which Vercel works out from the request.
- Your browser and operating system, with their versions, and the type of device: mobile, tablet or desktop.
- The version of the measurement script.
According to Vercel’s own documentation, Web Analytics sets no cookies. Vercel tells visitors apart by a hash created from the incoming request, and discards the visitor session after 24 hours. What we see is aggregated: counts of page views and visitors, broken down by the items above. The dashboard offers no way to look up a particular person’s visit, and we do not connect these counts to form submissions or conversations.
Measurement data is processed by Vercel Inc. as our processor, and may be transferred outside the European Economic Area, to the United States; the safeguards for that are set out under "Who we share the data with".
Measurement data is not stored in our own database, so it is governed by Vercel’s own retention rules rather than by the 90-day deletion described below. Vercel’s documentation gives no deletion date: it states the period for which measurement data is guaranteed to be stored and viewable — which depends on the Vercel plan — and says Vercel may keep the data for longer. According to Vercel’s privacy documentation, the recording of data points is anonymous: they are not tied to an individual or an IP address, and the service collects no personal identifiers that could follow a visitor across websites.
What we use the data for
- Answering your enquiry and, where you ask for one, preparing a quote.
- Preparing and sending the free digital assessment. Félix Tarnóy reviews each assessment personally.
- Keeping one coherent client relationship record, so that an earlier question and a later assessment request belong to the same relationship rather than to two separate files.
- Protecting the forms against automated and abusive submissions — this is what the rate limiting and the IP hash are for.
- Being able to evidence consent: what you accepted, when, in what wording, and from where.
- Diagnosing faults: a stored copy of the submitted payload lets us investigate a processing error without asking you to fill the form in again.
- Seeing, in aggregate, which pages are read and where visitors arrive from — only if you have allowed visit measurement.
There is no automated decision-making and no profiling. Assessments are written by a person.
The legal basis for each use
- Answering your enquiry, preparing a quote or the free assessment, and Aurelia AI’s replies — steps taken at your request before entering into a contract (GDPR Article 6(1)(b)). Where you write on behalf of a company, our legitimate interest in answering and handling the company’s enquiry (Article 6(1)(f)).
- The client relationship record, while you are our client — performance of the contract (Article 6(1)(b)), or, where the contract is made by a company you act for, our legitimate interest in working with the company’s contact person (Article 6(1)(f)).
- Linking an earlier enquiry with a later one — our legitimate interest in answering consistently, without you having to repeat yourself (Article 6(1)(f)).
- Protection against automated and abusive submissions — the rate limiting, the IP hash, the hidden field and the tool call log, and the hosting provider’s request logs: our legitimate interest in keeping the site and its forms secure (Article 6(1)(f)).
- Diagnosing faults from the stored copy of a submission — our legitimate interest in fixing a processing error without asking you to fill the form in again (Article 6(1)(f)).
- Evidencing consent — compliance with a legal obligation (Article 6(1)(c)), because Article 7(1) requires us to be able to demonstrate consent.
- Marketing email and visit measurement — your consent (Article 6(1)(a)).
- Emails to our mailboxes and WhatsApp messages — according to what they are about: an enquiry has the same basis as the forms, and answering a data protection request is a legal obligation (Article 6(1)(c), Articles 12 to 22).
Where we rely on legitimate interest, you may object to the processing at any time — see "Your rights". Giving your details is voluntary: no law or contract requires it, but without a form’s required fields we cannot answer the enquiry.
What we ask your consent for
We ask for your consent, specifically, for two kinds of processing, and carry out neither without it. One is marketing email: a separate tick box on the forms, empty by default, asks for it, and no such email is sent at all today — for now the consent is only recorded. The other is visit measurement, which the panel on your first visit asks about. Either consent can be withdrawn at any time, free of charge, and withdrawal does not affect the lawfulness of processing before it.
How long we keep the data
Data held in our own database is kept for no more than 90 days; where a shorter period applies, the shorter one does. Two things are kept longer: a marketing consent still in force, until you withdraw it, and the record of a client relationship, while it lasts — both below. Deletion is carried out by the database itself, automatically and on a schedule: it does not depend on anyone remembering to start it.
- Enquiries and assessment requests — the content of the enquiry or assessment (your message, your assessment answers, any calculator scenario you attached, and the route you arrived by), the form submission log (with the stored copy of the submitted data, the IP hash and your browser’s identifying string), and the internal timeline entries: deleted 90 days after they were created.
- Contact and company details — your name, email address, phone number and preferred contact method, and your company’s details, are reused by any later enquiry you make, so that it belongs to the same relationship. They are therefore deleted 90 days after your latest enquiry, not your first — and your contact details are kept longer only while a marketing consent of yours is in force (see below).
- Acknowledgement of the privacy notice — this is not a marketing consent, only a record that you were given this notice, on a form or in an Aurelia AI conversation. It is deleted with the enquiry, after 90 days.
- Marketing consent — the consent record is kept for as long as the consent is in force, that is, until you withdraw it. Because a consent proves nothing without the email address it was given for, your contact details — your name and email address and, if you gave them, your phone number and preferred contact method — are kept for that time too. Everything else about you — the text of your enquiry, your form submissions, the internal timeline, your assessment answers and your company’s details — still goes after 90 days. Once you withdraw, the entries recording the consent and its withdrawal, with the contact details they belong to, are kept for a further 90 days and then deleted.
- Client relationships — if an enquiry leads to working together, the record of it — the enquiry, your assessment answers, the internal timeline, and the contact and company details — is kept for as long as you are our client, and deleted 90 days after the relationship ends. The form submission log still goes after 90 days.
- Emails to our mailboxes — deleted within 90 days of arrival, unless the correspondence leads to a client relationship: then it is kept while the relationship lasts, and deleted within 90 days of its end.
- Aurelia AI conversations — 30 days from the last message; see the section on Aurelia AI below. Even a conversation that is still going on is not kept for more than 90 days from its start.
- Rate-limiting traces — 25 hours. A job that runs every hour deletes them.
The job that deletes enquiries, assessment requests and consent records runs once a day, as does the one that deletes conversations, so a record can outlast its period by up to a day. The consent record is append-only: a withdrawal is a new entry rather than an overwrite of the earlier one. That keeps the history of a consent auditable, and it records the time of the withdrawal from which the period above is counted.
A deleted record can survive in the database provider’s daily backups for up to 7 more days. Backups are used only to recover from a failure, and if one ever had to be restored, the daily deletion would remove anything past its period again.
Where a law requires a document to be kept for longer — accounting records, for example, which Hungarian accounting law requires to be kept for at least eight years — that document is kept for the period the law sets.
Vercel’s request logs and Vercel Web Analytics measurement data are not stored in our own database; they are governed by Vercel’s own retention rules — for measurement data, see "Measuring visits". Conversations on WhatsApp are covered under "If you message us on WhatsApp".
Who we share the data with
The providers below process personal data on our behalf, as processors. For each one we give what it does, where it has its seat, and where the processing takes place.
- Vercel Inc. (seat: United States) — hosting and the content delivery network for the website; it keeps logs of the requests it serves. The server-side functions — including form processing and Aurelia AI — run in Frankfurt, Germany. Vercel Web Analytics visit measurement is also provided by Vercel, and only with your permission.
- Supabase Pte. Ltd. (seat: Singapore) — the database that stores enquiries, assessment requests, the consent record, Aurelia AI conversations and rate-limiting traces. The database server is in Dublin, Ireland, inside the European Union.
- Anthropic Ireland, Limited (seat: Dublin, Ireland) — for Aurelia AI only: what you type to the assistant is sent through Anthropic’s application programming interface (API) to its language model to produce the reply. The model runs in the United States. Anthropic deletes what it receives and returns through the API within 30 days, unless the law or the enforcement of its usage policy requires it to keep it longer.
- Zoho Corporation B.V. (seat: the Netherlands) — the support@aureliadigitalsystems.com, info-@aureliadigitalsystems.com and sales@aureliadigitalsystems.com mailboxes. Emails sent to those addresses, including data subject requests, are held there, in Zoho’s data centre in the European Union.
- Plus Five Five, Inc., which operates the Resend email service (seat: United States) — when you submit a form, it sends us an email notifying us of the submission. The notification contains what you entered in the form, such as your name, company, email address, phone number and message, and goes to our info-@aureliadigitalsystems.com or sales@aureliadigitalsystems.com mailbox with your email address as the reply address. Resend sends the email from Ireland, and stores the email and its delivery log in the United States: it keeps them for 30 days, and its backups for 7 days.
Data processed by Vercel and by Anthropic may be transferred outside the European Economic Area, to the United States, and Resend stores the notification emails there. Supabase and Zoho store the data in the European Union, but their staff and subprocessors may access it from outside the European Economic Area, for example for operations or support. The safeguard for the transfer is, for Vercel, the EU–US Data Privacy Framework and the European Commission’s Standard Contractual Clauses, and for Anthropic, Supabase, Zoho and Resend, the European Commission’s Standard Contractual Clauses.
The site uses no advertising provider and sends no data to an advertising network. The visit measurement script is served from this site’s own address; no script is loaded from any other site. When you submit a form, the only email the site sends is the Resend notification described above, to our own mailbox: it sends you no confirmation email and no marketing email.
Where the law requires it, data may be disclosed to an authority or a court.
Marketing consent is separate
Marketing consent is a separate tick box, empty by default, and it is not a condition of either the assessment or of contacting us. If you do not give it, no record of it is created — not a row marked "withdrawn", but no row at all. If you do give it, the record includes the exact wording shown and the time it was given.
There is no mailing list in operation and no outbound campaign sending is implemented. The unsubscribe page covers this in detail, including how to withdraw consent.
Aurelia AI: the chat assistant
Aurelia AI is an AI, not a person. It answers from the content published on this site, and the chat window says so every time it is opened. It sends no email, books no appointments, and changes or deletes nothing that has already been recorded. While the assistant is switched off, the interface is unavailable and no conversation data is created.
To produce a reply, the text of the conversation is sent to Anthropic’s language model. Alongside that, the conversation is recorded in our own database; the list below is what actually goes into it.
What we record about a conversation
- The language of the conversation, and the times it began and was last active.
- A salted hash of your IP address. The raw address is not stored here either — the same rule the forms follow.
- The identifying string your browser sends (the user agent).
- The text of the messages: yours and the assistant’s replies alike.
- The token counts for each reply, from which usage and cost can be read. They hold no personal data of their own.
- If you give your details during the conversation, the identifiers of the contact and enquiry records created from them, so that an enquiry made in chat and one made on a form belong to a single relationship.
- Every tool call: which action the assistant proposed, with what arguments, and whether it was executed, refused or failed.
The tool call log deliberately keeps the refused proposals as well. The assistant can only propose; whether a proposal becomes an action is decided by code that never reads your message. A run of refusals is what an attempt to talk the assistant into something looks like from the inside, which is precisely why they are kept alongside the calls that ran.
How long a conversation is kept
Conversations are kept for 30 days from the last message and are then deleted for good. The deletion takes the messages and the tool call log with the conversation: it is a real deletion, not an archive. Every new message restarts the 30 days, so a conversation still in progress is not removed from under the person having it; 90 days after it began, however, a conversation is deleted even if it is still going on.
The 30 days is held by the database itself, in one place, so that the period stated here and the period actually enforced cannot drift apart. The deletion runs on a daily schedule; it does not depend on anyone remembering to start it. If an enquiry is created during the conversation, it follows the periods under "How long we keep the data".
If you want your conversation deleted sooner than that, write to support@aureliadigitalsystems.com. Please give the approximate time of the conversation and, if you gave your details, the email address you used. Without that, an anonymous conversation cannot be identified with confidence.
The assistant records your name, email address or other contact details only if you explicitly acknowledged this notice during the conversation. It answers your questions either way; the difference is that no identifiable record of you is created. That condition is checked by the application code, not by the model.
If you message us on WhatsApp
You can message us on WhatsApp from the contact page, and you can choose WhatsApp as your preferred contact method on the forms. WhatsApp is operated by WhatsApp Ireland Limited (Dublin, Ireland), part of the Meta group. It is a separate service that you choose to use: the link opens WhatsApp, and the conversation takes place there, under WhatsApp’s own terms of service and privacy policy, under which Meta decides many of the purposes of processing itself.
The website neither receives nor stores WhatsApp messages, and it sends nothing to WhatsApp unless you click the link. Our own records fall under the same 90-day maximum: if you choose WhatsApp as your preferred contact method on a form, that choice is deleted with your contact details, on the schedule under "How long we keep the data", and we keep no message in our WhatsApp account for more than 90 days.
Your rights
- Access (Article 15 GDPR) — you may ask whether we hold data about you and, if so, what.
- Rectification (Article 16 GDPR) — you may ask for inaccurate data to be corrected and incomplete data completed.
- Erasure (Article 17 GDPR) — you may ask for your data to be deleted.
- Restriction of processing (Article 18 GDPR) — you may ask that we store the data but otherwise stop processing it.
- Portability (Article 20 GDPR) — you may ask for the data you provided in a machine-readable form.
- Objection (Article 21 GDPR) — you may object to the processing.
- Withdrawal of consent (Article 7(3) GDPR) — marketing consent and consent to visit measurement can each be withdrawn at any time, free of charge; the latter on the cookie notice page. Withdrawal does not affect the lawfulness of processing before it.
How to exercise them
To exercise any of these rights, write to support@aureliadigitalsystems.com. Please give your name and the email address you used, so that we can find your data. If we have reasonable doubts about who is making the request, we may ask for the additional information needed to confirm your identity (Article 12(6) GDPR).
We reply without undue delay and in any event within one month of receiving the request. Where necessary, taking into account the complexity and number of requests, that period may be extended by two further months; if so, we tell you within the first month, with the reasons (Article 12(3) GDPR).
Complaints and remedies
If you consider that the processing of your personal data infringes your rights, you may complain to the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság, NAIH). Seat: 1055 Budapest, Falk Miksa utca 9–11.; postal address: 1363 Budapest, Pf. 9.; email: ugyfelszolgalat@naih.hu; telephone: +36 1 391 1400; website: naih.hu. You may also apply to a court.