Privacy policy of AmbarMark
Version: 1.6. In force since: 18 November 2026.
What data we process, why, for how long, and how to exercise your rights.
This policy is written in two layers. The first one is a short summary shown next to the registration form and next to each signature request. The second one is the full information. Spanish data protection law allows it to be presented this way.
Second layer: full information
1. Who is responsible for your data
The controller is the person or company that decides why and how personal data is used. For this service it is:
- Aitor Fernández Martín
- Tax identification number (NIF): 09442216A
- Address: C/ Víctor Hugo, nº 4, dcha, 28004 Madrid
- Contact email: aitorcoontigo@gmail.com
- Email for data protection matters: aitorcoontigo@gmail.com. We have not appointed a data protection officer, the person in charge of monitoring compliance with data protection law; questions and requests about your data are handled directly by the controller.
Aitor Fernández Martín is the controller of the account data, the billing data, the security data of the service and the data of its own website. In addition, it processes on behalf of its customers the documents they upload and the data of the people they ask to sign. For that data Aitor Fernández Martín is a processor and the controller is the customer who sends the document, under annex 2 of the terms and conditions of use. If you are a signer and want to exercise your rights over a specific document, contact the person who sent it to you; if you write to us, we will pass your request on to them.
2. What data we process
Data of your account:
- Name.
- Email address.
- Password. We do not store it as it is: we only store an irreversible fingerprint, a mathematical summary from which the password cannot be rebuilt.
- Single-use links we send you by email: one to activate the account when you register, valid for 1 day, and another one to choose a new password if you forget it, valid for 30 minutes.
- Single-use code sent by email to the person who has to sign a document, to check that they have access to that email address. It does not check who the person is. It is valid for 15 minutes.
- Record of your acceptance of the terms, with the accepted version and the date.
Data of each signature (the evidence trail, that is, the proof of what was signed, with which email address and when):
- Name and email of each signer.
- IP address from which the signature was made, which is the number that identifies the internet connection at that moment.
- Date and time of each step.
- Document fingerprint, a unique code calculated from the content of the file that lets anyone check whether the document has been changed.
- Time stamp issued by an external entity, FreeTSA and, as a fallback, DigiCert, which serves as evidence that the document existed at a specific moment.
- Audit log: the ordered list of actions performed on the document.
- Opening of the document, or "document viewed": before signing, the document has to be opened at least once. It does not have to be downloaded, opening it is enough. When you open it we keep the date and time, the IP address, the user agent (explained in the next point) and the SHA-256 fingerprint of the PDF served to you, which is a code calculated from the file that identifies exactly which version you had in front of you.
- Technical connection data when you open the document and when you sign: the user agent, which is the text in which your browser states which program and which system it uses; the time zone and the language set in your browser.
Additional signals of the act of signing, only if you accept them. Each one has its own checkbox on the signing page, not ticked. If you do not accept them, or if your browser does not provide them, you can sign all the same:
- Stroke dynamics of the signature, only if you draw it by hand: the points of the stroke with their position and the moment they were drawn, the type of pointer (mouse, touch screen or pen) and the pressure, if the device provides it. We treat it as biometric data, that is, data about how a person behaves that the law protects in a special way (articles 4(14) and 9 GDPR). It is voluntary and it is not a requirement to sign.
- Browser location: the latitude and longitude provided by your browser, rounded so that they do not point to an exact spot, the accuracy stated by the browser itself, in metres, and the date and time. Your browser obtains it only when you allow it, with its own checkbox, separate from the stroke one; we do not use external services to infer your location from the IP address. If you do not allow it, or your browser does not provide it, you sign all the same.
Signature drawn on the phone, or phone handoff, only if you choose to use it. On the signing page on the computer you can ask for a QR code or a link to draw the signature with your finger on your phone. You can also ask for that link to be sent to the email address the signature request was sent to, and to no other. It is optional: you can draw the signature on the computer or sign without drawing it.
- What the phone provides: only the image of the signature you draw and, if you accept them on the phone itself with their checkboxes, not ticked, the stroke dynamics and the location of the phone. The phone cannot complete the signature: the signature is accepted on the computer, with the code sent to your email and after having opened the document.
- What we keep from the phone as evidence: its IP address, its user agent, its time zone and its language, and the date and time of each step, that is, when the link is created, when the drawing arrives and when it is accepted or discarded on the computer. If you give the location on the computer and also on the phone, they are kept separately, each one stating which device it comes from.
- The phone link works only once and expires soon, within the period set by the configuration of the service. We do not keep the link, only its SHA-256 fingerprint, from which it cannot be rebuilt.
- Before letting you draw, the phone page shows you the title of the document, who sends it, your name and your email with some of its letters hidden, so that you can check that the signature is yours.
- Drawing the signature on the phone does not change its type: it is still a simple electronic signature. The phone data shows which device the drawing came from; it does not prove that the phone is yours or who used it.
Content of the documents: we keep the document you upload and the signed PDFs for the period in section 8, which depends on the plan, and we do not review their content. It can contain personal data of third parties: we process it on behalf of the person who uploads the document, who is responsible for having the right to use it
Data on the use of the service, only if you accept analytics cookies:
- The pages of the service you visit, clicks on the main buttons, the tools you open or use and the steps of registration and of choosing a plan.
- The date and time of each of those records.
- When you come from another website, only the domain of that website.
- The family of your browser and the type of device (mobile, tablet or computer).
- A fingerprint, that is, a code calculated from the random identifier stored in the visitor analytics cookie (firma_visitante). That identifier does not contain your name, your email or your account, and we do not link it to them. Even so, the law considers that an identifier of this kind can be personal data, which is why we explain it here.
In these records we do not store your IP address, the full description of your browser, your email or your account identifier.
We do not use your data for advertising, we do not sell it and we do not build profiles about you.
3. What we use your data for and on what legal basis
The law requires each use of data to have a legal basis, that is, a reason recognised by law that allows it. These are our uses and the basis of each one:
Creating and managing your account, checking your email with the code and letting you sign in.
Legal basis: it is necessary to perform the contract you accept when you register (article 6(1)(b) of the General Data Protection Regulation, hereinafter GDPR).
Providing the signature service and generating the evidence trail of your documents.
Legal basis: it is necessary to perform the contract (article 6(1)(b) GDPR).
Processing the documents, the data of the people you ask to sign and the evidence trail of each signature, and keeping them for the period that corresponds to your plan.
We do it on behalf of the sender of the document, as a processor (article 28 GDPR). The legal basis must be held by the sender of the document, for example the contract they want to sign with those people or their legitimate interest in the signature being made and proved.
Recording the opening of the document and the technical connection data (IP address, user agent, time zone and language), to provide additional evidence of the act of signing.
Legal basis: the legitimate interest of the sender of the document in being able to prove that the signer had the document in front of them and how it was signed (article 6(1)(f) GDPR). We process it on their behalf, like the rest of the evidence trail.
Allowing the signature to be drawn on the phone, recording which device the drawing came from (IP address, user agent, time zone and language of the phone and the time of each step) and, if you ask for it, sending the phone link to the email address of the signature request.
Legal basis: the legitimate interest of the sender of the document in the signature being possible from a phone too and in being able to prove how it was made (article 6(1)(f) GDPR). We process it on their behalf, like the rest of the evidence trail.
Keeping the stroke dynamics of the signature and the browser location, only if you accept them, to provide additional evidence of the act of signing. We do not use them to identify you, to compare your signature with others or to build a pattern of the way you sign.
Legal basis: your explicit consent, which you give with the checkbox of each one on the signing page or, if you draw on the phone, on the phone page (article 9(2)(a) GDPR for the stroke dynamics and article 6(1)(a) GDPR for the location). The service asks for it on behalf of the sender of the document. It is voluntary: before signing you can choose not to give it or untick the checkbox, and the signature is made all the same. After signing you can withdraw it as explained in section 7. Withdrawing it does not affect the lawfulness of what was processed before (article 7(3) GDPR).
Neither these signals, nor the record of the opening of the document, nor drawing the signature on the phone turn the signature into an advanced or qualified electronic signature. It is still a simple electronic signature under Regulation (EU) No 910/2014 (eIDAS): they are additional evidence of how the signature was made, not a check of who you are.
Keeping the record of your acceptance of the terms, with version and date.
Legal basis: it is part of the contract (article 6(1)(b) GDPR) and allows us to prove which version you accepted (article 6(1)(f) GDPR).
Informing you of changes to the terms or to this policy.
Legal basis: it is necessary to perform the contract (article 6(1)(b) GDPR).
Handling your data protection rights requests.
Legal basis: compliance with a legal obligation (article 6(1)(c) GDPR).
Delivering a document or a notice with acknowledgement of receipt and recording whether the link was opened and whether receipt was confirmed with the code: the date and time, the IP address and the user agent of each moment, the recipient's email address and the texts shown to them with their SHA-256 fingerprint. It does not show that the recipient has read the content or agrees with it.
Legal basis: we do it on behalf of the sender, as processor (article 28 GDPR); the sender must have the legal basis, for example their legitimate interest in being able to prove that they delivered a communication.
Recording the fingerprint seal of a file: we keep the SHA-256 fingerprint calculated in your browser, the date and time, the space that asks for it and the file name if you type it. We do not receive the file and we do not keep your IP address.
Legal basis: providing the service you have contracted (article 6(1)(b) GDPR).
Reminding you before a signed document or an accepted quote ends and sending the renewal to the other person so that they accept or decline it expressly. We keep the other person's name and email address, the end date, the reminder, the answer with its date and time and the texts shown with their SHA-256 fingerprint.
Legal basis: providing the service you have contracted (article 6(1)(b) GDPR). For the other person's data, we act as your processor.
Aggregated usage analytics: knowing which pages and features of the service people find useful, in aggregate figures, to decide what to improve. Only if you accept analytics cookies.
Legal basis: your consent (article 6(1)(a) GDPR), which we ask for with the cookie notice before storing anything in your browser, as required by article 22.2 of Spanish Law 34/2002 on information society services (LSSI). You can withdraw it at any time with the Cookie preferences link, as easily as you gave it. Withdrawing it does not affect the lawfulness of what was recorded before, while you had allowed it (article 7(3) GDPR). The details are in the cookie policy: https://ambarmark.com/firma/cookies
Contact form and quote requests
- Purpose: to answer your question or prepare a quote for you.
- Data: name, email, phone if you give it, company if you state it, and your message.
- Legal basis: handling your request before a possible contract (article 6(1)(b) GDPR).
- How long: 365 days from your last message. If you become a customer, they become customer data.
- The phone number is optional: if you do not give it, we reply by email.
Automatic notifications to other systems (webhooks)
If you set up your account so that the service notifies another system of yours when a document changes status, we keep a log of each notification sent.
- Purpose: so you can check that the notification was sent and resend it if it failed.
- Data: the destination address you configure, the date, the result and the document identifier. The notification does not include the document.
- Legal basis: providing the service you have subscribed to (article 6(1)(b) GDPR). For any signer data the notification may contain, we act as your processor.
- How long: 30 days.
- You are responsible for the system that receives the notification.
Team invitations
If you invite someone to your team, we use their email to send the invitation.
- Purpose: so they can join your team.
- Data: the invited person's email and who invited them.
- Legal basis: the legitimate interest of the team plan holder in organising their work (article 6(1)(f) GDPR). The invited person can ignore the invitation or ask us to delete their email.
- How long: until they accept, until the invitation expires (7 days) or until it is cancelled; then it is deleted.
- Whoever sends the invitation must be entitled to share that email.
Public verification page
Anyone who has a document's code can check at https://ambarmark.com/verificar that the signature evidence is the one we generated.
- What is shown: each signer's name, their email with some characters hidden, and the sending and signing dates. The document is not shown.
- Purpose: so whoever receives the signed document can check it is authentic without asking us.
- Legal basis: for the sender, providing the subscribed service (article 6(1)(b) GDPR); for signers, the legitimate interest of the sender and of whoever receives the document in checking its authenticity (article 6(1)(f) GDPR).
- Who can see it: only someone who has the code, which is in the signed document itself. It cannot be searched by name.
- How long: as long as the signature evidence is kept, within the periods in section 8.
- You can object to your data appearing on this page by writing to aitorcoontigo@gmail.com; we will weigh your case together with that of the sender.
Other uses
If we wanted to use your data for anything else that needs your consent, we would ask for it separately and you could withdraw it whenever you want, as easily as you gave it.
You can object to the uses based on legitimate interest on grounds relating to your particular situation. We explain it in section 7.
4. Whether you have to give us your data
Name, email and password are necessary to create the account. If you do not provide them, we cannot register you. The data of the evidence trail is necessary to sign: without it, the signature could not be proved. The stroke dynamics of the signature and the browser location are voluntary: if you do not accept them they are not collected, and you can sign exactly the same. Drawing the signature on the phone is also voluntary; if you use it, the phone data described in section 2 is necessary to record where the drawing came from.
Data on the use of the service is voluntary. If you do not accept analytics cookies it is not collected, and you can use the whole service exactly the same.
5. Who receives your data
We only share data with those who need it to provide the service:
- Google (Gmail), which sends the emails of the service (verification code, signature requests and notices). It receives your name, your email, the content of the message and, when it is sent to you, the signed document.
- An external timestamping authority, which issues the time stamps. To timestamp the signature we only send it a fingerprint of the document, which contains no personal data: it receives only the document fingerprint (a code calculated from the file), not the document nor your name or email. The request goes out from our server, not from your device.
- Hostinger International Limited (Cyprus, European Union), which hosts the server the service runs on, and Stripe Payments Europe Limited (Ireland), which handles the charges for paid plans and receives your email and the payment details you enter on its page.
Providers that process data on our behalf do so as processors (article 28 GDPR). Stripe, our payment provider, also processes some data as an independent controller to prevent fraud and meet its legal obligations; its policy is on its website. For account data they are processors; for the documents and signer data that we process on behalf of our customers they are sub-processors. This list is the list of sub-processors of annex 2 of the terms and conditions of use. If we add or replace a provider, we update this list and give customers at least 30 days notice.
The additional signals of the act of signing are not sent to any new provider: the location is provided by your browser and we do not query external location services. The sender of the document receives them in the signature evidence report: of the stroke dynamics, only a summary (number of strokes and points, duration, average speed and type of pointer) and the SHA-256 fingerprint of the full data, a code that lets anyone check that it has not changed without showing it. The report also states whether the drawing was made on the computer or on the phone and, in that case, the phone data described in section 2, without stating that the phone belongs to the signer. If you ask for the phone link by email, that email is sent by Google (Gmail), the same provider that sends the signature request, and only to the email address of the request. The phone handoff does not use any other provider: the QR code is generated by the service itself.
The other signers of the same document can see the document title and the name of the person who sent it. The final signed document, which everyone receives, includes for each signer their name, their email, the date and time, the IP address they signed from, the image of their signature if they added one and, if they signed on behalf of an entity, the entity details they declared.
Usage analytics data is not disclosed to anyone. The analysis is done by the service itself, without analytics tools from other companies, and this data is stored on the same server as the rest of the service.
We may also have to give data to judges, courts or other authorities when the law requires it.
6. Transfers of data outside the European Economic Area
Google, which provides the email service, and Stripe, which handles the charges, may process data outside the European Economic Area, in the United States. They do so with the safeguards of Chapter V of the GDPR: the provider's adherence to the EU-U.S. Data Privacy Framework (Commission Implementing Decision (EU) 2023/1795) and, where applicable, the Commission's standard contractual clauses (Decision 2021/914). To ask about these safeguards, write to aitorcoontigo@gmail.com.
Usage analytics does not add any transfer of data outside the European Economic Area, because no new provider is involved.
7. Your rights
You have these rights over your data:
- Access: knowing whether we process your data and obtaining a copy.
- Rectification: correcting data that is wrong or completing it.
- Erasure: asking us to delete your data. There is a limit: we cannot delete the evidence trail while it is necessary to defend or bring legal claims about a signature, within the period in section 8.
- Restriction: asking us to stop using your data for a while, for example while we check whether a piece of data is correct, and only keep it.
- Objection: objecting to our use of your data based on legitimate interest, on grounds relating to your particular situation. We will stop using it unless there are compelling legitimate grounds or it is necessary to defend or bring legal claims.
- Portability: receiving the data you gave us in a format that a computer can read, to take it to another service.
- Not being subject to automated decisions: we do not make any decision about you solely by automated means that has legal effects or similarly affects you, and we do not build profiles.
How to exercise them:
- Write to aitorcoontigo@gmail.com, stating which right you want to exercise.
- You can do it yourself or through a person representing you.
- If we have reasonable doubts that it is you, we may ask you for some additional data to check it.
- It is free of charge.
- We will reply within one month at most from receiving your request. If the request is complex or there are many, the period may be extended by two more months; in that case we will tell you within the first month and give you the reason.
- From your account, in the section called Your data, you can download a copy of your data and delete the account; from your profile you can change your username and your language.
Usage analytics data:
- To withdraw your consent use the Cookie preferences link. From that moment we stop recording and we delete the records linked to your visitor analytics cookie.
- As we do not link these records to your name, your email or your account, we usually cannot know which ones are yours. In that case the law does not require us to ask you for more data only to identify you, and the rights of access, rectification, erasure, restriction and portability do not apply unless you give us information that allows us to find your records (article 11 GDPR), for example the identifier of your visitor analytics cookie.
Additional signals of the act of signing:
- Before signing, to not give consent or to withdraw it, it is enough to leave its checkbox unticked or untick it, on the computer or on the phone.
- After signing, you can withdraw it at any time by writing to the person who sent you the document or to aitorcoontigo@gmail.com, and we will pass it on to them. From then on we stop processing that data and delete it, unless there is another legal basis to keep it. The signature remains valid on the same terms, because it does not depend on these signals.
- The phone and connection data that does not depend on your consent (IP address, user agent, time zone, language and time of each step) is based on legitimate interest. You can object to it as explained by the right to object in this section, by writing to the person who sent you the document or to aitorcoontigo@gmail.com.
If you think we have not handled your data properly, you can lodge a complaint with the Spanish Data Protection Agency (Agencia Española de Protección de Datos), the public authority that supervises compliance with this law in Spain (www.aepd.es). You can also complain to the authority of the European Union country where you live or work. We recommend writing to us first, to try to solve it.
8. How long we keep your data
- Account data: while the account is open. When you ask to close it you have 30 days to download your data, with a reminder by email every 7 days and a final one 3 days before it ends. During that period you can reactivate the account without losing anything. You choose when closing: delete when the period ends (default) or delete once you confirm you have your copy (never before 7 days from the closure). You can ask for immediate deletion at aitorcoontigo@gmail.com (GDPR article 17; we answer within one month at most). The legal basis is performance of the contract (GDPR article 6.1(b)). When that period ends we delete the account data, except what is listed in the following points. Billing data and the record of acceptance of the terms and of this policy are kept blocked for 6 years.
- Single-use links and codes: the activation link stops working after 1 day, the password link after 30 minutes and the signature code after 15 minutes. They are deleted from the system once used or expired, in an automatic cleanup that runs while the service is in use. Accounts that are not activated are deleted after 7 days.
- Document, signed PDFs and evidence trail of each signature: we keep them until 7 days after the last signature, or from the upload if nobody signs it, and never while someone still has to sign. Download your copy. The sender receives by email the final signed PDF and the signature evidence report, and each signer their signed copy. The law sets no minimum period for a non-qualified signature service like this one to keep the documents signed with it (the 15 years of article 9.3.a of Law 6/2020 apply to qualified providers), and the GDPR requires not keeping data longer than necessary (article 5(1)(e)).
- The opening of the document, the technical connection data and, if accepted, the stroke dynamics of the signature and the browser location are part of the evidence trail and are kept and deleted with it, within the same periods of this point. If you withdraw your consent earlier, the stroke dynamics and the location are deleted as explained in section 7.
- The same applies to the phone data when the drawing made on the phone is accepted on the computer. If it is never accepted, because the link expires, because you discard it or because another drawing arrives first, the image, the stroke, the location and the data of that phone do not become part of the evidence trail: they are deleted after the link expires, in the next periodic clean-up of the service.
- Whoever uploaded the document can ask for it to be deleted earlier, and then the personal data in the trail is replaced by the mark [suprimido].
- Charge record of each document sent (account, SHA-256 fingerprint of the PDF and signatures charged, with no names or emails): used to charge only the difference when signers are added and for the free resend. It is deleted when the account is closed and, if the document is deleted earlier, once the validity period of the bonos has passed since it was last used.
- Record of acceptance of the terms: while the account is open and, after it is deleted, 6 years more, blocked.
- Billing data of payments for paid plans: 6 years. Commercial law requires keeping accounting records and their supporting documents for six years from the last entry (article 30 of the Commercial Code); after that they are deleted.
- Rights requests and their answer: 3 years
- Security log of the account (sign-ins, password changes and other actions, with the IP address): 3 years
- Log of the deletions the service makes: 3 years
- Information that EU rules require trust service providers to keep (Article 4.3.b of Commission Implementing Regulation (EU) 2025/2160): the account sign-up data, the verification data of each signer (which email received the code, when it was confirmed and from which IP address) and the changes to the key the service uses to sign the evidence. They are kept in the evidence trail, in the account security log and in the service's key change log, for the periods in this section, and remain kept until those periods end even if the service stops being provided.
- Backups: when we delete a piece of data, it may remain in the service backups for 2 weeks more, until those backups are deleted. Those backups are only used to restore the service if it fails.
- Deliveries with acknowledgement of receipt, with the times, IP addresses, user agents and texts of each moment: 7 days; then they are deleted.
- Fingerprint seals: 7 days; then they are deleted.
- Usage analytics data: 395 days from each record; then it is deleted. If you withdraw your consent earlier, it is deleted at that moment. The visitor analytics cookie lasts 395 days.
When data is no longer used but the law requires us to keep it for a while, we block it: we set it aside so that nobody can see or use it, except judges, courts and authorities, and we delete it when that time ends.
9. How we protect your data
We apply technical and organisational measures appropriate to the risk. Among them:
- We only store passwords as an irreversible fingerprint.
- We check that the email is yours with a single-use link that expires after 1 day, and we check that whoever signs has access to the email address with a single-use code that expires after 15 minutes.
- We calculate a fingerprint of each document and time-stamp it, so that any later change can be detected.
- We keep the stroke dynamics of the signature encrypted.
- The link to draw on the phone works only once, expires soon and we only keep its fingerprint. The computer only accepts the exact drawing it showed you, checking its SHA-256 fingerprint.
- All communication with the service is encrypted (HTTPS), account session cookies only travel over secure connections and we limit the number of attempts to sign in to an account.
If there were a security breach affecting your data, we would act as the law requires, including notifying the authority and, where appropriate, you. If it affects documents we process on behalf of a customer, we notify that customer without undue delay and at the latest 48 hours after becoming aware of it, so that they can meet their own obligations.
10. Minimum age
The service is not intended for people under 18 years of age.
11. Changes to this policy
If we change this policy we will notify you by email and in the service. Each version has a number and a date, shown at the beginning.
Change in this version: it adds the information we keep as a trust service provider, also if the service stops being provided (section 8). The previous version added how long deleted data may remain in backups, clarified the period for the record of acceptance of the terms (section 8) and explained what the time stamp proves (section 3). Before that, we explained the time you have to download your data when you close your account and what is kept afterwards (section 8) and, when the service offers them, deliveries with acknowledgement of receipt, the fingerprint seal and renewals (sections 3 and 8). Earlier versions added the contact form, automatic notifications to other systems, team invitations and the public verification page (section 3), and clarified what each provider receives and Stripe's role (section 5).
Reason for this version: it adds aggregated usage analytics with your consent (sections 2, 3, 4, 5, 6, 7 and 8).