Política de Privacidade
Data de entrada em vigor: 30 de outubro de 2026
Fornecedor: Effective Activism (effectiveactivism.com), VAT ID DK36667621
1. Introdução
A presente Política de Privacidade explica como a Effective Activism (effectiveactivism.com, VAT ID DK36667621), entidade que gere a Active for Animals («nós», «nos», «nosso»), trata dados pessoais quando atua como responsável pelo tratamento ao abrigo do Regulamento Geral sobre a Proteção de Dados (RGPD). Abrange este website e a plataforma que disponibiliza as ferramentas da Active for Animals.
Esta Política não abrange os dados pessoais que as organizações tratam com as nossas ferramentas, como os contactos que uma organização acompanha com o Engagement Tracker ou as publicações que planeia com o Planeador de conteúdos para redes sociais. Relativamente a esses dados, a organização é a responsável pelo tratamento e nós tratamo-los por conta dela ao abrigo do acordo que aceita quando começa a utilizar uma ferramenta.
2. Categorias de dados pessoais que tratamos
Na qualidade de responsável pelo tratamento, podemos tratar os seguintes dados pessoais:
2.1 Contas
- Nome e endereço de e-mail
- Língua preferida
- As organizações a que pertence e a sua função em cada uma
- As sessões iniciadas e os dias em que iniciou sessão
2.2 Contactos de clientes e parceiros
- Nome
- Endereço de e-mail
- Organização
- Função / cargo
- Histórico de comunicações
2.3 Dados de contacto do website
- Submissões do formulário de contacto (o seu nome, endereço de e-mail e mensagem), que nos são enviadas por e-mail e não são armazenadas pela plataforma
- Inscrições na lista de espera de ferramentas que ainda estamos a desenvolver (o seu endereço de e-mail, o nome da sua organização e, se os indicar, o respetivo sítio web e número de colaboradores, e o grau de urgência com que a sua organização precisa da ferramenta), que são guardadas na base de dados da própria plataforma, só podem ser lidas pelos administradores da plataforma Active for Animals e são conservadas até as eliminarmos
- Correspondência por e-mail
2.4 Respostas a inquéritos
Quando responde a um dos nossos inquéritos de impacto do Engagement Tracker, guardamos as suas respostas com o inquérito, o idioma em que respondeu e o momento do envio: o seu endereço de e-mail (obrigatório nos inquéritos de 3 meses, 6 meses e 1 ano, opcional no inquérito inicial), o nome da sua organização e, se os indicar, o respetivo sítio web e número de colaboradores, a sua função e as respostas às perguntas. Utilizamo-las, com o seu consentimento, para acompanhar o nosso desempenho e melhorar os nossos serviços. As respostas são guardadas na base de dados da própria plataforma, só podem ser lidas pelos administradores da plataforma Active for Animals e nunca são partilhadas com terceiros. Conservamo-las durante 2 anos a contar do dia do envio e depois eliminamo-las; pode pedir-nos que eliminemos a sua resposta mais cedo.
2.5 Marcação de uma demonstração ou de uma conversa
As páginas «Marque uma demonstração gratuita» e «Marque uma conversa» apresentam os calendários de marcação dos nossos fornecedores de agendamento, Calendly e zcal. O seu navegador comunica diretamente com o fornecedor quando o calendário é carregado; os dados que introduz ao fazer a marcação são recolhidos por esse fornecedor e partilhados connosco para que possamos realizar a reunião. As nossas próprias páginas não recolhem nada.
2.6 Dados técnicos
- O seu endereço de rede, conservado para limitação de pedidos e tratamento de abusos
- Registos operacionais, com os endereços mascarados e sem o conteúdo das mensagens
Não tratamos intencionalmente categorias especiais de dados.
3. Fundamento jurídico do tratamento
Baseamo-nos principalmente no interesse legítimo (artigo 6.º, n.º 1, alínea f), do RGPD), nomeadamente para:
- Gerir as relações com os clientes
- Melhorar os nossos serviços
- Gerir a nossa organização
- Comunicar com organizações parceiras
- Manter a plataforma segura
Tratamos os dados das contas para disponibilizar as ferramentas que a sua organização solicitou (artigo 6.º, n.º 1, alínea b), do RGPD), e as respostas aos inquéritos com base no consentimento que dá no inquérito (artigo 6.º, n.º 1, alínea a), do RGPD). Pode retirar o seu consentimento a qualquer momento contactando-nos.
4. Cookies
Este website utiliza apenas cookies estritamente necessários. Não são utilizados cookies de rastreamento, analíticos nem de marketing. Estes são todos os cookies que a plataforma define:
| Cookie | Finalidade | Duração |
|---|---|---|
| afa_session | Mantém a sua sessão iniciada. É definido quando inicia sessão e removido quando termina sessão. | 90 dias após iniciar sessão, ou até terminar sessão |
| afa_form | Protege os formulários de início de sessão, registo, contacto e inquéritos contra falsificação. Contém apenas um valor aleatório. | 24 horas |
| afa_sso | Acompanha um início de sessão único através do fornecedor de identidade da sua organização enquanto está em curso. | 10 minutos; removido quando o início de sessão é concluído |
| afa_contact_sent | Mostra a confirmação uma vez depois de enviar o formulário de contacto. Não guarda nenhuma parte da sua mensagem. | 5 minutos, removido quando a confirmação é mostrada |
Estes cookies são estritamente necessários para iniciar sessão e para proteger os formulários contra falsificação, e são definidos com base no interesse legítimo. Ao abrigo da Diretiva Privacidade Eletrónica, estes cookies não requerem consentimento.
Quando fecha o aviso de cookies, o seu navegador memoriza essa escolha no seu próprio armazenamento no seu dispositivo. Não se trata de um cookie e nunca nos é enviado.
Os calendários de marcação de «Marque uma demonstração gratuita» (Calendly) e «Marque uma conversa» (zcal) são carregados a partir desses fornecedores, que podem definir os seus próprios cookies ao abrigo das suas próprias políticas. Isto acontece apenas nessas duas páginas.
5. Conservação dos dados
Os dados pessoais são conservados apenas durante o tempo necessário para as finalidades acima descritas. A tabela abaixo é o registo de conservação da plataforma: cada tipo de dados que a plataforma conserva e durante quanto tempo.
| Dados | Prazo de conservação | Contado a partir de |
|---|---|---|
| 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 |
As linhas desta tabela constituem o registo da plataforma e são apresentadas em inglês.
6. Transferências internacionais
A base de dados principal e os servidores da plataforma situam-se em Frankfurt, na Alemanha (UE). Para que as ferramentas sejam rápidas para organizações de todo o mundo, são mantidas cópias só de leitura da base de dados em Singapura e Nova Iorque (Estados Unidos). A plataforma está alojada principalmente na UE, mas isto não constitui residência de dados na UE: os dados pessoais também são armazenados nessas cópias. Os pedidos à plataforma passam pela rede global da Cloudflare.
Quando os dados pessoais são transferidos para fora da UE/EEE, baseamo-nos em:
- Cláusulas contratuais-tipo da Comissão Europeia (2021/914), incluídas nos acordos de tratamento de dados dos nossos fornecedores
- Garantias técnicas e organizativas adequadas
7. Subcontratantes e prestadores de serviços
Utilizamos os seguintes prestadores de serviços para gerir a plataforma. A lista constitui o registo de subcontratantes da plataforma:
| Fornecedor | Serviço | O que faz por nós | Dados pessoais envolvidos |
|---|---|---|---|
| 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 |
As linhas desta tabela constituem o registo da plataforma e são apresentadas em inglês.
Estes prestadores estão contratualmente obrigados a tratar os dados de acordo com os requisitos de proteção de dados aplicáveis.
8. Medidas de segurança
Aplicamos medidas técnicas e organizativas adequadas para proteger os dados pessoais, incluindo:
- Infraestrutura de alojamento segura
- Transmissão cifrada (HTTPS)
- Controlos de acesso para o acesso administrativo
- Acesso interno restrito
- Cifragem dos dados sensíveis em repouso
- Separação dos dados de cada organização dos de todas as outras organizações
9. Direitos dos titulares dos dados
Ao abrigo do RGPD, tem o direito de:
- Aceder aos seus dados pessoais
- Solicitar a retificação
- Solicitar o apagamento
- Limitar o tratamento
- Opor-se ao tratamento
- Portabilidade dos dados
- Apresentar reclamação a uma autoridade de controlo
Para exercer os seus direitos, contacte-nos através de: [email protected]
10. Ligação de contas de redes sociais e eliminação de dados
Esta secção aplica-se às organizações que ligam uma Página do Facebook ou uma conta do Instagram ao Planeador de conteúdos para redes sociais através da nossa plataforma.
10.1 O que armazenamos quando uma conta é ligada
Quando a sua organização liga uma conta de redes sociais, armazenamos:
- Um token de acesso que nos autoriza a obter dados dessa conta (armazenado cifrado em repouso)
- O identificador e o nome apresentado da conta
- As publicações dessa conta importadas no momento da ligação e nas sincronizações seguintes
- Instantâneos de desempenho (como valores de alcance e envolvimento) dessas publicações
10.2 O que acontece quando desliga uma conta
Desligar uma conta de redes sociais através do botão Desligar nas definições do Planeador de conteúdos para redes sociais da sua organização remove o token de acesso armazenado e impede qualquer nova importação de publicações ou dados de desempenho dessa conta. O token de acesso é eliminado de imediato.
As publicações e os instantâneos de desempenho já importados antes de a conta ser desligada não são eliminados automaticamente. Permanecem no espaço de trabalho da sua organização como registo histórico dos conteúdos e métricas importados.
10.3 Pedido de apagamento dos dados importados
Se pretender que as publicações e os dados de desempenho já importados sejam eliminados definitivamente, envie um pedido para [email protected]. Indique o nome da sua organização e a(s) conta(s) de redes sociais em causa. Daremos seguimento aos pedidos de apagamento no prazo de 30 dias.
10.4 Remoção de dados ao nível da plataforma
Pode também revogar a qualquer momento o nosso acesso à sua Página do Facebook ou conta do Instagram através das próprias definições de aplicações da Meta. Revogar o acesso nesse local tem o mesmo efeito que desligar a conta na nossa plataforma: impede novas importações, mas não elimina automaticamente os dados já importados. Para pedir a eliminação desses dados, siga o procedimento descrito no §10.3 acima.
11. Autoridade de controlo
Enquanto organização sediada na Dinamarca, a nossa autoridade de controlo é a Datatilsynet (Dinamarca).
12. Atualizações desta Política
Podemos atualizar esta Política de Privacidade para refletir alterações nos requisitos legais ou nas práticas operacionais. A versão mais recente estará sempre disponível no nosso website, com a respetiva data de entrada em vigor no topo.
Contacto
As questões sobre esta política podem ser dirigidas a [email protected].