Make a personal data request.

Ask whether Tervuq holds personal data relating to you and request access to the relevant information. A useful starting point is the email address used for an earlier inquiry and an approximate period. You can mention a receipt reference if you already have one; it is not required to begin.

Describe the interaction rather than resending its full contents. An inquiry about a public website and a later support conversation may be separate records.

An access request needs to be matched to the right person and records. Information about other people, protected material and security details may need to be removed before information is provided. Access does not mean unrestricted access to a working system.

Identify the detail that is wrong and the replacement you want considered. For example, say that the contact address on an inquiry is outdated. Explain which record it relates to without copying a whole client database into the form.

A correction may change an active contact field while a limited record of the original exchange remains where needed to understand the request.

Accurate details help avoid replies going to the wrong person. A request to rewrite the history of an exchange is different from correcting an inaccurate field. Where those differ, the response explains what can be corrected or annotated.

Tell us which personal data you want removed, or ask for a review of the personal data associated with your inquiry. You do not need to know a database name or a storage location. Closing a browser window or deleting its local chat token does not itself delete the related conversation record.

Where deletion can be completed, the response describes the action. Where a record must remain, the response explains the applicable reason rather than treating the entire request as resolved.

Deletion can be limited by legal obligations, the need to establish or defend a claim, or other exceptions under applicable law. Retention is assessed against the record's purpose and those obligations, not a single storage period for every type of record.

You can ask about restriction of processing, object to a particular use, request a portable copy where that right applies, or withdraw consent for processing that relies on it. State the use you are concerned about and the change you want.

If you want to challenge a decision on a request, reply through the same contact route and explain what should be reconsidered. Ask about an appeal where applicable law provides one. You may also contact the relevant privacy authority where you have that right.

Not every visitor has identical statutory rights. The applicable law and the basis for processing affect what can be done. Withdrawing consent does not undo earlier lawful processing or automatically remove records retained on another lawful basis.

Start with your name and one reply route. Where possible, use a contact channel already associated with the inquiry. Follow-up may ask you to confirm a non-sensitive detail from that interaction or respond through the original channel. If you no longer control it, explain that limitation.

Do not send an identity document, password or account recovery code. A postal address is not required. If you act for someone else, say so and describe your authority without attaching their private records.

A request must not become a way for a stranger to obtain or delete another person's information. Verification is proportionate to the request and the risk of disclosure. Authority to act for another person may need separate confirmation before their records can be released.

This form concerns personal data handled by Tervuq. If the record sits in a customer portal operated by another business, name the business and describe your connection without sending the record. A request may need to go to that operator, which decides how its customer information is used.

The export panel shown in this page's menu is an illustrative interface study. It is not a login to your records or a self-service export feature.

Building an interface does not necessarily make the studio responsible for every record used through it. Tervuq cannot promise to disclose or alter information it does not control. A referral is explained when another responsible party must handle the request.

Google Ads and Microsoft Advertising send traffic to this site. Meta Ads can also bring visitors here. Their arrival URLs can contain gclid, msclkid and fbclid respectively. Use Cookie settings to change optional storage without waiting for a data-request reply.

Consent Mode v2 holds ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow optional storage. Allowing updates them to granted; declining or withdrawing sets all four back to denied. Denied storage does not necessarily mean no consent-aware network signals are sent.

A site storage preference is separate from an access or deletion request. Changing it does not remove platform-held records or clear every browser item. This request form's consent only covers handling your request, not advertising storage.

The request is reviewed for scope, verification needs and the law that applies. A reply may ask a focused question before any records are released. Where a legal response period applies, that period and any permitted extension govern the handling; this page does not impose one deadline on every visitor.

If a request cannot be fulfilled in full, the response explains the limitation and any available next step. You can ask for an explanation in clearer language.

Immediate disclosure would bypass verification. The request itself also creates a record needed to handle the exchange and account for the response. It is subject to the retention criteria and security limits described in the privacy statement.