Política de privacidad
Fecha de entrada en vigor: 30 de octubre de 2026
Proveedor: Effective Activism (effectiveactivism.com), VAT ID DK36667621
1. Introducción
La presente Política de privacidad explica cómo Effective Activism (effectiveactivism.com, VAT ID DK36667621), entidad que gestiona Active for Animals («nosotros», «nos», «nuestro»), trata los datos personales cuando actúa como responsable del tratamiento en virtud del Reglamento General de Protección de Datos (RGPD). Abarca este sitio web y la plataforma que presta las herramientas de Active for Animals.
Esta Política no abarca los datos personales que las organizaciones tratan con nuestras herramientas, como los contactos de los que una organización hace seguimiento con el Engagement Tracker o las publicaciones que planifica con el Planificador de contenido para redes sociales. Respecto de esos datos, la organización es la responsable del tratamiento y nosotros los tratamos por cuenta de ella conforme al acuerdo que acepta cuando empieza a utilizar una herramienta.
2. Categorías de datos personales que tratamos
En nuestra condición de responsable del tratamiento, podemos tratar los siguientes datos personales:
2.1 Cuentas
- Nombre y dirección de correo electrónico
- Idioma preferido
- Las organizaciones a las que perteneces y tu función en cada una de ellas
- Las sesiones iniciadas y los días en que iniciaste sesión
2.2 Contactos de clientes y socios
- Nombre
- Dirección de correo electrónico
- Organización
- Función / cargo
- Historial de comunicaciones
2.3 Datos de contacto del sitio web
- Envíos del formulario de contacto (tu nombre, dirección de correo electrónico y mensaje), que se nos remiten por correo electrónico y que la plataforma no almacena
- Inscripciones en la lista de espera de herramientas que aún estamos desarrollando (tu dirección de correo electrónico, el nombre de tu organización y, si los indicas, su sitio web y número de empleados, y la urgencia con la que tu organización necesita la herramienta), que se guardan en la base de datos propia de la plataforma, solo pueden leerlas los administradores de la plataforma de Active for Animals y se conservan hasta que las eliminamos
- Correspondencia por correo electrónico
2.4 Respuestas a encuestas
Cuando respondes a una de nuestras encuestas de impacto de Engagement Tracker, guardamos tus respuestas junto con la encuesta, el idioma en que respondiste y el momento del envío: tu dirección de correo electrónico (obligatoria en las encuestas de 3 meses, 6 meses y 1 año, opcional en la encuesta inicial), el nombre de tu organización y, si los indicas, su sitio web y número de empleados, tu función y las respuestas a las preguntas. Las utilizamos, con tu consentimiento, para medir nuestro rendimiento y mejorar nuestros servicios. Las respuestas se guardan en la base de datos propia de la plataforma, solo pueden leerlas los administradores de la plataforma de Active for Animals y nunca se comparten con terceros. Las conservamos durante 2 años desde el día del envío y después las eliminamos; puedes pedirnos que eliminemos tu respuesta antes.
2.5 Reserva de una demostración o una conversación
Las páginas «Reserva una demostración gratuita» y «Reserva una conversación» muestran los calendarios de reserva de nuestros proveedores de programación, Calendly y zcal. Tu navegador se comunica directamente con el proveedor al cargarse el calendario; los datos que introduces al hacer la reserva los recoge dicho proveedor y nos los comunica para que podamos celebrar la reunión. Nuestras propias páginas no recogen nada.
2.6 Datos técnicos
- Tu dirección de red, que se conserva para limitar la frecuencia de solicitudes y gestionar abusos
- Registros operativos, con las direcciones enmascaradas y sin el contenido de los mensajes
No tratamos intencionadamente categorías especiales de datos.
3. Base jurídica del tratamiento
Nos basamos principalmente en el interés legítimo (art. 6, apartado 1, letra f), del RGPD), en particular para:
- Gestionar las relaciones con los clientes
- Mejorar nuestros servicios
- Gestionar nuestra organización
- Comunicarnos con organizaciones socias
- Mantener la seguridad de la plataforma
Tratamos los datos de las cuentas para prestar las herramientas que ha solicitado tu organización (art. 6, apartado 1, letra b), del RGPD), y las respuestas a las encuestas sobre la base del consentimiento que otorgas en la encuesta (art. 6, apartado 1, letra a), del RGPD). Puedes retirar tu consentimiento en cualquier momento poniéndote en contacto con nosotros.
4. Cookies
Este sitio web utiliza únicamente cookies estrictamente necesarias. No se utilizan cookies de seguimiento, analíticas ni de marketing. Estas son todas las cookies que establece la plataforma:
| Cookie | Finalidad | Duración |
|---|---|---|
| afa_session | Mantiene tu sesión iniciada. Se establece al iniciar sesión y se elimina al cerrar sesión. | 90 días después de iniciar sesión, o hasta que cierres sesión |
| afa_form | Protege los formularios de inicio de sesión, registro, contacto y encuestas frente a falsificaciones. Solo contiene un valor aleatorio. | 24 horas |
| afa_sso | Registra un inicio de sesión único a través del proveedor de identidad de tu organización mientras está en curso. | 10 minutos; se elimina al completarse el inicio de sesión |
| afa_contact_sent | Muestra la confirmación una vez después de enviar el formulario de contacto. No guarda ninguna parte de tu mensaje. | 5 minutos, se elimina al mostrarse la confirmación |
Estas cookies son estrictamente necesarias para iniciar sesión y para proteger los formularios frente a falsificaciones, y se establecen sobre la base jurídica del interés legítimo. Conforme a la Directiva sobre la privacidad y las comunicaciones electrónicas, estas cookies no requieren consentimiento.
Cuando cierras el aviso de cookies, tu navegador recuerda esa elección en su propio almacenamiento en tu dispositivo. No es una cookie y nunca se nos envía.
Los calendarios de reserva de «Reserva una demostración gratuita» (Calendly) y «Reserva una conversación» (zcal) se cargan desde dichos proveedores, que pueden establecer sus propias cookies conforme a sus propias políticas. Esto solo ocurre en esas dos páginas.
5. Conservación de los datos
Los datos personales se conservan únicamente durante el tiempo necesario para los fines descritos anteriormente. La tabla siguiente es el registro de conservación de la plataforma: cada tipo de dato que conserva la plataforma y durante cuánto tiempo.
| Datos | Plazo de conservación | Contado desde |
|---|---|---|
| Operator audit trail entries | 24 months | entry time |
| Visitors' network addresses kept for rate limiting and abuse handling | at most 30 days | request |
| Operator logs | 90 days | entry time |
| Backups | 30 days | backup time |
| Backup markers (object key, size, duration and time of each nightly backup; no personal data) | 400 days | backup time |
| Client addresses on audit entries | XC-RET-009 period (30 days), then removed from the entry | entry time |
| Operator notifications | 90 days | cleared or notified |
| Idempotency keys of creating requests (key, principal, operation, the request hash and the first answer as sent, which may carry the created resource; operations whose answer is a credential are never kept, decision 0017) | 24 hours | request |
| AI request budget counters (requests on the platform’s AI key per organization and month, the operator’s override; counts only) | 13 months | the month counted |
| Geocoding results by normalised query (address text, no names) | 90 days | cached |
| Send log of platform emails: the full recipient address, template, subject, outcome and the transport error with addresses masked; no bodies | 90 days | send |
| Addresses suppressed after a hard bounce or complaint | until cleared by an administrator | bounce |
| Tracking ids and link ids with their tenant, email and link target or hosted-file key (the token-to-target map) | for as long as the platform runs; removed with the tenant | tenant deletion |
| Raw tracking requests (tracking or link id, time, network address, device description) before ingestion | 7 days after ingestion | ingestion of the hit |
| Tracked emails (tracking id, mailbox, send time, mail-merge id, tracking domain, per-email consent and opt-out) over the CRM’s emails | as the CRM email it belongs to (removed with it) | removal of the CRM email; tenant deletion |
| Tracked links and hosted files (target address or file, mailbox, the email they belong to) | for as long as the platform runs; removed with the tenant | tenant deletion |
| Engagement events (kind, time, verification, exclusion, sign-off) with the network address, device description and approximate location of the request | network address, device description and location: 2 years after the event; the event itself as its tracked email | event age (daily retention sweep); removal of the tracked email |
| Self-view reports (the reporting mailbox, the network address and the time) | as the tracked email they concern | removal of the tracked email |
| The organization’s engagement options (GDPR mode, contact management, the AI assistant, a reference to its own key) | for the life of the organization; removed with it | tenant deletion |
| The organization’s own Google Gemini API key, encrypted (XC-SEC-004) | until removed ("Remove key") or replaced; removed with the organization | Remove key; replacement; tenant deletion |
| Stored AI texts (mailbox, generation key, prompt, generated and edited text) and the links to the people they were made for | 180 days after the text was last read or edited | last read or edit |
| AI usage figures (texts generated and edits saved per organization and day; counts only) | 13 months | the day counted |
| Follow-up plans: steps with their subjects, bodies and addresses (whatever the store option, never returned beyond the contract), per-recipient progress | as the tracked email or merge they belong to; stopped steps keep their reason | removal of the anchor email or merge; tenant deletion |
| Send-attempt records of follow-up steps (time, mailbox, plan and step, tracking id, outcome, reason; no bodies) | 13 months | the attempt |
| Automation runs: who or what each run was about, the data of the event that started it, and what each step did (including the addresses an email went to) | 90 days; the event’s data and addresses go at once when the person or record is erased or deleted | the run |
| Automations, their saved versions, email templates and newsletter lists (a list’s API key encrypted, XC-SEC-004) | for the life of the organization or until deleted; removed with it | deletion; tenant deletion |
| Platform-wide follow-up release counters per minute (planned and handed counts only; no tenant, mailbox or recipient) | 2 days | the minute counted |
| Send-attempt records of platform-performed Outlook sends (time, mailbox, request, tracking token, outcome, reason; no bodies) | 13 months | the record’s time |
| Outlook send requests (mailbox, draft id, outcome; the enriched contacts only until the request ends; subject and To recipients only while the organization stores emails) | 13 months after the request ended | the request’s end |
| Failed-send notices (time, reason, sender address; subject and To recipients only while the organization stores emails) | 90 days after dismissal or clearing, and at most 90 days after the notice was raised | the notice’s raising; dismissal by the sender, or a later successful send of the same draft; an erased person’s addresses go at once |
| Usage figures per organization (counts of tracked emails, active mailboxes, mail merges, follow-ups and AI texts; first use; providers), never an email, person or event | the last 53 ISO weeks; the current figures are replaced at every rollup; removed with the organization | week; tenant deletion |
| Counts of tracked emails’ counted events per email, day and figure, and per day (no address, device or location) | with the tracked email they count (removed with it); rebuilt on demand | the email’s removal; tenant deletion |
| The dashboard’s sender list: per mailbox, the stored sender addresses of its tracked emails and their latest stored name | rebuilt from the CRM every hour (an erased or anonymised sender leaves it within the hour); removed with the organization | hourly rebuild; tenant deletion |
| Tracking health counts per day (requests, events per kind, gate drops, failures), numbers only | 13 months (lead default) | day |
| Invoice PDFs uploaded for an egg sale not yet recorded, and replacement invoices never stamped | at most 24 hours after their last use (usable for at least 2) | the last upload, preview or refused report naming them |
| The public network address of each opening of an egg verification page (the time of the opening stays for the farm’s life) | 12 months | the opening |
| The inactive periods of each egg farm and when their alert was sent | for the farm’s life; removed with it | deletion of the farm |
| Consultation responses: the consent statement as shown and its time, the submitted email address, the page’s language, whether and when the supporter confirmed sending their email, the answers, and the link to the person in Contacts | until the organization deletes the response or the person (an erased person’s responses stay anonymised, without the address and the answers) | deletion of the response or the person; tenant deletion |
| Consultation form versions (the saved form, who saved it and when, the comment) | for the consultation’s life; removed with it | deletion of the consultation |
| Planned social media posts: the day, time, status, category and team, each network variant’s copy, hashtags, design link and chosen account, the approval, every version, comments and their mentions | until the organization deletes the post (its comments, versions and files go with it) | deletion of the post; tenant deletion |
| Media uploaded to planned posts (images and videos, publicly reachable at their address on the media host so the networks can fetch them) | as the post and its versions that name them; an upload never saved to a post: 24 hours | deletion of the post; upload |
| Social account connections: the network, the account’s id, name and picture address, who connected it and when, its team, and the access credentials (encrypted) | until disconnected (the credentials are deleted at once); removed with the organization | disconnect; tenant deletion |
| Pending social account connection requests: the member and sign-in session that started it, the accounts offered, the network’s interim grant (encrypted) | 1 hour after it is used or expires (it is valid for 10 minutes) | use or expiry |
| Posts published on connected social accounts (network, post id, account id and name, time, caption, format, link, the planned post it is linked to) and their daily metric readings | until the organization deletes them, or an operator deletes the account’s data on request (§10.3); kept after a disconnect | deletion request; tenant deletion |
| Publishing activity of planned posts: each publish, schedule, cancel and removal, who did it, when, the account, the request sent (never a credential) and the network’s answer | for the life of the organization, also after the post is deleted; an account’s name and the requests sent are removed on a deletion request (§10.3) | tenant deletion; deletion request |
| Deletion requests for a social account’s data (network, account id, the operator’s note, progress) | kept as the record of the deletion | never |
| Watched pages: the address, title, company, tags, owner and recipients, the watched part of the page, the keywords or topic, and the section proposal (short excerpts of the page) | until the organization deletes the watch; removed with the organization | deletion of the watch; tenant deletion |
| Snapshots of a watched page’s text (the watched part, normalised; never the page’s raw content) | the last 30 per watch, and every snapshot a change refers to, for the watch’s life | a newer snapshot; deletion of the watch |
| Changes found on watched pages (the removed and added passages, the summary, the verdict), the members’ feedback on them (useful or not, by whom) and the alert emails sent (recipient, address, time, outcome) | for the watch’s life | deletion of the watch; tenant deletion |
| Checks of watched pages (time, fetch method, outcome, failure reason, duration, size, AI use; no page content) | 13 months | the check |
| Imports of page lists (who imported, when, the counts, the rows that could not be imported and why; never the file) | for the life of the organization | tenant deletion |
| Web page monitoring feasibility runs (the run’s settings, reviewers’ labels of changes, the comparison list of another tool’s alerts) | until the organization is deleted | tenant deletion |
| Responses to the Engagement Tracker impact surveys at the four client-held survey links (survey, language, submission time and the answers, which may include the respondent’s email address and organisation) | 2 years | submission |
| Entries on the waiting lists of the tools in development (the tool, language, submission time, email address, organisation name, website and size if given, and how urgently the organisation needs the tool) | Until an administrator deletes them | submission |
| Single sign-on configuration per tenant (issuer, client id, metadata, certificate; the secret in the credential store) | the life of the tenant | tenant deletion |
| Identifiers of the SAML assertions consumed and the requests they answered (no personal data) | until the assertion’s own expiry | the assertion’s NotOnOrAfter |
| Sign-in sessions (token hash, timestamps); ended rows | 30 days after end | end or expiry |
| Email-change confirmation links (new address, token hash) | 30 days after expiry | expiry |
| Sign-in days per user (user id, day) for the admin usage comparison | 90 days | day |
| Unique sign-ins per week (counts only) | 53 weeks | week |
| Password reset and set links (token hash) | 30 days after expiry | expiry |
| Invitations (address, role, token hash) | 90 days after decision or expiry | decision or expiry |
| Sign-up requests (organization name, website, address, tools, decider and time) | kept as the decision record (phase-1-plan §6); a rejected request is deleted (IAM-RULE-096) | decision |
| Service agreement acceptances (who, when, which version) | the life of the tenant plus 6 years | tenant deletion |
| Offboarding record (tenant name, identifier, dates) | kept | never |
| Uploaded CSV files of a Contacts import | until the run ends; 24 hours for an import that is never started | end of the run, or upload |
| Contacts import records and run reports (row outcomes, values not stored, the records written) | 90 days | end of the run |
| Bulk tag changes (the tag, the records selected, progress) | 30 days | end of the operation |
| Subjects, HTML and plain-text bodies and attachment content of tracked emails, thread messages and CRM history emails | 2 years after the send time, removed within the following 24 hours | send time (registration time without one) |
| Sender and recipient addresses, names and person links on emails (slots and counts stay, anonymised) | 2 years after the send time; kept while the participant is a person synchronised from a connected HubSpot or Salesforce integration | send time; end of the CRM link |
| Subject and bodies of an email handed off by getEmail while it awaits the HubSpot export | 24 hours after the hand-off, or until the export handled it | hand-off |
| The message of a requested send (recipients, subject, bodies, attachments) | until the send ends (sent, failed or uncertain) | end of the send |
| The email records without content: kind, times, send state, recipient counts, message references | the life of the tenant | tenant deletion |
| Erasure audit entries: who, when, trigger, count, the identities of the anonymised records, erased-address markers and their lifts (no erased value) | the life of the tenant and 6 years after it ends | the tenant’s deletion |
| Keyed one-way fingerprints of erased addresses, with the opt-out held against them | the life of the tenant (a lift ends the suppression, not the opt-out) | the tenant’s deletion |
| CRM integration run history (what each sync, write-back and probe did) | 180 days | run start |
| Closed write-backs to connected CRMs | 30 days | write-back closed |
| Platform-performed sends: state, provider references and the masked failure text | 180 days | send finished |
| The once-only record of possibly-stuck Gmail send notifications (INT-RULE-034) | 30 days | noticed |
| Contacts-started Gmail connects: the single-use nonce, its starter and, until the finish step, the parked grant | 1 day (the parked grant: 15 minutes) | connect started |
| Marks that a mailbox’s conversations are read again from a send time | until the next run (at most 90 days) | email became matchable |
| MCP access log: token id, user email and tenant name at issue, client, scopes, issue and expiry times | 24 months | issue time |
| OAuth codes and tokens (hashed) with their grants | codes 1 day after expiry; tokens 30 days after expiry or revocation; grants kept while active | expiry or revocation |
| Operator record of MCP tool calls (user, tenant, tool, filters, row count, token id) | 90 days | call |
Las filas de esta tabla constituyen el registro de la plataforma y se muestran en inglés.
6. Transferencias internacionales
La base de datos principal y los servidores de la plataforma se encuentran en Fráncfort (Alemania, UE). Para que las herramientas sean rápidas para organizaciones de todo el mundo, se mantienen copias de solo lectura de la base de datos en Singapur y Nueva York (Estados Unidos). La plataforma está alojada principalmente en la UE, pero esto no constituye una residencia de datos en la UE: los datos personales también se almacenan en dichas copias. Las solicitudes a la plataforma pasan por la red global de Cloudflare.
Cuando se transfieren datos personales fuera de la UE/EEE, nos basamos en:
- Las cláusulas contractuales tipo de la Comisión Europea (2021/914), incluidas en los acuerdos de tratamiento de datos de nuestros proveedores
- Garantías técnicas y organizativas adecuadas
7. Subencargados y proveedores de servicios
Utilizamos los siguientes proveedores de servicios para gestionar la plataforma. La lista constituye el registro de encargados del tratamiento de la plataforma:
| Proveedor | Servicio | Qué hace para nosotros | Datos personales afectados |
|---|---|---|---|
| DigitalOcean | Hosting | Hosting, managed database with read-only replicas in Singapore and New York, object storage, backups | All platform data, replicated to the read regions under the provider’s DPA and SCCs (plan §3.4) |
| Cloudflare | Edge and human check | TLS termination, caching, routing, abuse protection in front of every host; on the public forms (contact, sign-up, surveys, waiting lists, consultations, volunteer sign-up, directory sign-up), the Turnstile check that the visitor is not a robot, which loads a Cloudflare script and frame in the visitor’s browser | Request metadata including the visitor’s network address; on the public forms, the browser and device characteristics the check collects |
| SolarWinds Observability | Logs and metrics | Operational logs and metrics | Log entries with masked addresses; no bodies or tokens (XC-PRV-005) |
| Calendly | Scheduling widget | The demo booking calendar embedded on the "Book a free demo" page | What a visitor enters to book (name, email address, answers) and their network address, collected by Calendly in the visitor’s browser; the platform stores nothing |
| zcal | Scheduling widget | The conversation booking calendar embedded on the "Book a conversation" page | What a visitor enters to book (name, email address, answers) and their network address, collected by zcal in the visitor’s browser; the platform stores nothing |
| Postmark | Email delivery service | Transactional email: invitations, password resets, sign-up decisions, email-change confirmations and later the emails other sections send | Recipient address and subject of every platform email; the body passes through Postmark and is not retained by the platform |
| Google Maps (map display key) | Maps | The browser map-display key the mail clients use to show event locations (ETC-X-Q Q09); used by the clients, named for completeness | none sent by the platform |
| LocationIQ | Address lookup | Turns an address typed into the platform into map coordinates and a formatted address, and a point chosen on the map into an address; served from its EU region | The address text or the point; no names or account details |
| OpenStreetMap Foundation (Nominatim) | Address lookup (fallback) | The same lookups when LocationIQ does not answer | The address text or the point; no names or account details |
| Network-owner and geolocation data provider | Reference data | Classifying tracking requests (TRK-RULE-050 rules 6 and 7) and the approximate location shown with an event; not configured until AfA supplies the account (phase-4-plan §2) | network addresses of tracking requests (no names) |
| Google Gemini | AI text | Outreach text for organizations with the AI assistant on: fragments, subject lines and follow-up bodies (OUT-CAP-021 to 025) | Prompts, AI context (the recipient’s own email chain, read from the sender’s mailbox) and generated text of organizations with the assistant on; nothing stored by the provider on the platform’s behalf beyond its terms |
| Google Gemini | AI judgement of page changes | Web page monitoring: whether a change on a watched page matters, a short summary of it, and whether text about a member’s topic appeared | The changed passages of the public pages members watch, the page’s title and address, and examples of changes members marked not useful; no member data; nothing stored by the provider on the platform’s behalf beyond its terms |
| Google (Gmail API) | Mailbox provider | Reading replies to tracked emails and sending emails from a tenant’s connected Gmail mailbox, for tenants that connect one (phase-3-plan §6) | Message headers of messages in tracked conversations and, when the tenant stores emails, their subjects, bodies and addresses |
| Microsoft (Microsoft Graph) | Mailbox provider | Change notifications, reading replies to tracked emails and sending emails from a tenant’s connected Outlook mailbox, for tenants that connect one (phase-3-plan §6) | Message headers of messages in tracked conversations and, when the tenant stores emails, their subjects, bodies and addresses |
| Meta (Facebook, Instagram) | Social network | Connecting Facebook Pages and Instagram professional accounts, publishing approved posts to them and reading their published posts and metrics, for organizations that connect one | The post’s text and the addresses of its media, the scheduled time, the Page and account ids; the connecting member signs in to Meta in their own browser |
| TikTok | Social network | Connecting TikTok accounts, publishing approved posts to them or to their TikTok inbox, and reading their published posts and metrics, for organizations that connect one | The post’s text and the addresses of its media, the visibility, interaction and disclosure choices, the account id; the connecting member signs in to TikTok in their own browser |
| Social network | Connecting LinkedIn organisation Pages, publishing approved posts to them and reading their published posts and metrics, for organizations that connect one | The post’s text and its images, the organisation Page id; the connecting member signs in to LinkedIn in their own browser | |
| Canva | Design preview | Shows a planned post’s Canva design link as Canva’s own preview in the post view | The viewer’s network address and browser data, collected by Canva in the viewer’s browser when the preview loads; the platform sends nothing |
| Mailchimp (Intuit) | Newsletter list | Adds people to an organization’s Mailchimp audience when one of its automations has a Newsletter step on that list, with the organization’s own API key (FLW-CAP-014 to 016) | The subscriber’s email address, first and last name and, where the audience has the field, country: of people who gave them on a form and agreed |
| MailerLite | Newsletter list | Adds people to an organization’s MailerLite account and group when one of its automations has a Newsletter step on that list, with the organization’s own API key (FLW-CAP-014 to 016) | The subscriber’s email address, first and last name and country: of people who gave them on a form and agreed |
Las filas de esta tabla constituyen el registro de la plataforma y se muestran en inglés.
Estos proveedores están obligados contractualmente a tratar los datos de conformidad con los requisitos aplicables en materia de protección de datos.
8. Medidas de seguridad
Aplicamos medidas técnicas y organizativas adecuadas para proteger los datos personales, entre ellas:
- Infraestructura de alojamiento segura
- Transmisión cifrada (HTTPS)
- Controles de acceso para el acceso administrativo
- Acceso interno restringido
- Cifrado en reposo de los datos sensibles
- Separación de los datos de cada organización respecto de los de cualquier otra organización
9. Derechos de los interesados
En virtud del RGPD, tienes derecho a:
- Acceder a tus datos personales
- Solicitar su rectificación
- Solicitar su supresión
- Limitar el tratamiento
- Oponerte al tratamiento
- La portabilidad de los datos
- Presentar una reclamación ante una autoridad de control
Para ejercer tus derechos, ponte en contacto con nosotros en: [email protected]
10. Conexión de cuentas de redes sociales y eliminación de datos
Esta sección se aplica a las organizaciones que conectan una página de Facebook o una cuenta de Instagram al Planificador de contenido para redes sociales a través de nuestra plataforma.
10.1 Qué almacenamos cuando se conecta una cuenta
Cuando tu organización conecta una cuenta de redes sociales, almacenamos:
- Un token de acceso que nos autoriza a obtener datos de esa cuenta (almacenado cifrado en reposo)
- El identificador y el nombre visible de la cuenta
- Las publicaciones de esa cuenta incorporadas en el momento de la conexión y en las sincronizaciones posteriores
- Instantáneas de rendimiento (como cifras de alcance e interacción) de dichas publicaciones
10.2 Qué ocurre cuando desconectas una cuenta
Desconectar una cuenta de redes sociales mediante el botón Desconectar de la configuración del Planificador de contenido para redes sociales de tu organización elimina el token de acceso almacenado e impide cualquier nueva incorporación de publicaciones o datos de rendimiento de esa cuenta. El token de acceso se elimina de inmediato.
Las publicaciones y las instantáneas de rendimiento incorporadas antes de la desconexión no se eliminan automáticamente. Permanecen en el espacio de trabajo de tu organización como registro histórico del contenido y las métricas importados.
10.3 Solicitud de supresión de los datos incorporados
Si deseas que se eliminen definitivamente las publicaciones y los datos de rendimiento ya incorporados, envía una solicitud a [email protected]. Indica el nombre de tu organización y la cuenta o cuentas de redes sociales afectadas. Atenderemos las solicitudes de supresión en un plazo de 30 días.
10.4 Eliminación de datos a nivel de plataforma
También puedes revocar en cualquier momento nuestro acceso a tu página de Facebook o tu cuenta de Instagram a través de la propia configuración de aplicaciones de Meta. Revocar el acceso desde allí tiene el mismo efecto que desconectar la cuenta en nuestra plataforma: impide nuevas incorporaciones, pero no elimina automáticamente los datos ya incorporados. Para solicitar la eliminación de esos datos, sigue el procedimiento descrito en el §10.3 anterior.
11. Autoridad de control
Como organización establecida en Dinamarca, nuestra autoridad de control es Datatilsynet (Dinamarca).
12. Actualizaciones de esta Política
Podemos actualizar esta Política de privacidad para reflejar cambios en los requisitos legales o en nuestras prácticas operativas. La versión más reciente estará siempre disponible en nuestro sitio web, con su fecha de entrada en vigor en la parte superior.
Contacto
Las preguntas sobre esta política pueden dirigirse a [email protected].