Sera ya Faragha
Tarehe ya kuanza kutumika: 30 Oktoba 2026
Mtoa huduma: Effective Activism (effectiveactivism.com), namba ya VAT DK36667621
1. Utangulizi
Sera hii ya Faragha inaeleza jinsi Effective Activism (effectiveactivism.com, nambari ya utambulisho wa VAT DK36667621), inayoendesha Active for Animals ("sisi", "kwetu", "yetu"), inavyochakata data binafsi inapofanya kazi kama mdhibiti wa data chini ya Kanuni ya Jumla ya Ulinzi wa Data (GDPR). Inahusu tovuti hii na jukwaa linalotoa zana za Active for Animals.
Sera hii haihusu data binafsi ambayo mashirika huchakata kwa kutumia zana zetu, kama vile watu wa mawasiliano ambao shirika hufuatilia kwa Engagement Tracker au machapisho ambayo hupanga kwa Kipanga Maudhui ya Mitandao ya Kijamii. Kwa data hiyo, shirika ndilo mdhibiti wa data na sisi tunaichakata kwa niaba yake chini ya makubaliano ambayo shirika hukubali linapoanza kutumia zana.
2. Aina za Data Binafsi Tunazochakata
Tunaweza kuchakata data binafsi ifuatayo katika nafasi yetu kama mdhibiti:
2.1 Akaunti
- Jina na anwani ya barua pepe
- Lugha unayopendelea
- Mashirika unayoyahusika nayo na jukumu lako katika kila moja
- Vipindi vya kuingia na siku ulizoingia
2.2 Watu wa Mawasiliano wa Wateja na Washirika
- Jina
- Anwani ya barua pepe
- Shirika
- Jukumu / cheo
- Historia ya mawasiliano
2.3 Data ya Mawasiliano ya Tovuti
- Mawasilisho ya fomu ya mawasiliano (jina lako, anwani ya barua pepe na ujumbe), ambayo hutumwa kwetu kwa barua pepe na hayahifadhiwi na jukwaa
- Usajili kwenye orodha za kusubiri za zana ambazo bado tunazijenga (anwani yako ya barua pepe, jina la shirika lako na, ukiyatoa, tovuti yake na idadi ya wafanyakazi wake, na jinsi shirika lako linavyohitaji zana hiyo kwa haraka), ambao huhifadhiwa katika hifadhidata ya jukwaa lenyewe, unaweza kusomwa na wasimamizi wa jukwaa wa Active for Animals pekee na huhifadhiwa hadi tutakapoufuta
- Mawasiliano ya barua pepe
2.4 Majibu ya Tafiti
Unapojibu mojawapo ya tafiti zetu za athari za Engagement Tracker, tunahifadhi majibu yako pamoja na utafiti husika, lugha uliyojibu kwayo na wakati ulipoyawasilisha: anwani yako ya barua pepe (inahitajika katika tafiti za miezi 3, miezi 6 na mwaka 1, ni ya hiari katika utafiti wa msingi), jina la shirika lako na, ukiyatoa, tovuti yake na idadi ya wafanyakazi wake, jukumu lako na majibu ya maswali. Tunayatumia, kwa ridhaa yako, kufuatilia utendaji wetu na kuboresha huduma zetu. Majibu ya tafiti huhifadhiwa katika hifadhidata ya jukwaa lenyewe, yanaweza kusomwa na wasimamizi wa jukwaa wa Active for Animals pekee na hayashirikiwi kamwe na wahusika wengine. Tunayahifadhi kwa miaka 2 tangu siku unayoyawasilisha kisha tunayafuta; unaweza kutuomba tufute jibu lako mapema zaidi.
2.5 Kuweka Miadi ya Onyesho au Mazungumzo
Kurasa za "Panga onyesho la bure" na "Panga mazungumzo" zinaonyesha kalenda za kuweka miadi za watoa huduma wetu wa ratiba, Calendly na zcal. Kivinjari chako huwasiliana moja kwa moja na mtoa huduma kalenda inapopakiwa; taarifa unazoweka unapoweka miadi hukusanywa na mtoa huduma huyo na kushirikiwa nasi ili tuweze kufanya mkutano. Kurasa zetu wenyewe hazikusanyi chochote.
2.6 Data ya Kiufundi
- Anwani yako ya mtandao, inayohifadhiwa kwa ajili ya kudhibiti kiwango cha maombi na kushughulikia matumizi mabaya
- Kumbukumbu za uendeshaji, zenye anwani zilizofichwa na bila maudhui ya ujumbe
Hatuchakati kwa makusudi data ya aina maalum.
3. Msingi Halali wa Kuchakata
Tunategemea hasa Maslahi Halali (Ibara ya 6(1)(f) ya GDPR), ikiwemo:
- Kusimamia mahusiano na wateja
- Kuboresha huduma zetu
- Kuendesha shirika letu
- Kuwasiliana na mashirika washirika
- Kulinda usalama wa jukwaa
Tunachakata data ya akaunti ili kutoa zana ambazo shirika lako limeomba (Ibara ya 6(1)(b) ya GDPR), na majibu ya tafiti kwa msingi wa ridhaa unayotoa katika utafiti (Ibara ya 6(1)(a) ya GDPR). Unaweza kuondoa ridhaa yako wakati wowote kwa kuwasiliana nasi.
4. Vidakuzi
Tovuti hii inatumia vidakuzi vilivyo vya lazima kabisa pekee. Hakuna vidakuzi vya ufuatiliaji, uchanganuzi au masoko vinavyotumika. Hivi ndivyo vidakuzi vyote ambavyo jukwaa huweka:
| Kidakuzi | Madhumuni | Muda wa kudumu |
|---|---|---|
| afa_session | Hukuweka ukiwa umeingia. Huwekwa unapoingia na huondolewa unapotoka. | siku 90 baada ya kuingia, au hadi utakapotoka |
| afa_form | Hulinda fomu za kuingia, kujisajili, mawasiliano na tafiti dhidi ya ughushi. Huhifadhi thamani ya nasibu tu. | saa 24 |
| afa_sso | Hufuatilia uingiaji wa mara moja (single sign-on) kupitia mtoa utambulisho wa shirika lako wakati unaendelea. | dakika 10, huondolewa uingiaji unapokamilika |
| afa_contact_sent | Huonyesha uthibitisho mara moja baada ya kutuma fomu ya mawasiliano. Haihifadhi sehemu yoyote ya ujumbe wako. | dakika 5, huondolewa uthibitisho unapoonyeshwa |
Vidakuzi hivi ni vya lazima kabisa kwa ajili ya kuingia na kulinda fomu dhidi ya kughushiwa, na huwekwa chini ya msingi halali wa Maslahi Halali. Hakuna ridhaa inayohitajika kwa vidakuzi hivi chini ya Maagizo ya Faragha ya Kielektroniki (ePrivacy Directive).
Unapofunga taarifa ya vidakuzi, kivinjari chako hukumbuka chaguo hilo katika hifadhi yake yenyewe kwenye kifaa chako. Hicho si kidakuzi na hakitumwi kwetu kamwe.
Kalenda za kuweka miadi kwenye "Panga onyesho la bure" (Calendly) na "Panga mazungumzo" (zcal) hupakiwa kutoka kwa watoa huduma hao, ambao wanaweza kuweka vidakuzi vyao wenyewe chini ya sera zao wenyewe. Hili hutokea kwenye kurasa hizo mbili pekee.
5. Uhifadhi wa Data
Data binafsi huhifadhiwa kwa muda unaohitajika tu kwa madhumuni yaliyoelezwa hapo juu. Jedwali lililo hapa chini ni rejista ya uhifadhi ya jukwaa: kila aina ya data ambayo jukwaa huhifadhi na kwa muda gani.
| Data | Huhifadhiwa kwa | Kuhesabiwa kuanzia |
|---|---|---|
| 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 |
Safu za jedwali hili zinatoka kwenye rejista ya jukwaa na zinaonyeshwa kwa Kiingereza.
6. Uhamishaji wa Kimataifa
Hifadhidata kuu na seva za jukwaa ziko Frankfurt, Ujerumani (EU). Ili zana ziendelee kuwa za haraka kwa mashirika kote ulimwenguni, nakala za hifadhidata za kusoma tu huhifadhiwa Singapore na New York (Marekani). Jukwaa linapangishwa hasa ndani ya EU, lakini huu si ukaaji wa data ndani ya EU: data binafsi pia huhifadhiwa katika nakala hizo. Maombi kwa jukwaa hupitia mtandao wa kimataifa wa Cloudflare.
Pale data binafsi inapohamishwa nje ya EU/EEA, tunategemea:
- Vifungu vya Kawaida vya Mikataba vya Tume ya Ulaya (2021/914), vilivyojumuishwa katika makubaliano ya uchakataji wa data ya watoa huduma wetu
- Kinga zinazofaa za kiufundi na za kishirika
7. Wachakataji Wadogo na Watoa Huduma
Tunatumia watoa huduma wafuatao kuendesha jukwaa. Orodha hii ni rejista ya wachakataji ya jukwaa:
| Mtoa huduma | Huduma | Kile anachotufanyia | Data binafsi inayohusika |
|---|---|---|---|
| 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 |
Safu za jedwali hili zinatoka kwenye rejista ya jukwaa na zinaonyeshwa kwa Kiingereza.
Watoa huduma hawa wamefungwa kimkataba kuchakata data kwa mujibu wa matakwa husika ya ulinzi wa data.
8. Hatua za Usalama
Tunatekeleza hatua zinazofaa za kiufundi na za kishirika kulinda data binafsi, zikiwemo:
- Miundombinu salama ya upangishaji
- Usafirishaji wa data uliosimbwa (HTTPS)
- Udhibiti wa ufikiaji kwa ufikiaji wa kiutawala
- Ufikiaji wa ndani uliodhibitiwa
- Usimbaji fiche wa data nyeti iliyohifadhiwa
- Kutenganisha data ya kila shirika na data ya kila shirika jingine
9. Haki za Wahusika wa Data
Chini ya GDPR, una haki ya:
- Kufikia data yako binafsi
- Kuomba marekebisho
- Kuomba ufutaji
- Kuzuia uchakataji
- Kupinga uchakataji
- Kuhamisha data
- Kuwasilisha malalamiko kwa mamlaka ya usimamizi
Ili kutumia haki zako, wasiliana nasi kupitia: [email protected]
10. Miunganisho ya Akaunti za Mitandao ya Kijamii na Ufutaji wa Data
Sehemu hii inahusu mashirika yanayounganisha Ukurasa wa Facebook, akaunti ya kitaalamu ya Instagram, akaunti ya TikTok au Ukurasa wa shirika wa LinkedIn na Kipanga Maudhui ya Mitandao ya Kijamii kupitia jukwaa letu.
10.1 Tunachohifadhi akaunti inapounganishwa
Shirika lako linapounganisha akaunti ya mitandao ya kijamii, tunahifadhi:
- Vitambulisho vya ufikiaji ambavyo mtandao hutupa kwa akaunti hiyo (vimesimbwa fiche vikiwa vimehifadhiwa; havionyeshwi kwa mtu yeyote kamwe, na havitumwi popote isipokuwa kwa mtandao huo)
- Kitambulishi cha akaunti, jina linaloonyeshwa na anwani ya picha, nani aliiunganisha na lini
- Machapisho yaliyochapishwa kutoka akaunti hiyo katika siku 90 kabla ya kuunganishwa, na yale yaliyochapishwa baadaye, yanayosomwa mara moja kwa siku
- Takwimu za utendaji za machapisho hayo (kama vile ufikiaji, mitazamo na miitikio), zinazosomwa mara moja kwa siku
- Rekodi ya kila chapisho ambalo kipanga kilichapisha, kilipangia muda, kilighairi au kiliondoa kwenye akaunti hiyo: nani aliomba, lini, nini kilitumwa na jibu la mtandao
10.2 Kinachotokea unapotenganisha
Kutenganisha akaunti ya mitandao ya kijamii kwa kitufe cha Tenganisha katika Kipanga Maudhui ya Mitandao ya Kijamii cha shirika lako huondoa tokeni ya ufikiaji iliyohifadhiwa na kusimamisha uingizaji wowote zaidi wa machapisho au data ya utendaji kutoka akaunti hiyo. Tokeni ya ufikiaji hufutwa mara moja, na machapisho ambayo kipanga kilikuwa kimeyapangia muda kwenye akaunti hiyo yanaghairiwa.
Machapisho na takwimu za utendaji zilizokwisha kuingizwa kabla ya kutenganisha hazifutwi kiotomatiki. Zinabaki katika eneo la kazi la shirika lako kama rekodi ya kihistoria, na rekodi ya kile ambacho kipanga kilichapisha inabaki pia.
10.3 Kuomba ufutaji wa data iliyoingizwa
Ikiwa ungependa data ya akaunti ya mitandao ya kijamii ifutwe kabisa, tuma ombi kwa [email protected]. Tafadhali taja jina la shirika lako, mtandao na akaunti (au akaunti) zinazohusika. Tutashughulikia maombi ya ufutaji ndani ya siku 30.
Kisha msimamizi wa jukwaa huchukua hatua katika kila shirika ambalo akaunti hiyo imeunganishwa au iliwahi kuunganishwa, au ambalo lilichapisha au kupangia machapisho kwenye akaunti hiyo:
- hufuta muunganisho na vitambulisho vyake vya ufikiaji, pamoja na machapisho yaliyochapishwa ya akaunti hiyo na takwimu zake za utendaji;
- huondoa jina la akaunti kwenye machapisho yaliyopangwa kwa ajili yake;
- kutoka kwenye rekodi ya kile ambacho kipanga kilichapisha, huondoa jina la akaunti, maudhui yaliyotumwa na jumbe za mtandao, likibakiza tu ukweli kwamba hatua ilichukuliwa, na lini.
Kila ufutaji hurekodiwa katika kumbukumbu ya ukaguzi ya shirika.
10.4 Uondoaji wa data katika ngazi ya mtandao
Unaweza pia kubatilisha ufikiaji wetu wakati wowote katika mipangilio ya mtandao wenyewe: katika Facebook chini ya Settings → Business integrations, katika TikTok chini ya Settings and privacy → Security → Manage app permissions, na katika LinkedIn chini ya Settings → Data privacy → Permitted services. Kubatilisha ufikiaji hapo kuna athari sawa na kutenganisha ndani ya jukwaa letu: kunazuia kusomwa zaidi kwa data lakini hakufuti kiotomatiki data iliyokwisha kusomwa. Ili kuomba ufutaji wa data hiyo, fuata utaratibu ulio katika §10.3 hapo juu.
11. Mamlaka ya Usimamizi
Kama shirika lililo nchini Denmark, mamlaka yetu ya usimamizi ni Datatilsynet (Denmark).
12. Masasisho ya Sera Hii
Tunaweza kusasisha Sera hii ya Faragha ili kuakisi mabadiliko ya matakwa ya kisheria au ya utaratibu wa uendeshaji. Toleo la hivi karibuni litapatikana kila wakati kwenye tovuti yetu, likiwa na tarehe yake ya kuanza kutumika juu ya ukurasa.
Mawasiliano
Maswali kuhusu sera hii yanaweza kutumwa kwa [email protected].
