Skip to content

Privacy Policy

What data is processed, who is answerable for each, what for, who it reaches and how long it is kept. First the essentials; below, the detail.

Last updated:

In short

Causfy processes data from two very different groups of people: those who create causes, with an account on causfy.app, and those who sign them on causfy.com/causas, who do not need an account. This policy explains them separately.

Causfy is answerable for the data of whoever creates a cause. The creator of that cause, who is the one who gathers the signatures, is answerable for the data of whoever signs it: Causfy processes it on their behalf, as processor.

When you sign, your data and the technical data of the signature (such as the IP address and the approximate location) are incorporated into a certificate. You receive it and so does the creator. Causfy stores it encrypted with a key it does not hold in full, so it cannot read it, and erases it when the cause ends and the creator has downloaded it.

Only your first name is shown publicly. You can hide it, and you can delete your signature, from the links in the confirmation email.

The fingerprint of each certificate is recorded on a public blockchain. It contains no personal data and cannot be erased.

We do not sell, rent or transfer personal data to anyone for their own purposes. The data passes through the providers we need to provide the service, which are listed in a table below.

You can exercise your rights by writing to our data protection mailbox, and lodge a complaint with the Spanish Data Protection Agency.

What Causfy is and who is answerable for each piece of data

Causfy is a platform for public causes. A person or organisation (the Creator) creates a cause from their Account, personal or business. The cause is published on the portal, where the public signs it. It can also be supported with a payment called a Boost. Each signature generates a Certificate that proves the support, and the Creator uses it before the Addressee of the petition.

DataWho is answerableCausfy’s role
Account, use of the app and security of Creators and their TeamsCausfyController
Signers of a causeThe Creator of that causeProcessor, while the cause is active and until the Creator downloads the Certificates
Visitors to the portal and the website (browsing, Causfy cookies)CausfyController
Measurement pixels that the Creator adds to their cause (Meta, TikTok, Google)The Creator. The data goes to Meta, TikTok or Google under their responsibilityIt only loads them if the visitor accepts it in the cookie banner
Users of another company that uses the platform under its own brandThat companyProcessor

Terms that appear with an initial capital have the meaning given to them by the Terms of Use and the Terms for Creators.

Who the controller is and how to contact them

1.1. The controller of the platform is CAUSFY GLOBAL TECHNOLOGIES, S.L., a Spanish company. Its full details are set out at the end of this document.

1.2. For any data protection matter:

  • Data protection:

1.3. Data protection officer. You may contact them directly for any matter concerning your data:

  • Data protection officer:

1.4. Supervisory authority. The Spanish Data Protection Agency (Agencia Española de Protección de Datos, AEPD).

1.5. Scope. This Policy applies to causfy.com, including the causes portal at causfy.com/causas, and to causfy.app.

If you create causes: your account on causfy.app

This section is for whoever has an Account. Causfy is answerable for this data.

2.1. What data we process.

DataDetail
AccountFirst name, surname, email, language and username.
OptionalTelephone, if you verify it, and postal address, if you fill it in.
Profile photoThe one from your provider if you sign in with Google, LinkedIn or Facebook. From that provider we receive your name, your email and your photo.
SecurityYour passkeys (the public key and the device name) and the two-step verification secret. The sign-in history, with IP address and approximate location (country, city and internet provider). The devices used, with browser, operating system and a browser fingerprint. An audit log of security actions.
PasswordsThere are none. You sign in with a code sent to your email, with a device passkey or with Google, LinkedIn or Facebook sign-in.
Identity verification, required to download your signers’ Certificates and to receive paymentsIt is carried out by a provider specialised in identity verification, whose name you see when starting verification and when accepting its terms. It processes your document, your selfie, the liveness check and the sanctions list screening, and Causfy keeps only the result: the name appearing on the document, the document details and the result of the screening. The images stay with the provider. In business Accounts, also the registry checks and the key people of the organisation.
Payments receivedTo receive payments you open an account with our card payment provider, or with the institution that opens a bank account in your name, at a partner bank, to receive transfers. In both cases you first accept their terms and their privacy policy, on their own screen, where you see who they are, and you give your identity and bank details directly to them: Causfy does not send them or see them. What Causfy receives from them is your account identifier and its status and, for the bank account, the holder, the IBAN and the BIC. If you prefer to receive payments in cryptocurrencies, we store your wallet address.
Content you publishText, images, video, location of the cause and the Addressees of the petition (name and position of people or bodies, who are third parties).
TeamThe people you invite to manage your Account, their permissions and the invitations, with the email of the person invited.
Commercial communicationsYour consent or your refusal for each channel (email, SMS and WhatsApp), with the date, the version of the text you accepted, the IP address and the device, as evidence.
Artificial intelligence assistantSee point 2.4.

