Zircon CRM / Administration
Runs in the browser · HU / EN / DEGDPR compliance from consent to erasure requests
Zircon CRM has a dedicated GDPR area that records who agreed to what, and when. Customer contacts and leads can request an export or the removal of their data themselves, and you handle the requests in one list. You also edit your terms and privacy policy here and publish them at fixed public addresses.
Consent with date and IPData export as JSONErasure requests in one list
In short
How does Zircon CRM help with GDPR compliance?
The GDPR is the EU's General Data Protection Regulation, which gives people rights over their data: access, portability, erasure and withdrawing consent. The GDPR area in Zircon CRM gives contacts and leads consent purposes with an evidence trail, JSON data export, a list of erasure requests and a public consent page. It is built for administrators and data protection officers.
Sound familiar?
The consent exists somewhere. The proof does not.
If one of these rings true, data protection requests at your company still run by hand.
- 01
Newsletter, but who asked for it?
A contact complains about receiving your newsletter. You know they were added to the list, but not when or what they said yes to.
- 02
An export request by e-mail
A former customer asks for the data you hold on them. You copy it together from three systems by hand and still cannot be sure it is all there.
- 03
Erasure or bookkeeping
A customer asks to be deleted, but they have invoices. Either the request stays unanswered, or records your accountant needs disappear.
- 04
The yes on the phone gets lost
A sales rep asks on the phone whether they may send offers, and the answer survives only in their notebook.
What it does
GDPR compliance tools in one place.
You turn the GDPR features on with one master switch, then choose per right what you use.
Consent purposes
Define what you ask permission for, such as the newsletter or event invitations, with a short description. Once a purpose has been used its name is locked, so recorded consents always refer to the same purpose.
History as evidence
Every yes and no goes into the history with purpose, date, IP address and, when staff recorded it, their name and a note. Consent given on the phone is recorded with a note like "agreed by phone".
Public consent page
Each contact and each lead gets a personal, hard-to-guess link where they say yes or no per purpose. The page records every change with date and IP address and is excluded from search engines. You can add the link to any e-mail template as a merge field.
Data export as JSON
A contact downloads their data from the portal's GDPR page, a lead from their own public page: a ZIP file with a readable JSON document. You decide what goes in, passwords never. A primary contact's export can include the company's invoices, estimates, projects and contracts.
Erasure requests in one list
Contacts in the portal and leads on their public page can request removal with a reason. Requests land in one list with a Pending, Removed or Refused status, and every active administrator receives an e-mail.
Deletion that keeps your books
With GDPR on, you can delete a customer who has invoices. You choose whether their invoices, credit notes and estimates are deleted too or kept for your accounts with the company name preserved.
Terms and privacy policy
You edit your terms and conditions and privacy policy in the system, and they appear at fixed public addresses. You can require acceptance at customer registration, on lead forms, the ticket form and quote request forms.
Filter by consent
Contact and lead lists have a consent column and filter, so you can build a list of the people who said yes to a given purpose.
How it works
From switching it on to the first erasure request.
- 01
Enable the GDPR area
Write the information block for the portal's GDPR page and decide whether it is linked in the portal menu and footer.
- 02
Publish your legal texts
Fill in the terms and the privacy policy, and switch on acceptance on the forms you use.
- 03
Add consent purposes
Enable consent for contacts, leads or both, and put the consent link into your e-mail templates.
- 04
Set up export and erasure
Choose what goes into an export and what happens to invoices when a customer is deleted.
- 05
Handle the requests
After the e-mail arrives, review the request, delete the contact, customer or lead, or keep it if you have a legal reason, and set the status.
Works with
Where personal data passes through.
- Lead managementeach lead has a GDPR tab, and on conversion its consent history can move to the new contact.
- Customer managementcontact lists show a consent column and filter, and deleting a customer follows your GDPR settings.
- Customer portalon the portal's GDPR page, contacts request an export or erasure and change their consent.
- Web-to-lead formsyou can make acceptance of your terms mandatory on the website form.
- E-mail templates and notificationsthe consent link goes into e-mails as a merge field, and the erasure request notification is sent from here.
- Security and sign-intwo-factor login and the login audit trail guard the way in to personal data.
Honestly
Good to know before you start.
Zircon CRM gives you tools for GDPR compliance, but it does not make you compliant by itself. The legal basis, retention periods and the wording of your notices are decisions for your company, best made with a lawyer.
Zircon CRM does not provide a cookie consent banner. Its consent management covers contacts and leads.
An erasure request does not delete anything automatically: an administrator reviews it, deletes the data and sets the status.
Deleting a consent purpose also deletes every consent record for it. GDPR settings, the request list and exports on someone's behalf are for administrators only.
Before you write
Fair questions. Straight answers.
- 01
Does Zircon CRM make my company GDPR compliant?
Not on its own. Zircon CRM records consent, handles export and erasure requests and publishes your legal texts. The legal basis, retention periods and the content of your notices are still for your company to decide.
- 02
How can I prove in Zircon CRM that someone agreed to the newsletter?
The contact's or lead's history lists every yes and no with purpose, date, IP address and, when staff recorded it, their name. If the person agreed on the public page, the exact wording they agreed to is kept too.
- 03
Can a lead without a portal account request erasure in Zircon CRM?
Yes. Every lead can get a unique public page where they view and correct their data, export it, change their consent and request removal. Zircon CRM then e-mails your administrators about the request.
- 04
What happens to invoices when I delete a customer in Zircon CRM after a GDPR request?
It depends on your settings. Zircon CRM either deletes the invoices, credit notes and estimates with the customer, or keeps them: they are detached from the deleted customer but keep the company name. Contacts, tickets, notes and contracts are removed.
- 05
In what format does Zircon CRM hand over a person's data?
As a ZIP file containing a structured, readable JSON document named after the person. Passwords are never included. You set separately for contacts and leads exactly what goes in.
Let's talk.
The first call costs nothing
A human replies — not a bot
Bring your current privacy notice and how people sign up for your newsletter today. In the demo we turn that into a consent purpose with its public page and run an erasure request from start to finish.
- hello@zircon.hu
- Phone
- +36 30 487 7979
- Hours
- Weekdays 9–17
- Support
- support@zircon.hu (existing clients)