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.
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 is incorporated into a certificate that you receive and so does the creator. Causfy stores it encrypted in such a way that it cannot read it on its own, and erases it when the creator confirms that they have downloaded it or, at the latest, 90 days after the cause finishes.
Publicly, only the initial of your name followed by four asterisks appears (for example, “J****”). You can delete your signature from the link 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.
| Data | Who is answerable | Causfy’s role |
|---|---|---|
| Account, use of the app and security of Creators and their Teams | Causfy | Controller |
| Signers of a cause | The Creator of that cause | Processor, while the cause is active or paused and, once finished, until the Creator confirms that they have decrypted the Certificates |
| Visitors to the portal and the website (browsing, Causfy cookies) | Causfy | Controller |
| Users of another company that uses the platform under its own brand | That company | Processor |
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.
| Data | Detail |
|---|---|
| Account | First name, surname, email, language and username. |
| Optional | Telephone, if you verify it, and postal address, if you fill it in. |
| Profile photo | The 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. |
| Security | Your 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. |
| Passwords | There 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 payments | It is carried out by a provider specialised in identity verification, on behalf of Causfy, whose name you see when starting verification; we also provide it to you if you ask. It processes your document, your selfie, the liveness check and the sanctions list screening, with your explicit consent. The images and the biometric data are erased within a maximum of one month from verification, and Causfy keeps only the result: the name appearing on the document, the document details, the check that you are of age and the result of the screening. The provider may process some data in a limited way, pseudonymised or aggregated, as an independent controller, for the security of its service and the prevention of fraud, in accordance with the terms you accept on its screen. In business Accounts, also the registry checks and the key people of the organisation. |
| Payments received | To 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 publish | Text, images, video, location of the cause and the Addressees of the petition (name and position of people or bodies, who are third parties). |
| Team | The people you invite to manage your Account, their permissions and the invitations, with the email of the person invited. |
| Commercial communications | Your 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 assistant | See point 2.4. |
2.2. What we use it for and on what basis.
| Purpose | Legal basis |
|---|---|
| Providing the service: your Account, your causes, your Team, the Certificates and payments received | Performance 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 reputation | Our legitimate interest in keeping the platform secure (art. 6.1.f) |
| Verifying your identity and that of your organisation, and screening sanctions lists, to download the Certificates and activate means of collection | For the document details and the screening: performance of the contract (art. 6.1.b) and our legitimate interest in preventing fraud (art. 6.1.f). For the selfie and the liveness check, which are biometric data: your explicit consent (art. 9.2.a), which you give before starting verification. If you do not give it, you will not be able to download Certificates or receive payments. 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 doubts | Our 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 communications | Your 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 details | Performance of the contract and our legitimate interest. They cannot be turned off |
2.3. How long we keep it.
| Data | Period |
|---|---|
| Account and content | For as long as your Account exists. |
| After deleting the Account | Your 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 history | 90 days. |
| Security audit log | 12 months. |
| Devices | 12 months from last use. |
| Identity verification file | For as long as your Account exists. After closure, blocked for 5 years. |
| Images and biometric data from verification, held by the provider | One month at most. |
| Evidence of your commercial consents | 3 years from when you withdraw them. |
| Half-completed registrations | 12 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 16 years old, and 18 to sign with verified identity. 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, which serves so that the Creator can demonstrate to the Addressee that each signature is from a real and distinct person. It contains your name as you wrote it, your email, the text of the petition, the date and time, the country from which you signed, whether the connection went through a VPN, a proxy or Tor, the browser and operating system you used, 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. You receive it, by email when signing, and so does the Creator of the cause.
3.4. What Causfy stores and how. Your data is processed in the clear only while the signature is taking place, in memory. Afterwards, the personal data of your signature is encrypted in such a way that only the Creator can open it, with their passkey: Causfy cannot read on its own what it stores, and for that reason it cannot sell or transfer your data.
| Data | How it is kept |
|---|---|
| Certificate, full name and email | Encrypted. Only the Creator can open them, with their passkey. |
| Email, to prevent duplicate signatures | As a pseudonymised code (HMAC), calculated with a secret key held in our secrets manager and the identifier of the cause. It does not make it possible to recover your email or to link signatures from different causes. |
| Email, if you asked for updates | Additionally, encrypted like the Certificate. If you unsubscribe, the encrypted copy is erased and only the code is kept. |
| IP address | It is not stored. To curb mass submissions, a temporary code is used that is erased within an hour. |
| What remains readable | The initial of your name, to display it; the country, for statistics; the date of the signature; the anti-duplicate code; and a random reference for the signature. |
3.5. What is public. The number of signatures and their breakdown by country. The list of recent signatures, with the initial of your name followed by four asterisks (“J****”) and how long ago the signature was made, with no other data. The public verification page of a Certificate, which only confirms that the document exists and has not been altered, and its date.
3.6. What the Creator sees. While the cause is active or paused, the summary of signatures: totals, dates and countries. When they finish it, the full Certificates of their signers, which they download and decrypt on their own device.
3.7. What your data is used for and on what basis. These are the purposes of the Creator as controller:
| Purpose | Legal basis |
|---|---|
| Gathering your signature and proving support before the Addressee of the petition | Your 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 signatures | Legitimate interest |
| Sending you updates about the cause | Your consent, with the separate, optional box |
| Verifying your identity with your document and a selfie (“verified identity” level) | Your explicit consent, with a specific box before verification (arts. 6.1.a and 9.2.a GDPR). You may refuse; if you do, you will not be able to sign at this level. |
3.8. How long it is kept.
| Situation | What happens |
|---|---|
| Unconfirmed signature | It is erased after 24 hours. |
| Active or paused cause | Causfy keeps the encrypted Certificates as processor. They cannot be downloaded yet. If you delete your signature, Causfy erases your Certificate. |
| Finished cause | A finished cause cannot be activated again. The Creator can download the Certificates, encrypted, and decrypt them on their own device. If you delete your signature before they download them, Causfy erases your Certificate. |
| The Creator confirms that they have decrypted them | The processing ends and Causfy erases all the Certificates and the other encrypted data of the cause. |
| The Creator does not confirm within 90 days | Causfy notifies them beforehand and, 90 days after the cause finishes, erases everything all the same. |
| What is erased | The Certificates, the encrypted emails, the anti-duplicate codes and any link between your signature and its record on the blockchain. Backups disappear within a maximum of 30 days; if they had to be restored, the pending erasures are applied again first. |
| What remains | The cause published as finished, with its text and its signature counter; the record of each Certificate on the blockchain, which is permanent; and the verification page, which only confirms that the document existed and has not been altered, without showing your name. |
| The Creator’s copy | From the moment they download it, it is theirs, as controller. If you delete your signature afterwards, Causfy notifies them that they must erase your Certificate. |
3.9. Your rights. With the links in the confirmation email you can delete your signature, which erases the Certificate and the record, 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: only for people aged 18 or over. At the moment of signing, Causfy checks your identity with your identity document and a selfie: it reads the document details, checks that you are a real person and compares your face with the photo on the document. It is a processing of biometric data and is done only with your explicit consent, which is requested from you with a box before the first photo. The check is performed by a system from a specialised provider that Causfy runs on a machine of its own, in the European Union, with no internet connection; neither that provider nor any other third party receives your images, which travel encrypted through our network provider. If the document indicates that you are under 18, verification ends before the liveness check. When it finishes, no image or template of your face remains: within your signature, encrypted, remain your first name and surname, the type, country and number of your document, your age in years, the result of the check and a pseudonymised code to prevent you from signing the same cause twice. 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. The providers in this table act on our behalf and under our instructions, except those indicated as controllers: the sign-in services of Google, LinkedIn and Facebook, YouTube, Meta (WhatsApp), Google Analytics and the identity verification provider as regards what it processes for its own security, which process certain data for their own purposes in accordance with their policies. 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:
| Provider | What for | What data | Where |
|---|---|---|---|
| MongoDB Atlas | Database | All | European Union (Frankfurt) |
| OVHcloud | Servers, in-house artificial intelligence, live streams and monitoring | All that passes through the platform | European Union (France and Germany) |
| Amazon Web Services | Storage of Certificates, sending of emails, including updates to signers, and safeguarding of encryption keys | Encrypted Certificates, emails and the content of the emails | European Union |
| Microsoft Azure | Image storage and artificial intelligence for drafting, moderating and generating images | Images; texts of the causes and Addressees | European Union |
| Cloudflare | Content delivery network, hosting and anti-bot protection; the traffic, including the identity verification images, passes encrypted through its network without it keeping it | Traffic and IP addresses | United States and global network |
| Card payment provider | Card 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 status | Payment data; identity and bank details of whoever receives payment | United States and European Union |
| Institution that opens the collection bank accounts | It 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 status | Identity of the Creator and the transfers that account receives | United States and European Union |
| Identity verification provider | Verifying 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 it | Document, selfie, liveness check and sanctions screening | European Union |
| Speech synthesis provider | Voice of the assistant | Text of the replies; never your voice | United States, with standard contractual clauses |
| IP address geolocation provider | Approximate location of an IP address when signing in or signing | IP address | European Union. It declares that it does not log queries and keeps the IP in memory for a maximum of one minute |
| IP address reputation provider | Detecting access from addresses flagged for abuse | IP address | United States, with standard contractual clauses |
| Sectigo, DigiCert or GlobalSign | Qualified timestamp | Only a hash | Depending 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 them | What you authorise in your wallet or certificate; Causfy receives the result and the signature | That 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 Certificate | Only a hash | Global network |
| Google, LinkedIn and Facebook | Sign-in with their account | Name, email and photo | United States |
| Meta (WhatsApp) | Codes and notices via WhatsApp | Telephone and message | United States and European Union |
| Place autocomplete provider | Suggesting locations as you type | Text searched and IP address | European 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 controller | What the assistant reads from your Account with the permissions you gave it; never personal data of signers | Anthropic, in the United States |
| Google Analytics | Analytics of the causfy.com website, only with your consent; never on the causes portal or when signing | Browsing | United States |
| YouTube | Videos of the causes, only when pressing play | IP address and cookies | United 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. Some providers in the table above process data in the United States or on their global network, with 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:
| Data | Period |
|---|---|
| IP address of whoever comments | A few minutes, only against spam. |
| Chat of a live stream | 24 hours. |
| Enquiries and reports received through the contact form | While they are being processed and, afterwards, the time necessary to deal with possible claims. |
| Accounting and commercial records | 6 years. |
| Records with tax relevance | 4 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. When each Certificate is created, a figure calculated from the complete document (its hash) is recorded on a public blockchain, with no other data. From it, the Certificate cannot be reconstructed nor can it be known which cause it belongs to. Only whoever holds a copy of the Certificate (you, the Creator and, if it is handed over to them, the Addressee) can check that it existed on that date and has not been modified. The record is permanent. When you delete your signature, Causfy erases the Certificate and any link between your signature and its record, and the Creator is obliged to erase their copy; from then on the record can only be linked to you through the copies legitimately kept by those who already had them.
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 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 16; to sign with verified identity, 18.
10.2. Age is established by the person’s own declaration. When signing with verified identity it is checked automatically against the document, without storing the date of birth.
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 personal data of those who sign is encrypted in such a way that Causfy cannot read it on its own, or reduced to pseudonymised codes. The keys Causfy uses are in a secrets manager separate from the database, with restricted and logged access. Identity verification runs on a machine isolated from the internet.
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, Sección 8.ª, Hoja M-888274, Inscripción 1.ª
- Data protection: