Notice 1 — Draft under legal review. This document is a technical draft prepared for review by MisAbogados (attorney Ricardo Cantero, case 25762) and does not constitute legal advice. Chile's Law 21.719 takes effect around December 2026; this text will be adjusted to the legal opinion before the final version.
Notice 2 — Unresolved address discrepancy. Our internal compliance package records Cochrane 639, Of. 54, Valparaíso; the verified record in Meta Business Manager reads Cochrane 639, of 54, Valparaíso, 2361806. This page uses Cochrane 639, as it is the platform-verified value. It must be confirmed with our accountant and attorney before final publication. See the Pending human decision block.
None of this affects your right to request deletion: if you write to datos@herihe.digital today, your request is processed today.
1. Who receives your request
| Legal entity | HERIHE DIGITAL LTDA. |
|---|---|
| Tax ID (RUT) | 78.389.881-0 |
| Registered address | Cochrane 639, of. 54, Valparaíso, 2361806, Chile (see Notice 2 above) |
| Data privacy channel | datos@herihe.digital |
| Phone | +56 9 4043 5095 |
| Website | https://herihe.digital/ |
| Business | Digital marketing and automation agency. We operate from Chile and serve clients in Chile, Brazil, the United States, Spain, Peru and Mexico. |
We act in two distinct roles, and which one applies determines who decides on deletion:
- Controller — when the data is ours: B2B prospects we contact, people who fill in our forms, visitors to our sites, vendors and staff. Here the decision is ours and we execute directly.
- Processor — when we operate data on behalf of a client (their CRM, their store, their ad account, their support channel). Here the decision is not ours: we forward your request to the client who controls the data and tell you who they are. See section 11.
2. What "delete my data" means
When you request deletion, we look for your data and erase it across every system where we might hold it, not just the one that contacted you:
- Our central contact database (identification, contact details, company, job title, source of the record and its usage history).
- The Mautic email marketing instances we operate.
- Our Chatwoot conversation system (website chat, WhatsApp, Messenger and Instagram Direct).
- Working spreadsheets, exports and internal reports where your data appears.
- Audiences and lists uploaded to advertising platforms, where we were the ones who uploaded them.
What we cannot delete for you: your Instagram, Facebook, WhatsApp, Google or Apple account; the messages stored on your own phone; or the data those platforms keep on their own behalf. Those deletions are requested from each platform. Section 12 tells you exactly where.
3. How to request deletion — step by step
There is no charge, no special form, and no need to justify your decision. We will not ask you why.
- Email datos@herihe.digital with the subject "Delete my personal data". This is the official channel and the one that creates a record.
- Tell us how to find you. The email address or phone number we used to contact you is enough. If you remember where the contact happened (an email, a WhatsApp message, a form), mention it — it speeds up the search.
- Tell us what you want. You can ask for full deletion, or only to stop receiving commercial communications (objection), which is faster and does not erase your contract history if you are a client.
- You will receive an acknowledgement within 48 hours with a reference number in the format
ARCO-YYYY-NNN. Keep it: with that number you can ask for the status of your request at any time by replying to the same email. - We confirm in writing once it is done, within the legal deadline that applies to your country (section 6), stating what was deleted and what — if anything — was retained under a legal obligation, and on what grounds.
If you would rather copy and paste, this message is enough:
4. Every available channel
| Channel | How to use it | What it does |
|---|---|---|
| Email (official) | datos@herihe.digital | Any right: deletion, access, rectification, objection, portability, blocking |
| Unsubscribe link | At the bottom of every email we send | Immediate opt-out from commercial communications (one click). Does not erase the rest of the data |
| Direct reply | Reply to any of our emails with "STOP SENDING ME COMMUNICATIONS" | Counts as an objection and is recorded exactly like an unsubscribe |
| WhatsApp or chat | Write "I want my data deleted" in your open conversation with us | We record it and ask you to confirm by email so there is a written record |
| Phone | +56 9 4043 5095 | We write it down and confirm by email before executing |
| Postal mail | Cochrane 639, of. 54, Valparaíso, Chile | Same process; the clock starts on receipt |
| From your Meta account | Settings → Apps and Websites (section 12.1) | Specific to data we receive from Meta platforms |
| From your Google account | myaccount.google.com/permissions (section 12.2) | Revokes our access to your Google data immediately |
5. What happens after your request
- Day 0 — Receipt. We log the request with its reference number and send you the acknowledgement within 48 hours.
- Days 1 to 5 — Search and verification. We verify your identity (section 7) and locate your data in the central database, in each Mautic instance, in the conversation system and in internal reports.
- Days 5 to 10 — Execution. We delete the record; where referential integrity prevents that, we irreversibly anonymise it. We add your minimum identifier to the suppression list (section 9) so you are not re-imported. All commercial communication stops immediately.
- Day 10 through the legal deadline — Response. We confirm the outcome in writing, stating what was deleted, what was kept, and on what legal ground.
If you only want to stop receiving commercial communications, we execute that within 48 hours across every channel, with no exceptions and without asking for a justification. It is an absolute right and we treat it as one.
6. Response times by jurisdiction
The deadline that applies to you is the one from your own jurisdiction. Where a person could be covered by more than one law, we apply the shortest deadline.
| Where you are | Applicable law | Response deadline | Authority you can complain to |
|---|---|---|---|
| Chile | Law 21.719 | 15 business days from receipt. Acknowledgement within 48 h. Objection to marketing: immediate (max. 48 h) | Agencia de Protección de Datos Personales (once constituted) |
| Brazil | LGPD — Law 13.709/2018 | Confirmation of processing and access in simplified format: immediate; full statement and execution: 15 days (art. 19). Withdrawal of consent: immediate (art. 8 §5) | ANPD — Autoridade Nacional de Proteção de Dados |
| European Union / EEA and United Kingdom | GDPR / UK GDPR | 1 month from receipt (art. 12.3), extendable by up to 2 further months for complex requests, with notice to you inside the first month | The supervisory authority of your country of residence |
| California (USA) | CCPA / CPRA | Acknowledgement within 10 business days; response within 45 calendar days, extendable by 45 more (90 total) with notice | California Privacy Protection Agency (CPPA) and the California Attorney General |
| Rest of the world | — | We apply the Chilean standard by default: 15 business days | Your country's data protection authority, where one exists |
About the platforms: Meta requires developers to act "promptly" but sets no number of days. That is why the deadline we give you always comes from the law that protects you, not from the platform.
7. How we verify it is really you
We verify identity so that we never hand over or erase one person's data at another person's request. It protects you; it is not a delaying tactic.
| Situation | What we ask for |
|---|---|
| You write from the same email address we have on file | Nothing further. That is enough |
| You write from a different address | Full name, the registered email address and, if you remember it, the subject line of the last message we sent you |
| You request it by phone or chat | We confirm by email before executing |
| You act as someone else's representative | A power of attorney or mandate evidencing the representation |
Anything you send us to verify your identity is used only for that purpose and is deleted when the request is closed, except for the minimum record we are legally required to keep as evidence that we handled it.
8. What gets deleted and what we must keep
Deletion is the rule. Retention is the exception, and only applies where there is a legal obligation or a right to exercise or defend. When we keep something, we tell you exactly what and why.
| Type of data | What happens when you request deletion | Ground |
|---|---|---|
| B2B prospecting data (name, work email, job title, company) | Deleted. Only the minimum stays on the suppression list | No legal obligation to retain |
| Campaign history and email interaction history | Deleted along with the contact record | — |
| Chat, WhatsApp, Messenger and Instagram Direct conversations | Deleted from our support system | — |
| Browsing and analytics data | Deleted or anonymised. Ordinary retention: 12 months | — |
| Tax and invoicing records | Retained for the statutory period (6 years in Chile), and used for nothing else | Statutory tax obligation |
| Data from a current or recent contract | Retained for the duration of the relationship plus the subsequent limitation period (5 years) | Performance of the contract and defence of legal claims |
| Evidence of your own request | Retained as a minimal record: date, channel, right exercised and outcome | Duty to demonstrate that we handled it |
| Suppression list | Retained at the strict minimum (see next section) | Honouring your own objection |
9. The suppression list (why we keep a minimum)
This one tends to surprise people, so here it is without euphemism.
If we erase absolutely every trace of you, nothing stops you from entering our database again tomorrow from a public source — a business directory, a corporate website, a list handed to us by a client — and receiving another email from us. The only way to guarantee that does not happen is to keep a marker saying "this person must not be contacted".
So when we carry out your deletion, we keep on a suppression list:
- Your email address and/or phone number, as a cryptographic hash wherever technically possible.
- The date of your request and the reason (objection or deletion).
That list is never used to send you anything. It does the exact opposite: every new batch of contacts is checked against it and matches are discarded before import.
If you still want us to erase even that minimum, ask and we will. But you should know the consequence: we lose the ability to recognise you, and you could be contacted again if your details reappear in a public source. We will warn you of this in writing before executing it.
10. What happens with backups
Backups exist so systems can be recovered after an incident. They are encrypted and are not consulted in day-to-day operations.
- Your deletion is carried out immediately in production systems, which are the only ones that send communications or drive decisions.
- Backup copies are never restored in order to undo a deletion. They are overwritten on their own rotation cycle.
- While a copy still exists, your data inside it is frozen: it is not used for any purpose.
- If we ever had to restore a backup after an incident, we re-apply the suppression list before returning the system to service, so your deletion is automatically re-executed.
The maximum length of the backup rotation cycle still has to be fixed and published: see the corresponding item under Pending human decision.
11. If we handle your data on a client's behalf
A large part of our work consists of operating other companies' data infrastructure: their CRM, their online store, their ad account, their support channel. In those cases the client company is the controller and we act on their instructions.
If your request falls into that category:
- We tell you within the same 48-hour acknowledgement window, rather than leaving you waiting.
- We identify which company is the controller and give you their contact channel, so you can go to them directly if you prefer.
- We forward your request to them anyway and assist them in executing it within the legal deadline. We do not use the handover as an excuse to do nothing.
- If that company instructs us to carry out the deletion, we execute it in the systems we operate and confirm it to you.
When a client contract ends, their data is returned or deleted as agreed in the data processing agreement, and we do not reuse it for any purpose of our own.
12. Platforms: where the data comes from and how to erase it
This section exists because data does not always arrive through a form. Sometimes it arrives from a platform, and each platform has its own deletion route alongside ours.
12.1 Meta — Facebook, Instagram, Messenger and WhatsApp
What data we may receive from Meta platforms:
| Data | What we use it for |
|---|---|
| App-scoped and page-scoped user IDs | Recognising the same conversation across messages; it does not identify you outside that context |
| Public name, profile picture and email address, where the person authorises them at login | Knowing who we are talking to |
| The content of Messenger, Instagram Direct and WhatsApp messages that reach our support system | Solely to answer and follow up on that same conversation |
| Public comments and mentions on pages and accounts we manage | Moderation and community response |
| Advertising metrics and campaign data from our client's ad account | Running, optimising and reporting on those campaigns, for that advertiser and no one else |
Limits we expressly accept for this data:
- We do not sell, license or purchase data obtained from Meta platforms.
- Message content never feeds commercial prospecting, marketing lists or database enrichment. It is used only to support the conversation you started with us.
- One client's advertising data is never combined with another's and is used for nothing other than assessing the performance of that advertiser's campaigns.
- We only process the platform data described here and in our privacy policy. If we ever needed another type of data, we would update these documents first.
How to request deletion of this data — two routes, either one works:
- Write to us directly at datos@herihe.digital, telling us the Instagram handle, Facebook page or WhatsApp number we spoke through. This is the fastest route: it enters the flow described in section 5.
- From your own Meta account, if you ever logged into an application of ours: Settings & Privacy → Settings → Apps and Websites → remove the app → View Removed Apps and Websites → select the app → Send Request. Meta delivers those requests to us in batches on a periodic basis, so if you want us to act right away, email us as well.
Remember that erasing your data from our systems does not delete your account or your messages on Facebook, Instagram or WhatsApp: that copy lives on the platform and on your phone, and is deleted from within the app itself.
12.2 Google — Ads, Analytics, Search Console, Tag Manager and Merchant Center
Here the data almost always belongs to a client company that granted us access to its own accounts through Google OAuth. We do not access anyone's personal Google account.
| Service and scope | What we access | Purpose |
|---|---|---|
Google Ads API (auth/adwords) | Campaign metrics, keywords, ads, budgets, conversions and account identifiers | Auditing, optimising and reporting on the client's campaigns |
Google Analytics (auth/analytics.readonly) | Aggregated reports on sessions, conversions and behaviour | Measuring results |
Search Console (auth/webmasters.readonly) | Queries, pages, impressions and organic positions | SEO diagnosis and planning |
Tag Manager (auth/tagmanager.readonly) | Inventory of tags, triggers and variables | Measurement audit |
Merchant Center (auth/content) | Feed and product status | Catalogue diagnosis |
How to cut off access and request deletion:
- Revoke the access yourself at myaccount.google.com/permissions. It is immediate and does not depend on us: from that moment we can no longer access anything.
- Email datos@herihe.digital so we also delete the data already extracted (reports, metric tables, exports) and the stored credentials.
When access is revoked or the contract ends, authorisation tokens are deleted immediately. Data already extracted is deleted or anonymised at the end of the relationship, within the term set in the data processing agreement with each client (see pending item 6). We do not use Google user data for our own advertising, to train general-purpose artificial intelligence models, or for creditworthiness assessment, and we do not sell it.
HERIHE DIGITAL LTDA.'s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
12.3 Apple — App Store and Sign in with Apple
Current status: HERIHE DIGITAL LTDA. does not currently publish any app of its own on the App Store. This section applies when we build or operate an iOS app on a client's behalf, and states what we guarantee in that case.
- In-app account deletion. Every app that lets you create an account also offers, inside the app itself and in an easily accessible way, the option to delete that account and its associated data — not merely deactivate it.
- Sign in with Apple. If you signed in with Apple and chose to hide your email address, we only ever receive Apple's private relay address. You can sever the link in Settings → your name → Sign-In & Security → Sign in with Apple; that stops the relay, and to erase data already stored, email us at datos@herihe.digital as well.
- Policy link. Each app's privacy policy is linked from its App Store product page and from inside the app itself, and its App Privacy labels declare the data collected.
12.4 Other platforms
This table grows as we add channels. In every case, the general route remains datos@herihe.digital.
| Platform | What we may hold | Additional deletion route |
|---|---|---|
| WhatsApp Business | Phone number, profile name and the content of messages you sent us | Email us; deleting the chat on your phone does not delete our copy, and vice versa |
| TikTok | Advertising campaign data and public comments on accounts we manage | Email us; your own profile content is managed in your TikTok account |
| Public professional data used for B2B prospecting | Email us; you go on the suppression list | |
| Shopify / WooCommerce | Order data from stores we operate on a client's behalf | Processor role: see section 11 |
| Stripe, MercadoPago, Transbank, Flow | We do not store card numbers. Payment references tied to an order | Subject to tax retention; see section 8 |
| Google Maps and public directories | Publicly published business contact data | Email us; you go on the suppression list so it is not re-imported |
| Fathom (meeting recording) | Voice, image and transcript of meetings you took part in | Email us with the date of the meeting |
| Telegram | Identifier and messages in support channels | Email us |
13. Your rights by jurisdiction
Deletion is one of several rights. They are all exercised through the same channel and all free of charge.
Chile — Law 21.719
Access, rectification, cancellation (erasure), objection, portability and blocking. Objection to direct marketing is absolute: you do not need to justify it and we cannot refuse it. Deadline: 15 business days. Complaints go to the Agencia de Protección de Datos Personales.
Brazil — LGPD
Confirmation that processing exists, access, correction, anonymisation, blocking or deletion of unnecessary or excessive data, portability, deletion of data processed on the basis of consent, information about who we share data with, information about the option not to consent, withdrawal of consent, and review of automated decisions. Deadline: immediate in simplified format, 15 days for the full response. Complaints go to the ANPD.
European Union / EEA and United Kingdom — GDPR
Access, rectification, erasure ("right to be forgotten"), restriction of processing, portability, objection — including the absolute right to object to direct marketing — and the right not to be subject to solely automated decisions producing legal effects. Deadline: 1 month, extendable by 2 further months. Complaints go to your national supervisory authority, and you also have the right to an effective judicial remedy.
California — CCPA / CPRA
The right to know what personal information we collect, use and share; the right to delete it; the right to correct it; the right to limit the use of sensitive personal information; and the right not to be discriminated against for exercising any of these rights — we will not charge you more or give you a worse service.
We do not sell or share your personal information as those terms are defined under the CCPA/CPRA, and we do not use it for cross-context behavioural advertising. Deadline: acknowledgement within 10 business days and a response within 45 calendar days, extendable by 45 more. You may appoint an authorised agent to exercise your rights; we will ask them for proof of that authorisation.
14. Vendors and international transfers
To deliver our services we work with vendors that process data on our instructions. When we carry out a deletion, we propagate it to those concerned.
| Vendor | Function | Where the data sits |
|---|---|---|
| DigitalOcean | Compute infrastructure and hosting | USA |
| cPanel hosting (converclick.com) | Websites and forms | USA |
| Mautic (self-hosted instances) | Email marketing | On our own infrastructure |
| SendGrid | Email delivery | USA |
| Google (Ads, Analytics, Search Console, Tag Manager, Workspace) | Advertising, analytics and corporate email | USA / EU |
| Meta | Advertising and messaging channels | USA |
| Salesforce Marketing Cloud | A client's audiences | USA |
| Klaviyo | A client's email marketing | USA |
| Apify | Public data collection | EU / USA |
| Hunter, Apollo | B2B email verification and enrichment | EU / USA |
| OpenAI, Anthropic | Transcription and artificial intelligence agents | USA |
| Fathom | Meeting transcription | USA |
| Transbank, MercadoPago, Flow, Bsale | Payments and invoicing | Chile and region |
Part of this infrastructure sits outside Chile, mainly in the United States. For those transfers we adopt the safeguards required by articles 27 and 28 of Law 21.719 and, where applicable, the GDPR standard contractual clauses. An up-to-date vendor list is available on request.
15. If we cannot delete your data
Some of your data may have to be retained. If that happens we will not go silent or answer with boilerplate. We send you, in writing:
- What was actually deleted and what was not.
- The specific reason for the retention and the rule that requires it (for example, the tax obligation to keep invoicing records).
- The date after which that portion will also be deleted.
- Confirmation that what is retained is not used for any other purpose, and in particular is never used to contact you.
If you disagree with our answer, you can complain to the authority for your country listed in section 6. You can also reply to the same email asking for a review, and we will carry one out.
16. Contact and related documents
- Data privacy channel: datos@herihe.digital
- Phone: +56 9 4043 5095
- Postal address: Cochrane 639, of. 54, Valparaíso, 2361806, Chile
- Website: https://herihe.digital/
The other two documents in this same package (also under review):
Until this package is published, the versions in force on the site are the current privacy policy and terms.
17. Pending human decision
This block is deliberately visible. It lists what cannot be settled in the drafting and requires a decision from HERIHE DIGITAL LTDA.'s management, its accountant or its attorney.
- Registered address. The current address is Cochrane 639, Of. 54, Valparaíso, per the articles of incorporation and the compliance file. The Meta Business Manager record contains a typo (“630”); HERIHE DIGITAL LTDA. decided on 2026-09-06 not to correct it, to avoid reopening the already completed business verification. This page uses the correct address.
- Responsible entity — resolved. The controller is HERIHE DIGITAL LTDA. (RUT 78.389.881-0, Valparaíso), confirmed by management on 2026-09-06. The earlier attribution to “Converclick, based in Santiago” is superseded.
- Response deadline discrepancy. The live page promises 20 business days; the internal procedure and this page use 15 business days, which is the Law 21.719 deadline. This must be unified on the shorter figure.
- Contact phone number. The website shows a WhatsApp number,
+56 9 4043 5095; the operational record lists+56 9 4043 5095, which is the one shown here. Decide which is the official channel for data protection matters. - Backup rotation cycle. A maximum number of days after which every backup copy containing deleted data has been overwritten still needs to be fixed and published.
- Deletion deadline for data extracted from Google APIs. The technical proposal is 30 days from the end of the relationship or from revocation. It needs operational confirmation (is it achievable?) and legal sign-off before being published as a commitment.
- Meta deletion route. Meta lets you choose between a data deletion instructions URL (which is what this page is) and a callback URL that receives signed requests and returns a confirmation code. Today we cover the first. The second requires development: endpoint, signature verification, deletion queue and status page. Decide which one gets declared.
- Publication and URL declaration. Decide the final URL for this page and declare it in Meta's App Dashboard and, where applicable, in App Store Connect. Remember that Google requires the privacy policy to be hosted on the same domain as the declared home page and linked from it, and the domain to be verified in Search Console by the same identity that owns the Google Cloud project.
- Appointment of a data protection officer. Still not appointed. Its mandatory nature must be assessed given the volume processed and the presence of clients' sensitive data.
- Anonymisation as an alternative to erasure. Confirm whether it is legally acceptable where referential integrity prevents physical deletion, and with what irreversibility guarantees.
- Twelve-month retention for unresponsive prospects. Confirm whether the period is sufficient and defensible under Law 21.719.
- Contractual chain with sub-processors. Formal data processing agreements with the foreign vendors listed in section 14 are still missing. Without them, what this page promises about propagating deletion downstream rests only on each vendor's generic terms.
- Residual data in decommissioned instances. There are Mautic instances belonging to former clients that no longer run but still hold data. A decision is needed between secure erasure, return to the former client, or retention on an express legal basis — and it must be reflected here.
- Publish the package together. This page, the privacy policy and the terms form a single package and link to each other by filename (
privacy.{es|pt|en}.html,terms.{es|pt|en}.html,data-deletion.{es|pt|en}.html). They must be published together and in the same directory; if any of them is renamed or moved on upload, the links must be adjusted before declaring any URL to Meta or Google. To Meta, a broken link on a legal page is a violation, not a detail.
Drafted as version 1.0 on September 6, 2026 for review by MisAbogados (case 25762). It does not constitute legal advice. If you are the professional reviewing it, write to datos@herihe.digital.