2.2. What we use it for and on what basis.

PurposeLegal basis
Providing the service: your Account, your causes, your Team, the Certificates and payments receivedPerformance of the contract with you (art. 6.1.b GDPR)
Security and prevention of fraud and abuse: sign-in history, devices, audit and IP address reputationOur legitimate interest in keeping the platform secure (art. 6.1.f)
Verifying your identity, and screening sanctions lists, to download your signers’ Certificates and to receive paymentsPerformance of the contract: it is a condition for downloading the Certificates and for activating a means of collection. Causfy does not hold money and is not an obliged entity under anti-money-laundering rules; verification is its own measure against fraud
Moderating content with automated means, with human review when there are doubtsOur legitimate interest in the orderly operation of the platform and compliance with legal obligations. You have the right to have a person review any decision (see rights)
Sending you commercial communicationsYour consent (art. 6.1.a), which you may withdraw for each channel
Service and security notices: sign-in codes, sign-ins from new devices, changes to your detailsPerformance of the contract and our legitimate interest. They cannot be turned off

2.3. How long we keep it.

DataPeriod
Account and contentFor as long as your Account exists.
After deleting the AccountYour data is blocked: it remains outside all use, with restricted access and available only to judges, courts and authorities, for as long as any liability may be claimed. Payment records, 6 years, which is what commercial law requires; the data of your account and your causes, and the identity verification file, 5 years, which is the general limitation period. After that it is all erased.
Sign-in history90 days.
Security audit log12 months.
Devices12 months from last use.
Identity verification fileFor as long as your Account exists. After closure, blocked for 5 years.
Evidence of your commercial consents3 years from when you withdraw them.
Half-completed registrations12 hours.

2.4. The artificial intelligence assistant. It helps you use the app, fills in forms without ever sending them on its own and reads your own data: your causes, the number of signatures and your tickets. It never accesses the data of those who sign; only counts. The model runs on Causfy servers at OVH (Germany). Conversations are not stored. If you speak to it, the audio is transcribed on those same servers and is not stored; for the spoken reply, the text of the reply is sent to a speech synthesis provider in the United States. If the model moves to another provider, this policy will be updated.

2.5. If you connect your own artificial intelligence assistant. You may connect to your Account an external assistant via the MCP protocol; today, Claude, by Anthropic. When you do, what that assistant reads from your Account at your request (your causes, your counts, your team and your tickets) is sent to the company that provides it, which processes it as controller in accordance with its own privacy policy; Causfy does not control that processing. Causfy sends only what the assistant requests within the permissions you gave it, and never personal data of those who sign your causes: only counts and what is already public. We keep the record of the connection (when you authorised it and with what permissions) while it is active, and you may revoke it at any time from the app. The basis is your own request, as part of the service we provide to you.

If you sign a cause

This section is for whoever signs. The Creator of the cause you sign is answerable for this data; Causfy processes it on their behalf, as processor, and here we explain how.

3.1. What a signature is like. No account is needed. You enter your name and your email, and confirm the email with a one-time code. You must be at least 14 years old. The form uses Cloudflare Turnstile to prevent automated submissions.

3.2. Your consent. When signing you tick a box, which is not pre-ticked, by which you give your explicit consent to the Creator to process your data in support of that cause, even though your signature may reveal an opinion. Next to the box you are informed of who the controller is, what the data is used for, that the Certificate is received by the Creator and that the fingerprint of the Certificate remains on a blockchain permanently. We keep the evidence: the version of the text, the time and the steps. There is also a separate, optional box to receive updates about the cause by email.

