Privacy
Privacy Policy
Last updated: November 22, 2026
1. Who we are
invitas.co is operated by Juan Felipe Rivera González, an individual residing in Cali, Valle del Cauca, Colombia. This Policy applies to hosts, guests, and site visitors.
- General inquiries: [email protected]
- Privacy and personal data: [email protected]
2. Your role and ours
- When you are a host: invitas.co is the Controller of your data (account, payments, and product use).
- When you are a guest at an event: the host is the Controller of your data (name, email, WhatsApp, RSVP responses, and custom fields); invitas.co acts as the Processor processing that data on the host’s instructions.
- When you enable change notifications from your invitation: you decide on that processing directly with us, so invitas.co is the Controller of the data for those notifications (details in Notifications on your device). The host remains responsible for the rest of your guest data.
3. Data we collect
From hosts:
- Identity and contact details: name, email, WhatsApp, country, and time zone.
- Account: credentials (through Google OAuth) and session history.
- Product use: events created, guests added, messages sent, and photos uploaded.
- Payments: processed by Wompi or Lemon Squeezy. invitas.co stores only the transaction ID, amount, currency, and status. We do not store card numbers.
From guests:
- Name and contact details uploaded by the host (email, WhatsApp).
- Custom fields defined by the host (what you will bring, menu choices, restrictions, and other details).
- RSVP response and optional messages to the host.
- Photos you choose to upload to the event album.
- If you turn on change notifications from your invitation: your device registration (see “Notifications on your device” below).
From visitors:
- Technical data: IP address, browser, operating system, and pages visited (through Google Analytics 4).
- Functional and analytics cookies (see §10).
Notifications on your device
Notifications are optional. They are used only if you turn them on for each event and grant your browser permission to send notifications. You can turn them off at any time; your invitation and dashboard will work the same without them.
RSVP notifications (host). When you turn them on under Guests, we store the subscription address created by your browser and its encryption keys, the browser you used to turn them on, a fingerprint of the session in which you did so (never the session itself), who turned on notifications for each event and when, and each notification’s history: its text, the device it was sent to, whether it was delivered, and whether you opened it. The notification includes the event name and says who responded, whether they confirmed or cannot attend, and how many people they confirmed for. If several people respond in quick succession, you receive one notification with up to three names per response and the number of additional responses. Depending on your settings, your phone may show it on the lock screen.
Change notifications (guest). When you turn on notifications from your invitation, we store your browser’s subscription address and encryption keys, the browser, which invitation that device follows, a fingerprint of the link used to turn notifications on (so we can stop notifying you if the link is no longer valid), the domain from which you enabled them if the invitation uses a custom domain, and notifications sent with their delivery status. To identify changes, we also store a copy of the event date, time, location, and schedule. The notification says only what changed (the date, time, location, or schedule), or that there is a new message, and gives the event name. It never includes the new address, date or time, the host’s note, your name, or other guests’ names; those details are available inside the invitation.
How the notification is delivered. invitas.co encrypts the notification and delivers it through your browser’s notification service: Google (Chrome, Android, and most Chromium-based browsers), Apple (Safari), Mozilla (Firefox), or Microsoft (Edge). We do not choose the service; your browser determines it. The service receives the subscription address and the message encrypted with your device’s keys (RFC 8291 standard), not the plaintext content, and stores it for up to 24 hours if your device is offline.
How to turn them off. If you are a host, select “Turn off notifications for this event” under the event’s Guests section: notifications for that event will stop on all your devices. That button does not delete your device registrations, which continue to work for your other events with notifications enabled. A device registration is deleted when you sign out on that device, sign in with another account in that browser, delete your account, the browser cancels the subscription, or—if your session has expired—that browser has not returned to your dashboard for 90 days. If you unsubscribe from the follow-up and tips emails we send, you will also stop receiving notifications. If you are a guest, select “Stop notifying me” in your invitation: that device will stop receiving notifications for the event and, if it does not follow any other event, its device registration, subscription address, and keys are deleted. You can also block notifications from invitas.co in your browser settings at any time.
Measurements. We record when a notification is offered, enabled, disabled, sent, or opened to measure use of the feature. Some of these records include the IP address and browser used for the action; none stores the subscription address or keys.
Your data export. A host account’s data export includes its notification-enabled devices (the notification service used, browser, and dates, without the subscription address or keys), notifications received and their delivery status, and notifications sent to guests, including how many guests follow each event. Guests do not have an account to export; their device registration is deleted when they select “Stop notifying me”.
4. How we use your data
Necessary purposes (contractual basis; we cannot provide the service without these purposes):
- Create and operate your account and events.
- Process payments and issue receipts.
- Send invitations and operational communications.
- When a host enables automatic RSVP reminders, we use the WhatsApp number they provided to send each guest who has not responded one message per number, containing the event information and personal link, 5 days and 1 day before the RSVP deadline. We send these messages between 8 a.m. and 10 p.m. in the event time zone. If a guest replies STOP, they will no longer receive messages from invitas.co.
- Send RSVP reminder summaries to the host.
- Generate text and images with AI (optional feature; see §6).
- Meet legal obligations (accounting, tax, and responding to authorities).
Secondary purposes (you may object without affecting the service):
- Improve the product through aggregated analytics.
- Send you product updates or tips by email (each email includes an opt-out).
Purposes you enable (with your consent, which you may withdraw at any time without affecting the service):
- Send notifications to your device: to the host when someone responds to their event, and to a guest when the date, time, location, or schedule changes, or there is an update (see Notifications on your device).
5. What we do NOT do
- We do not sell or share your data with third parties for advertising.
- We do not embed social media tracking pixels.
- We do not read messages written by your guests.
- We do not index invitation pages on Google (all have
noindex). - We do not use your data to train AI models (see §6 and our Terms).
6. AI processors
When you use AI features, we send your instructions (the text you enter and, for “Create an Invitation” and “Inspiration,” an optional photo) to one of the following providers, depending on the feature. Some processing takes place outside your country:
- Google Cloud Vertex AI — text generation and photo analysis (Gemini 3.1 Flash-Lite, processed in the
usmulti-region — United States) — primary provider, including for the Host Assistant. - Google Cloud Vertex AI — image generation and editing (image generation and image-to-image using
gemini-3.1-flash-image, processed in theus(United States); Imagen usesus-central1— Iowa). When you generate an image, or use “Inspiration” with photo editing, your image instructions (and, in that case, the reference photo, which must not contain recognizable people) are sent to the United States under the Google Cloud DPA’s Standard Contractual Clauses, pursuant to Article 26 of Law 1581/2012 (Colombia) and equivalent frameworks in other countries in the region. - DeepInfra (United States): AI backup provider; it receives text only if Vertex AI fails or does not respond. Before sending, we tokenize email addresses, phone numbers, Colombian national ID numbers (cédulas), Mexican CURP numbers, and Argentine DNI numbers, but not names. It does not receive photos or images and, according to its privacy policy, does not retain data or use it to train models.
Before sending data, we automatically replace the following categories of structured personal data with tokens (e.g., [EMAIL_0], [PHONE_1], [CEDULA_CO_2]): email addresses, phone numbers, Colombian national ID numbers (cédulas), Mexican CURP numbers, and Argentine DNI numbers. Tokens are restored only when we show you the result. Names are sent under each provider’s Data Processing Agreement (DPA), which explicitly prohibits their use to train models. Neither provider is permitted to use your data to train its models. We retain AI invocations in our database for 180 days for billing, debugging, and abuse prevention; they are then anonymized.
To assess the quality of Guest Import, we privately store the list you pasted, the proposed result, and the list you accepted. Only authorized invitas team members can access these texts. If you do not import the list, we delete them after 7 days; if you do, we delete them 180 days after processing, during the next daily cleanup. We retain the counts and import record linked to the event. If you delete your account or event, we also delete these texts; administrative deletions are processed during the next daily cleanup. To access or request deletion of these texts, email [email protected]. If you delete a guest row to correct your list, the import record remains subject to its retention period. To also request deletion of the original text, email [email protected].
The complete, up-to-date list of all our subprocessors (not only AI providers) is available at /en/subprocessors.
7. Other processors we use
- Contabo GmbH (Germany) — server hosting, data storage, and error monitoring.
- Cloudflare (United States + global edge network) — CDN, DNS, WAF, and R2 storage (photos and video).
- Google OAuth — host authentication (we receive email address and name).
- Google Analytics 4: public-site analytics, with IP anonymization, no names or email addresses, and no Google advertising signals. If you are signed in, an opaque internal identifier is associated with the data, not your email address. Analytics is not used on real event invitations, the host dashboard, check-in door links, or pages with tokenized links. Example demos are measured because they are fictional and contain no real people’s data. Only campaign parameters are sent to Google; all others, including tokens, are removed. You can disable it with the official Google opt-out extension.
- Resend (United States) — transactional email delivery (welcome messages, RSVP reminder summaries to the host, billing notices).
- Wompi (Bancolombia) — payment processing in Colombia (PCI compliance is its responsibility).
- Lemon Squeezy (United States) — international payment processing in USD (PCI compliance is its responsibility).
- Chatwoot Community Edition (self-hosted by invitas.co on Contabo’s server in Germany, domain
soporte.invitas.co) — management of conversations and customer support tickets when you contact us through the dashboard widget or via [email protected]. It stores your name, email address, conversation content, IP address, and browser metadata. Because this open-source software is operated directly by us, there is no intermediary SaaS provider: invitas.co acts as data controller and as the technical processor of the infrastructure. - External AI assistant (only when you connect your invitas.co account through our connector
invitas.co/mcp) This may be Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Perplexity, or any other tool using the same standard: you choose the provider, use your own account, and are subject to your existing agreement with that tool, so we cannot predict which provider it will be. When you connect, you approve the permissions requested by the application on a screen we provide. From then on, event data returned by each tool you ask it to access (event, guests and their contact details, RSVPs, invitation links, event images, wall messages, tables, and prepared reminder text) reaches the assistant provider because that is where the conversation runs. This transfer is optional and enabled by you: if you never connect your account, no data is sent to an assistant provider. We never send internal platform secrets or stored guest credentials to them. Preparing reminders does not send an email or WhatsApp message or add a send to the history. Guest-specific fields are for logistics, not medical data. Disconnecting an app revokes its access and refresh tokens; it does not delete copies already received by the provider, whose retention and deletion are governed by its policies. You may request access or deletion by emailing [email protected]. Full details and instructions to revoke access are available at /asistentes. - Your browser’s notification service, only if you enable notifications on your device: Google, Apple, Mozilla, or Microsoft, depending on your browser. We neither choose nor hire that provider; your browser determines it. The provider receives the subscription address and encrypted notification, not its plaintext content. Details are available at Notifications on your device.
8. International transfers
Your data may be transferred to:
- Countries with an adequate level of protection (EU, United Kingdom, Switzerland, and Uruguay): primary hosting in Germany (Contabo).
- United States (Cloudflare, including R2 storage for photos and video; Google OAuth/Analytics; Resend; Lemon Squeezy; DeepInfra; and Google Cloud Vertex AI — text, photo analysis, and image generation/editing with Gemini 3.1 Flash-Lite and Gemini Flash Image 3.1 in the
us, and Imagen inus-central1): under standard contractual clauses signed with each provider, except DeepInfra, which operates under its terms of service and privacy policy, pursuant to Article 26 of Law 1581/2012 (Colombia), AAIP Provision 60/2016 and Resolution 198/2023 (Argentina), MINJUS 2024 guidance (Peru), and LFPDPPP 2025 guidelines (Mexico). - To the country where the external AI assistant you connect is located, and only if you connect it, through the connector
invitas.co/mcp: under the standard contractual clauses in that provider’s data processing agreement and on the basis of your explicit consent, given on the authorization screen. You choose the provider (Claude, ChatGPT, Gemini, Perplexity, or another tool using the same standard), so the country depends on your choice; the most commonly used providers currently process data in the United States. This transfer does not happen by default: it begins only when you connect the account and ends when you revoke access. - To the country where your browser’s notification service is located, and only if you enable notifications on your device: Google, Apple, Mozilla, or Microsoft, companies based in the United States, depending on your browser. The subscription address and encrypted notification are transferred, not the plaintext content. The legal basis is your consent when you enable notifications. The transfer ends when you turn them off: as a guest, by selecting “Stop notifying me”; as a host, for one event by selecting “Turn off notifications for this event,” and for all events by signing out on that device or deleting your account.
For users residing in Ecuador, Costa Rica, the Dominican Republic, Panama, and other countries in the region without a recognized adequate level of protection, transfers take place on the same bases described above: standard contractual clauses and, for the browser notification service, your consent.
By using invitas.co, you accept these transfers, except for the two optional transfers (the external AI assistant and the browser notification service), which occur only if you enable them. You may request a copy of the clauses by emailing [email protected].
9. Your rights
Under Colombia’s Habeas Data law (Law 1581 of 2012) and equivalent laws in the region (Mexico’s LFPDPPP, Argentina’s Law 25.326, Chile’s Law 21.719, Peru’s Law 29733, Brazil’s LGPD, Ecuador’s LOPDP, Costa Rica’s Law 8968, the GDPR for the European Union/Spain, and applicable rules in other countries in the region), you may exercise the following rights:
- Access: know what data we hold about you.
- Rectification: correct inaccurate data.
- Cancellation / Erasure: ask us to delete your data.
- Objection: object to non-essential uses (marketing, analytics).
- Data portability: receive your data in a structured format (JSON).
- Withdrawal: withdraw your consent at any time.
- Complaint: lodge a complaint with your data protection authority (see §15).
Write to us at [email protected] with your request. Response times vary according to the type of request:
- Inquiries (access, information): we respond within 10 business days (extendable by 5 business days), under Article 14 of Law 1581/2012 in Colombia.
- Complaints (rectification, erasure, withdrawal): we respond within 15 business days (extendable by 8 business days), under Article 15 of Law 1581/2012.
- If you live outside Colombia, we apply whichever deadline is more favorable to the data subject: 15 days or the deadline in your jurisdiction (Mexico: 20+10; Argentina: 10 calendar days for access requests; Costa Rica: 5 business days).
If you reside in Colombia, also see our Data Processing Policy (Habeas Data) for details about Colombia’s legal framework.
10. Cookies and tracking technologies
We use:
- Strictly necessary cookies (session, authentication): consent is not required.
- Analytics cookies (Google Analytics 4): used on the public site and fictional demos, which contain no real people’s data. They are not used on real event invitations. You can disable them with the official Google extension linked above.
- Functionality cookies (theme preference): optional.
- Internal operational cookies (
invitas_internal, value 1/0, valid for 1 year): set manually only by the operations team on its devices to exclude their visits from GA4 metrics and preserve real traffic data for the pilot. It does not collect or link visitors’ personal data and is not set automatically.
You can manage your preferences in your browser settings. Starting in December 2026, in accordance with Chile’s Law 21.719, we will implement an explicit consent banner for residents of Chile.
11. Data retention
| Data type | Retention period |
|---|---|
| Host account data | While your account is active + 5 years (DIAN tax obligation) |
| Active events | While they are published |
| Archived events | 24 months after the event |
| Guest data | 12 months after the event (at the host’s direction) |
| AI invocations | 180 days, then anonymized |
| Guest Import text | 7 days if not imported; 180 days from processing if imported. Cleanup runs daily. |
| Create your invitation answers and data read from an inspiration invitation | We delete the Create your invitation answers and the data we read from an inspiration invitation after 7 days if you do not claim the draft. If you claim it, we keep them for up to 180 days from its creation. If you delete your account or event, we delete them sooner. |
| Support conversations (Chatwoot) | 12 months after the last activity, then automatically purged |
| Notifications on your device: text and delivery status | 30 days. Earlier if the event or host account is deleted, or if the guest named in an RSVP notification is deleted |
| Device receiving RSVP notifications (host) | Until you sign out on that device, sign in with another account in that browser, delete your account, or the browser cancels the subscription. If your session expires and that browser does not return to your dashboard for 90 days, the registration is deleted. |
| Device receiving change notifications (guest) | Until you select “Stop notifying me” or 7 days after the event date. Earlier if the guest, event, or host account is deleted. If the link you used to enable notifications becomes invalid (the host regenerates it, the event becomes private, or the event stops using that custom domain), that device stops receiving notifications for the event, and its tracking record is deleted the next time the host sends a notification or, at the latest, 7 days after the event. A device that no longer follows any event is deleted. |
| Copy of the event date, time, location, and schedule used to detect changes | While any guest follows the event, and at most 7 days after its date |
| Comments from the post-event survey | 24 months after your response, then deleted; earlier if you delete your account |
| Technical and audit logs | 90 days |
| Accounting and tax records | 5–10 years (depending on applicable law) |
Backups follow the applicable retention policy and are not used to assess Guest Import.
You may request earlier deletion unless we are legally required to retain the data.
Deletions of device notifications due to expiration or deletion are applied in an automated daily review. Deletions related to an invalid link or a subscription canceled by the browser are applied the next time a notification is attempted for that device. In the meantime, no notification is sent for a deleted event, account, or guest, or to an invalid link.
Right to erasure (Art. 8(e), Law 1581)
When you exercise your right to erasure (Art. 8(e), Law 1581 of 2012), we apply the procedure best suited to the type of data:
- Account, event, and guest data: physical deletion of records that are not subject to a retention obligation.
- Append-only tables (
payments,ai_invocations,audit_log): these tables are designed to prevent physical deletion (to preserve the integrity of accounting and audit records). Instead, we apply anonymization: we replace the user identifier withNULL, clear the sensitive content, and mark the row as anonymized. This satisfies the right to erasure because the data can no longer be attributed to an identified or identifiable person.
This exception is based on Article 9 of Decree 1377/2013 (retention due to a legal or contractual duty) and is equivalent to “pseudonymization” recognized under the GDPR and the LFPDPPP 2025 / Chilean Law 21.719 frameworks. - Tax records (
paymentsmore than 5 years old and still subject to a DIAN obligation): deletion is deferred until the period under Article 632 of Colombia’s Tax Statute has elapsed; a reasoned response is provided to the data subject within 15 business days.
To request erasure of your data, email [email protected] with the subject “Erasure request.” We respond within 15 business days (extendable by 8 business days) under Article 15 of Law 1581/2012.
12. Security
We apply reasonable technical and organizational measures: TLS encryption in transit, database encryption at rest, role-based access control, an append-only audit log, and encrypted daily backups. You access your account through Google, so you manage two-step verification in your Google account.
If a security breach affects your data and poses a significant risk, we will notify you as soon as possible and within the applicable legal deadlines:
- Colombia: 15 business days (SIC Unified Circular, Title V).
- Brazil: 3 business days (Resolution CD/ANPD 15/2024).
- Chile, Argentina, Ecuador, European Union/Spain: 72 hours.
- Costa Rica: 5 business days.
- Peru: 48 hours (Supreme Decree 016-2024-JUS).
- Mexico: without undue delay (LFPDPPP 2025).
13. Minors
invitas.co is not intended for children under 14 years. If you are between 14 and 18 years old, you need your parent’s or legal guardian’s consent to use the service. If you become aware that a child under 14 has provided us with data, email [email protected] so we can delete it.
For events with underage attendees (for example, quinceañeras), the host is responsible for obtaining any required parental consent.
14. Changes to this Policy
We may update this Policy. If the changes are material, we will notify you at least 10 days in advance by email or a visible notice on the platform. Continuing to use the service after notice means you accept the changes.
15. Contact
- General inquiries: [email protected]
- Privacy and personal data: [email protected]
- Address: Cali, Valle del Cauca, Colombia
To file a complaint with an authority:
- 🇨🇴 Colombia’s SIC: www.sic.gov.co
- 🇲🇽 Secretariat for Anti-Corruption and Good Governance: www.gob.mx/anticorrupcion
- 🇦🇷 Argentina’s AAIP: www.argentina.gob.ar/aaip
- 🇨🇱 APDP (being established; effective Dec. 2026)
- 🇵🇪 Peru’s ANPD: www.gob.pe/minjus
- 🇧🇷 Brazil’s ANPD: www.gov.br/anpd
- 🇪🇨 Ecuadorian APDP: www.protecciondatos.gob.ec
- 🇨🇷 Costa Rica’s PRODHAB: www.prodhab.go.cr
- 🇪🇸 Spain’s AEPD: www.aepd.es
This English version is provided as an informational translation. If there is any discrepancy, the Spanish version prevails.