3.3. The Certificate. Each confirmed signature generates a Certificate in PDF. It serves so that the Creator can demonstrate to the Addressee that each signature is from a real and distinct person, and for that purpose it gathers, in addition to your name, your email, the text of the petition and the date and time, the technical data of the signature: the IP address from which you signed and its approximate location (country, region, city and approximate coordinates), the internet provider, whether the connection went through a VPN or Tor (which helps to detect mass fake signatures), the browser and operating system you used and a device fingerprint; the method by which you identified yourself and, where there is one, the authority that did so; and the record of the verification steps. It is sealed with Causfy’s company certificate and with a qualified timestamp; only a digest (hash) of the document is sent to the timestamp provider. The fingerprint of the Certificate is recorded on a public blockchain: it is a figure from which neither the document nor any personal data can be reconstructed, and the record is permanent. You receive the Certificate, by email when signing, and so does the Creator of the cause.

3.4. What Causfy stores and how. Causfy does not store any of your personal data in the clear and cannot read what it stores. It is not a promise: it is how it is built. For that reason it cannot sell or transfer your data even if it wanted to, and for that reason neither its staff nor anyone who broke into its servers could read it:

DataHow it is kept
CertificateEncrypted with a key of the Creator’s Account that Causfy does not hold in full: one part is held by Causfy and the other only by the Creator, tied to their passkey. Both are needed to open it. The Creator downloads it and it opens in their own browser.
Email, if you did not ask for updatesOnly as an irreversible fingerprint (a hash with a secret key), which serves to prevent signing twice.
Email, if you asked for updatesEncrypted with the same split key. It is only decrypted for an instant, in memory, when the Creator sends an update.
NamePublicly, only the first name. The full name, encrypted.
IP addressOnly as an irreversible fingerprint.
Location, internet provider and device fingerprintOnly inside the encrypted Certificate. Outside it only the country is stored, for statistics.

3.5. What is public. The number of signatures and their breakdown by country. The list of recent signatures, with the first name and how long ago the signature was made (“2 hours ago”), with no surname, location or any other data; if you hid your name, your signature appears without it. The public verification page of a Certificate, which shows only the first name and the date of the signature.

3.6. What the Creator sees. The summary and the list of signatures (first name, date and country) and the full Certificates of their signers, which they download and decrypt in their browser.

3.7. What your data is used for and on what basis. These are the purposes of the Creator as controller:

PurposeLegal basis
Gathering your signature and proving support before the Addressee of the petitionYour explicit consent when signing (arts. 6.1.a and 9.2.a GDPR), because signing certain causes may reveal political opinions, beliefs or trade union membership.
Verifying your email and preventing duplicate or fraudulent signaturesLegitimate interest
Sending you updates about the causeYour consent, with the separate, optional box

3.8. How long it is kept.

SituationWhat happens
Unconfirmed signatureIt is erased after 24 hours.
Active cause (published or paused)Causfy keeps the Certificates and the encrypted data as processor.
Cause closed and Certificates downloaded by the CreatorThe processing ends. Causfy erases the Certificates, the emails and the encrypted full names.
Cause closed without the Creator downloadingThey are notified, and 90 days after closure everything is erased all the same. The cause may be reopened within those 90 days; afterwards, it may not.
What remains after erasureThe cause remains published as finished, with its text and its signature counter, which is a number and not personal data; and the fingerprint of each Certificate on the blockchain, which is permanent and is not personal data either. The list of first names is erased.
The Creator’s copyFrom the moment they download it, it is theirs, as controller, and they keep it under their own responsibility.

3.9. Your rights. With the links in the confirmation email you can delete your signature, which erases the Certificate and the record, hide your first name and unsubscribe from updates. If you delete your signature and the Creator had already downloaded your Certificate, they are obliged to erase their copy, and Causfy informs them. The other rights (access, rectification, portability, objection and restriction) are exercised before the Creator, who is the controller; Causfy assists them as processor. You can also write to us, and we will forward your request to the Creator. The only thing that cannot be erased is the fingerprint on the blockchain, which does not make it possible to identify you.

3.10. Identity levels when signing. Basic signature: only your email is confirmed. Verified identity: at the moment of signing, Causfy checks your identity with your identity document and a selfie: it reads the document details, compares your face with its photo and checks that you are a real person. This check processes biometric data, which is a special category, and is done only with your explicit consent; Causfy performs it with its own system, on its own servers in the European Union, in memory and for the seconds it lasts, without sending your images to third parties. When it finishes nothing remains: neither the images, nor any template of your face, nor any stored identity; if you sign again at this level, you repeat it. The Certificate records your name as it appears on the document and the method used. So that the same person does not sign the same cause twice, an irreversible fingerprint of your document number is stored within that signature, and is erased with it. Before putting this processing into operation, the impact assessment required by law has been carried out. Certified identity: you identify yourself through an official channel of your country, such as a digital identity wallet, a digital certificate or your identity card with chip; that identification is performed by the authority or the provider that issued your credential, in accordance with its own policy, and Causfy receives the result and the signature. In all cases you are told before signing of the level the cause requires, and the certificate states the method used.

Other people whose data we process

4.1. If you pay for a Boost. If you pay by card, the payment data is processed by our payment provider, whose name you see when paying. If you pay with cryptocurrencies, you do so from your own wallet: Causfy stores your wallet address, the transaction identifier, the amount and the currency. The address and the transaction are public on the network you used and permanent, and the conversion to stablecoin is done by decentralised protocols, without any third party receiving your data. Causfy does not store your name or your email. The Creator sees how many Boosts their cause has, never the amounts.

4.2. If you make a Contribution to a cause or to the platform. If you pay by card, the payment data is processed by our payment provider, whose name you see when paying. If you make a bank transfer, it reaches a bank account opened in the Creator’s name, and the institution that manages it sees the details of your transfer like any bank receiving a deposit. If you pay with cryptocurrencies, the operation goes from your wallet to the Creator’s, on a public network. In no case does Causfy receive or keep your card details or your banking credentials: only the confirmation that the operation has been carried out and its amount.

4.3. If you comment. We store an optional name and your message. We do not store your email. Your IP address is used only for a few minutes to prevent spam.

4.4. If you take part in a live stream. The image and voice of whoever streams and of their guests pass through Causfy’s own servers at OVH (France), without Causfy accessing their content. In the chat a name is stored, and the chat history is erased after 24 hours.

4.5. If you report content. From the button on the cause, the report is anonymous: the reason is stored and, if you add it, a detail. From the contact form, we process your name, your email and what you tell us in order to confirm receipt, check the report and communicate the decision to you (see point 4.7).

4.6. If you are the Addressee of a petition. Your name and position are published as the person or body to whom the cause is addressed, and that data is processed with artificial intelligence to moderate and help draft the cause. The basis is the legitimate interest of whoever creates it and freedom of expression. You are not notified individually: the data published is that of your position or public function, and this policy is the information about its processing (art. 14.5.b GDPR).

4.7. If you write to us from the contact form at causfy.com. We process your name, your email, the reason and your message, the country you declare and the country from which you connect, in order to deal with your enquiry and, if it is a content report, process it. The form uses Cloudflare Turnstile to prevent automated submissions.

4.8. If you only visit. What is stored on your device when browsing the website and the portal is explained in the Cookie Policy.

Who else processes the data

5.1. We need providers to provide the service. They act on our behalf, under our instructions, and may not use the data for their own purposes. The payment providers and the identity verification provider are not named here: you see their name when accepting their terms, and it is provided to whoever asks for it. They are these:

ProviderWhat forWhat dataWhere
MongoDB AtlasDatabaseAllEuropean Union (Frankfurt)
OVHcloudServers, in-house artificial intelligence, live streams and monitoringAll that passes through the platformEuropean Union (France and Germany)
Amazon Web ServicesStorage of Certificates, sending of emails, including updates to signers, and safeguarding of encryption keysEncrypted Certificates, emails and the content of the emailsEuropean Union
Microsoft AzureImage storage and artificial intelligence for drafting, moderating and generating imagesImages; texts of the causes and AddresseesEuropean Union
CloudflareContent delivery network, hosting of the website, the portal and the app, anti-bot protectionTraffic and IP addressesUnited States and global network
Card payment providerCard payments and Creators’ collection accounts. It gathers the data directly from whoever pays or receives payment, under its own terms; it returns to Causfy the payment confirmation or the account identifier and its statusPayment data; identity and bank details of whoever receives paymentUnited States and European Union
Institution that opens the collection bank accountsIt opens in the Creator’s name the bank account that receives the transfers for their cause. It gathers their data directly, under its own terms; it returns to Causfy the IBAN assigned and its statusIdentity of the Creator and the transfers that account receivesUnited States and European Union
Identity verification providerVerifying the identity of whoever creates causes (people and companies), not of whoever signs. You see its name when starting verification; it is provided to whoever asks for itDocument, selfie, liveness check and sanctions screeningEuropean Union
Speech synthesis providerVoice of the assistantText of the replies; never your voiceUnited States, with standard contractual clauses
IP address geolocation providerApproximate location of an IP address when signing in or signingIP addressEuropean Union. It declares that it does not log queries and keeps the IP in memory for a maximum of one minute
IP address reputation providerDetecting access from addresses flagged for abuseIP addressUnited States, with standard contractual clauses
Sectigo, DigiCert or GlobalSignQualified timestampOnly a hashDepending on the provider
Your identity wallet, your certificate provider or the authority issuing your document (EUDI wallet, Apple or Google Wallet, FNMT, DNIe and chip cards, SAT e.firma, ICP-Brasil…)Identifying you when you sign with certified identity. They are not Causfy providers: you choose themWhat you authorise in your wallet or certificate; Causfy receives the result and the signatureThat of each authority or provider
A public blockchain (the one Causfy uses at any given time; its name is provided to whoever asks for it)Proof of existence of the CertificateOnly a hashGlobal network
Google, LinkedIn and FacebookSign-in with their accountName, email and photoUnited States
Meta (WhatsApp)Codes and notices via WhatsAppTelephone and messageUnited States and European Union
Place autocomplete providerSuggesting locations as you typeText searched and IP addressEuropean Union
The AI assistant you connect via MCP (today, Claude, by Anthropic)Acting in your Account at your request. It is not a Causfy provider: you choose it and it processes the data as controllerWhat the assistant reads from your Account with the permissions you gave it; never personal data of signersAnthropic, in the United States
Microsoft Clarity and Google AnalyticsAnalytics of the website and the portal, only with your consentBrowsingUnited States
YouTubeVideos of the causes, only when pressing playIP address and cookiesUnited States

5.2. Transfers outside the European Union. When a provider processes data in the United States, the transfer is based on the EU-US Data Privacy Framework, to which most of the providers in the table are certified, or, for the others, on the standard contractual clauses approved by the European Commission. We tell you which applies to each provider, and give you a copy of the clauses, if you ask us.

5.3. The Creator of the cause. They receive the Certificates of those who sign it, under the terms of the signers section.

5.4. Authorities. When required by a rule or a decision.

5.5. Corporate transactions. In the event of a merger, acquisition or transfer of the business, with prior notice.

5.6. We do not sell, rent or transfer personal data to third parties for their own purposes.

Where the data is

6.1. The data is hosted in the European Union.

6.2. Some providers in the table above process data in the United States. In those cases, the transfer is based on the safeguards in point 5.2.

How long each thing is kept

7.1. The retention periods for Creators’ data are in point 2.3 and those for signers in 3.8. These are the others:

DataPeriod
IP address of whoever commentsA few minutes, only against spam.
Chat of a live stream24 hours.
Enquiries and reports received through the contact formWhile they are being processed and, afterwards, the time necessary to deal with possible claims.
Accounting and commercial records6 years.
Records with tax relevance4 years.

Erasing your data, and what cannot be erased

8.1. If you delete your Account. The Account is deactivated immediately and you can no longer sign in. Your causes are marked as finished and remain published, with your name as creator; if you do not want them to be, unpublish them beforehand or ask us afterwards. For 90 days you can download your signers’ Certificates; after that they are erased. Your own data remains blocked for the periods in point 2.3 (5 years, and 6 for payment records) and is then erased. The procedure is on the page Delete your data.

8.2. Data that is not erased immediately. Data that we must keep by legal obligation or to deal with claims remains blocked: outside all use and available only to judges, courts and authorities, for as long as those liabilities may be claimed.

8.3. The fingerprint on the blockchain. The record of a Certificate’s fingerprint is permanent and cannot be erased. It contains no personal data and does not allow anyone to be identified, so it does not affect your right to erase your data.

8.4. Deleting your signature. You can do so at any time with the link in your confirmation email. The Certificate and the record of the signature are erased, and it stops counting.

Your rights

9.1. What rights you have. To access your data, rectify it, erase it, object to its processing, restrict it, obtain it in a portable format, withdraw your consent without affecting what came before and not be subject to decisions based solely on automated processing.

9.2. If you have an Account. From the Privacy section of the app, or by writing to the data protection mailbox. We reply within one month, extendable by two further months if the complexity or the number of requests so requires, notifying you beforehand.

9.3. If you signed a cause. See point 3.9: deleting your signature, hiding your name and unsubscribing from updates you do yourself from the email; the rest, before the Creator, with our help.

9.4. Unsubscribing from communications. From the link that all of them carry, or by channel from the app.

9.5. Identity. We will only ask you to prove your identity if there are reasonable doubts about who is making the request.

9.6. Complaining. You may lodge a complaint with the Spanish Data Protection Agency or with the authority of your country of residence.

Minors

10.1. To create an Account you must be 18 years old, or the age of majority in your country of residence if it is higher. To sign a cause, at least 14.

10.2. Age is established by the person’s own declaration, without additional checks, except where identity verification is required.

10.3. If we detect data of a minor below those ages, we erase it. You can let us know at the data protection mailbox.

Security

11.1. The data of those who sign is encrypted or reduced to irreversible fingerprints. The encryption keys are not in the database, but in a separate system dedicated solely to safeguarding keys, with restricted and logged access. In the case of the Certificates and the emails, the key is split in two, like a bank’s safe deposit box: one half in that Causfy system and the other in the Creator’s passkey, on their device; without both nothing opens, and Causfy cannot open them on its own.

11.2. Provider credentials are stored encrypted with one key per organisation.

11.3. The audit log is chained, so that any tampering is detected.

11.4. There are no passwords: sign-in uses device passkeys, one-time codes and two-step verification.

11.5. No card data passes through our servers; it is handled by our payment provider.

11.6. Technical monitoring does not include emails or contact details.

11.7. Internal access to the data is limited to the staff who need it for their work.

11.8. If a security breach occurs that poses a risk to your rights, we will notify it to the supervisory authority within 72 hours of becoming aware of it and, if the risk is high, also to those affected without delay. When it affects signers’ data, we will notify the Creator, who is the controller, so that they fulfil their own obligations.

Cookies, changes and who we are

12.1. Cookies. What is stored on your device is described in the Cookie Policy, which forms part of this one.

12.2. Changes. This Policy may change. The date of the last review is in the header. If a change affects processing based on your consent, we will inform you beforehand and ask for it again.

12.3. Depending on where you live. In the European Union, the European Economic Area, the United Kingdom and Switzerland the provisions set out here apply, and you may contact the supervisory authority of your country. In other territories we apply the same regime to everyone; if the law of your country grants you additional rights, we will honour them if you write to us at the data protection mailbox.

12.4. Who we are.

CAUSFY GLOBAL TECHNOLOGIES, S.L.

NIF B88744602

C/ Princesa 31, planta 2, puerta 2, 28008 Madrid, España

Registro Mercantil de Madrid, Hoja M-888274, Inscripción 1

  • Data protection:
Browse causesStart a cause