DIGITAL PROTECTION GUIDES · OnbrandinG
DNI, passports, NIE and digital certificates: what you can request as a business or professional and what you should protect as an individual.
“Send me a photo of your ID.” “Give me the certificate and password and I’ll submit it.” “Photograph the passport on your phone; people are waiting.” These phrases can resolve a task in seconds while leaving a problem open for years.
Personal and business digital identity comprises documents, accounts, credentials, powers of attorney and evidence. Some elements identify you. Others may allow someone to act on your behalf. Treating them as ordinary attachments can mean losing control over who accesses your data, who signs and who is accountable afterwards.
This OnbrandinG guide offers practical criteria for both sides: the organisation requesting or receiving information and the person deciding what to provide. The aim is to prevent identity verification from becoming excessive data collection, and delegated administration from becoming surrender of the ability to sign.

The rule to remember
As a business, request what you can justify for a specific purpose. As an individual, verify the recipient and protect your authentication and signing secrets. An obligation to identify someone does not automatically mean an obligation to photocopy their document.
Quick navigation: documents and credentials · what a business may request · what individuals should protect · certificates and representation · sectors and examples · urgency and inadequate resources · transparency and public procurement · incident response · operational review · controls and compliance · frequently asked questions.
1. Identification, authentication and signing: three different decisions
Identification establishes who someone is. Authentication checks that the person acting corresponds to that identity. Signing adds an expression of intent linked to a document or action. Possessing a DNI number or receiving its photograph does not, by itself, achieve all three.
A photograph may have been obtained by a third party. An email may come from a compromised account. A visible signature pasted into a PDF may be just an image. And a valid certificate may be used on a device accessible to people who should not have access. Both the information and the verification procedure matter.
| Item | Purpose | What to protect |
|---|---|---|
| DNI and passport | Official identity documents; their use depends on the procedure. | Full image, photograph, signature and additional data. A copy enables information to be combined for fraud. |
| NIE and TIE | The NIE is an identification number for foreign nationals in Spain. The TIE is a physical identity card. The terms are not interchangeable. | Number, card copy and immigration documentation. Request or supply the document appropriate to the situation. |
| Electronic DNI | Alongside the physical document, it enables electronic operations using its certificates and supported systems. | Document, PIN and control of the transaction. A photograph of the DNI does not itself contain its private signing key. |
| Public digital certificate | Links an identity to a public key and enables verification of compatible signatures or authentication. | Identifying data and the context of disclosure. Do not confuse it with a private key. |
| Private key and backup | The private key enables signing or authentication, depending on the certificate and service. | File, password and devices. A .p12 or .pfx export normally includes the private key. |
| Codes, passwords and authorisations | Enable access or approval of specific actions. | PIN, Cl@ve password, one-time codes and signing approvals. Do not dictate them to callers. |
Sources: AEPD: electronic certificates, FNMT: export formats and Ministry of the Interior: NIE.
2. What you can request as a business or professional
The useful question is: what information do I need, for which action and on what justification? Requesting the entire document because a template allows it or because it has always been done does not demonstrate necessity.
Before adding a field or upload option to a form, resolve five issues: purpose, legal basis, essential data, people or entities with access, and retention period or criteria. The GDPR requires minimisation, information for the data subject and security appropriate to the risk; consent does not make excessive collection necessary. GDPR, Articles 5, 6, 13 and 32.
| Situation | As a business or professional | As an individual |
|---|---|---|
| Contract or customer registration | Justify the identification needed. Consider visual verification, signing or another alternative before retaining a full image. | Ask whether showing the document or supplying essential details is sufficient. |
| Invoice | Collect the tax details required for that invoice. This need does not establish that you must archive a photograph of the document. | Distinguish providing tax details from handing over a complete copy. |
| Guest registration | Collect the legally required fields and authenticate them through an appropriate procedure. Registration does not authorise requesting a full DNI or passport copy. | Cooperate with registration; ask for an alternative to a full photograph or scan. |
| Activities subject to anti-money-laundering rules | Apply the specific identification and retention obligations corresponding to your status as an obliged entity. | Check the organisation and channel. Do not remove data needed for legally required identification. |
| Medical records or results | Verify identity and, where a third party acts, their authority to represent the person. Use a channel and level of verification proportionate to the risk. | Provide the relevant proof. Do not give signing keys to someone so they can access services in your place. |
| Administrative or tax procedures | Use the representation mechanisms accepted for the procedure, with the representative’s own credentials and a defined scope. | Authorise the task through the appropriate route; avoid handing over your certificate with its private key. |
| Exercise of data protection rights | Do not routinely require a DNI copy. If there are reasonable doubts, request proportionate additional information. | Ask which uncertainty about identity they need to resolve. |
The AEPD states that a DNI copy is generally unnecessary for contracting or, as a general rule, exercising rights. Specific contexts may require documentation, including certain anti-money-laundering obligations. Avoid both indiscriminate copying and claiming that a copy can never be requested. AEPD: identification using DNI; Law 10/2010, Articles 3 and 25.
Requesting, receiving and storing create different responsibilities
One company may design the request while another receives the document through a booking platform, administrative adviser or outsourced support service. Establish who decides the purposes and means, and who processes data on whose behalf. Not every supplier is automatically a processor: actual functions may make them an independent controller or create joint controllership.
Where a processing arrangement exists, the contract and instructions must govern processing, security measures, subcontracting and return or erasure of information. Outsourcing the tool does not replace oversight by the organisation deciding the processing. GDPR, Articles 24, 26 and 28.
If you receive a copy you did not request: do not automatically add it to the file. Check whether it is necessary, restrict access and apply the appropriate erasure or retention procedure. Explain the correct channel to the sender. If it arrived by mistake or was exposed, also initiate an incident assessment.
3. What you should not routinely hand over as an individual
Do not provide a full copy without checking the recipient, purpose and necessity. Check the domain and use the official channel you already know. A message that knows your booking, name or invoice is not, by itself, proof of legitimacy.
When a copy is justified and the complete document is unnecessary, protect data not needed for that procedure. There is no universal list of fields to redact: data unnecessary for one contract may be required in another procedure. The AEPD recommends avoiding sending the copy by email. AEPD recommendations.
As an additional precaution, you can add a visible mark stating recipient, purpose and date, provided the procedure accepts the copy and the mark does not prevent verification of necessary details. Example: “Copy for [organisation], exclusively for [procedure], [date].” It is a deterrent, can be manipulated and does not prevent impersonation by itself. Nor does it justify collection that should not take place.
Do not upload your documentation to an unknown tool to watermark or blur it. You may be giving the original to another recipient. Use a local tool or trusted environment; check that concealed information cannot be recovered from the final file.
Do not share your private key, DNIe PIN, passwords or approval codes. Being your adviser, employee, relative or supplier does not mean someone needs your secrets. During authorised technical assistance, prevent copying of credentials and retain control over what is signed.
A useful response to a request
“I can prove my identity and provide the necessary details. Please explain the purpose, why you need this copy and the secure channel for this procedure. To act on my behalf, let’s use the appropriate representation mechanism.”
4. Personal and business certificates: delegate without handing over the key
The public certificate and private key are different components. The FNMT distinguishes public export files such as .cer or .crt from .p12 or .pfx copies that include the private key. The extension is a guide, but check the content and export process. Renaming a file does not change what it contains. FNMT: differences between formats.
A copy with a private key, together with its password or another unlocking method, may enable authentication and signing in services that accept it. This does not mean universal access to every bank account or service. Its scope depends on the certificate, authority, system and additional controls.
The FNMT recommends not giving third parties a certificate exported with its private key. A backup restores your ability to use it or transfers it to an environment under your control; it is not a way to authorise someone else to administer matters for you. FNMT: good practice manual.
Not all “business” certificates serve the same function
- Individual: identifies its holder. Using it at work does not make it a shared organisational credential.
- Representative: links a person’s actions to an entity and a type of representation. Check authority and procedural requirements.
- Electronic seal: links the origin and integrity of data to a legal entity. It does not automatically replace a person’s signature when their intent or involvement is required.
- Server certificate: performs technical functions such as authenticating a site. It does not by itself prove that an offer, booking or document request is honest.
The FNMT offers several representative certificate types. Moreover, a signature made with a certificate does not automatically have the legal equivalence of a handwritten signature: this equivalence applies to qualified electronic signatures. FNMT: representative certificates; Council of State: signature and seal effects under eIDAS.
The administrative adviser’s request: “Send it; the deadline is approaching”
Illustrative example. A company must file a return and the director sends their .p12 and password to the adviser. The file ends up in several inboxes, Downloads folders and a backup. Changing the email password neither removes these copies nor revokes the certificate.
The alternative is to check the representation or authorised tax intermediary arrangement accepted by the procedure. At Spain’s Tax Agency, powers of attorney allow an authorised third party to act using their own certificate within the relevant scope. The collaboration framework also has requirements and limits. AEAT: acting on behalf of third parties.
If a deadline is approaching, escalate the incident and examine alternatives accepted by the electronic office. Arranging a power of attorney after surrendering the key does not undo the earlier exposure.
Business custody that establishes who did what
As an OnbrandinG operational proposal, maintain a certificate inventory: holder, entity, purpose, custodian, devices, authorised copies, expiry and revocation route. Use individual accounts, restricted permissions and usage logs. Add approval and separation of duties for sensitive operations.
Consider non-exportable keys, cryptographic devices or signing services with safeguards appropriate to the risk. Properly managed remote signing differs from sending a private-key file to a third party: review the provider, signatory control, transaction authorisation, traceability and applicable conditions.
When employees leave, directors change or an adviser relationship ends, review credentials, powers, devices and certificates. If relevant details or authority change, check with the issuer whether revocation and replacement are required. Do not wait for expiry to investigate possible unauthorised use.
5. Exposed sectors: where errors arise
The following sectors face operational exposure through document volumes, intermediaries, urgency or data sensitivity. This is not a statistical ranking of incidents. All cases below are illustrative examples, not client accounts or accusations against businesses.
Hospitality and tourist accommodation: registration does not mean photocopying
Accommodation providers must collect the data specified for guest registration. The AEPD clarifies that this obligation does not permit requesting a DNI or passport copy to comply with Royal Decree 933/2021. It proposes forms and authentication procedures such as visually checking the document in person or using appropriate online mechanisms. Official AEPD accommodation guidance.
Situation: thirty guests arrive and the receptionist photographs passports on their phone to “fill it in later”. Images may synchronise to personal cloud storage and mix with other photographs.
Better procedure: a form with required fields, planned verification, a corporate terminal and restricted access. If the system fails, activate a contingency procedure with custody and subsequent controlled entry of essential information.
In restaurants, an ordinary table booking should not automatically inherit a hotel’s document workflow. If an exceptional process requires identity or age verification, define the specific necessity and verify it with minimal collection.
Tourism and agencies: the chain of recipients
Situation: an agency receives a passport for a travel procedure and forwards it to a group containing guides, drivers and partners. A specific need becomes widespread disclosure.
Better procedure: identify what each procedure requires—for example, visa processing or passenger details—and who needs to receive it. A driver may need a pickup list without needing a passport image. Separate files, channels and permissions; review international recipients too.
Do not confuse an authority’s or carrier’s requirement with permission for every intermediary to retain the same copy. Verify an emailed request before adding new recipients.
Passenger transport: verify without creating another archive
Situation: a ticket issue prompts staff to request a DNI photograph through an informal chat. The chat ends up containing passenger documents that should not be there.
Better procedure: apply the identification requirements relevant to the service and use the authorised incident channel. Obligations vary by transport type, route and procedure; accommodation-specific rules cannot automatically be applied to all transport.
Freight and logistics: documents that look like authorisation
Situation: someone sends a driver’s DNI and an email containing genuine cargo information. The warehouse takes this as proof of permission to collect the goods. An authentic document may be used by an unauthorised person.
Better procedure: verify collection authority with the carrier’s or customer’s known contact and cross-check relevant operational details. Do not accept a changed driver, registration plate or destination merely because a document is attached. A new phone number supplied in that same message is not independent verification.
If the driver lacks a compatible phone or connectivity fails, a supervised verification alternative must exist. Photographing their document on a personal phone does not resolve the authorisation problem.

Healthcare: incorrect identity can affect care
Healthcare involves more than a document: results, treatments and medical records must be linked correctly. Care has specific legal bases; not all healthcare processing relies on requesting consent. This does not remove information and security obligations. AEPD: healthcare users.
Situation: a caller knows a patient’s name and DNI and requests results. Or someone brings a relative’s document copy to collect a report.
Better procedure: follow the centre’s identity and representation protocol. Knowing a DNI does not itself prove someone is the patient; being a relative does not automatically authorise every access. For sensitive results, use the channels and checks defined for that information.
Another case: an unconscious or undocumented patient arrives at an emergency department. The procedure must enable care and provisional identification, followed by verification and reconciliation under clinical protocols. Requiring a companion to send documents to a personal phone does not resolve this.
Shared accounts, unlocked devices and sending information to the wrong patient can compromise confidentiality, integrity and availability. Response must coordinate IT security, data protection and continuity of care. AEPD: healthcare breaches.
Human resources, banking and other professional services
Human resources: do not automatically move documentation required to formalise employment into the initial selection stage. A fake vacancy may collect documents before an interview; verify the company and channel.
Banking and obliged entities: specific documentation requirements may apply. Customers should be able to identify the real recipient and procedure; the entity must protect the archive and restrict use and access.
Advisers and professional practices: distinguish proving identity, obtaining authorisation and retaining evidence. Requesting client documents does not authorise installing their signing certificate on a shared computer.
6. Urgency, habit and lack of devices: design the alternative beforehand
These failures often arise when operations push staff to improvise. “Don’t use WhatsApp” is insufficient if the company offers no usable alternative.
| Pressure | Risky shortcut | Operational alternative |
|---|---|---|
| Reception queue | Photographing documents to enter details at the end of the shift. | Minimum data in an authorised form and separate verification, with a defined contingency. |
| Administrative deadline | Sharing certificate and password so whoever is available can sign. | Representation arranged in advance, an authorised substitute and incident escalation. |
| Only one computer | Everyone accesses services with the director’s certificate. | Individual accounts, controlled custody and permissions by role. Review necessary resources. |
| Customer without a phone or battery | Installing their certificate on the reception computer. | An in-person or assisted channel accepted for that procedure, retaining control of credentials. |
| No connectivity | Sending documents to another employee’s personal phone. | An authorised offline procedure with custody, reconciliation and removal of auxiliary copies where appropriate. |
| Supplier habit | “Our software requires both sides of the DNI.” | Review legal necessity and adjust the form or supplier. |
| Urgent request from a superior | Signing or releasing cargo without checking an unexpected instruction. | Independent confirmation and a second check for sensitive actions. |
These OnbrandinG proposed controls must be adapted to each organisation’s obligations and resources. Night shifts, substitutes and temporary staff must know the contingency procedure, alongside management.
7. Transparency: publishing a contract does not mean publishing a full DNI
Spain’s Law 19/2013 requires disclosure of specified public contracts, including their subject, amounts and successful bidder’s identity. It also establishes data protection limits. Information enabling scrutiny of public spending is not equivalent to the supplier’s complete private file. Transparency Law, Articles 5, 8 and 15.
Distinguish a legal entity’s registered name and NIF tax identifier from a self-employed individual’s data and a representative’s details. A company winning the contract does not make the signing director’s privacy irrelevant.
Illustrative example: an authority publishes that a professional received an €8,500 contract, its subject and other required information. Instead of preparing a public version, it uploads a case-file PDF containing a full DNI, signature, private address and bank account. The transparency obligation does not automatically justify this additional exposure.
What to publish and what to review before uploading
The AEPD local government guide addresses publication of bidders, minutes and procurement committee members. For individual bidders, it specifies first name, surnames and the last four NIF digits; it also explains that chair and secretary signatures are unnecessary in minutes published for this purpose. This is a criterion for those situations, not a universal formula for every portal. AEPD: local government, procurement section.
The seventh additional provision of Spain’s LOPDGDD also sets rules for publishing administrative acts and notifications by public announcement. It distinguishes situations and does not permit publication of names and surnames together with the full identity document number. Guidance on which four digits to display in administrative acts uses a specific method: it must not be confused with a general instruction always to use the last four digits. LOPDGDD, seventh additional provision; Data protection authorities’ guidance.
A harder-to-see failure: the DNI is concealed on the PDF page but remains in extractable text, comments, annexes or certificate data embedded in the electronic signature. A superimposed black rectangle does not guarantee actual removal.
The operational recommendation is to retain the signed original in the file under the appropriate access rules and create a suitable public version. Review text, layers, metadata, attachments and signature data. If authenticity must be established, design a mechanism compatible with data protection; also check what a verification link or code can retrieve. Do not alter the evidential original to resolve public disclosure.
As a supplier, review the documentation you provide and what is published about you. If you find excessive exposure, preserve the reference and request assessment and correction from the responsible authority or its data protection officer. Removing unnecessary data does not mean hiding legally required contractual information.
8. Incident patterns in these processes and what complicates the response
Without assigning statistical frequencies, these are patterns to include in risk analysis:
- Wrong recipient: a DNI copy or clinical result goes to another person. Recalling the message does not prove that nobody opened or downloaded it.
- Exposed folder: customer attachments are accessible through a widely shared link or incorrect permissions.
- Fake booking or employment form: apparently legitimate requests collect documents for reuse.
- Compromised email: an attacker exploits genuine conversations to request documents, change instructions or demand payments.
- Lost personal phone: customer documents remain in the gallery, chats and synchronised backups.
- Copied certificate: a private key remains with third parties after the professional relationship ends.
- Hard-to-attribute signature: several people use the same credential and insufficient logs prevent reconstruction of the action.
- Mixed healthcare identities: clinical information is linked to the wrong patient, affecting care and later correction.
- Replicated public document: a PDF with excessive data has already been indexed, downloaded or copied outside the original portal.
The most problematic combination involves authentic documentation, account access and signing capability. The attacker has convincing context; the organisation must reconstruct what they could consult, change or submit and what evidence remains available.

9. If you have already sent a document or shared a certificate
For the affected individual
- Identify what was shared. A DNI number, image, public certificate and copy containing a private key and password are different things.
- Preserve evidence. Keep messages, recipients, dates and procedural references; do not redistribute sensitive documents when requesting help.
- If the private key may be compromised, contact the issuer immediately. Request revocation through its procedure and check the status. Deleting the file from your computer neither revokes the certificate nor removes other people’s copies.
- Review access and actions. Check relevant services and alert the affected organisation if you detect unauthorised procedures or contracts.
- Report fraud, threats or misuse to the authorities. Use official channels and notify the organisations involved. Avoid solutions offered by an unverified contact.
Revocation prevents future use in systems that correctly check status; it does not erase earlier actions or automatically invalidate all previous signatures. A dispute requires examination of evidence and circumstances. The FNMT provides for revocation where loss of confidentiality or unauthorised use is suspected. FNMT: individual certificate revocation.
If only a document copy was exposed, do not conclude that someone can electronically sign with it. Assess impersonation risk and contact the receiving organisation. Physically renewing the DNI is not an automatic solution to circulation of its data.
For the business requesting, receiving or retaining information
- Contain the exposure. Restrict the compromised link, access or account; activate the incident channel and preserve relevant logs.
- Determine the scope. Which documents, keys and people are involved, where copies exist, who could access them and what actions occurred.
- Coordinate revocation and recovery. Involve the holder, issuer, security team and process owners. Avoid destroying evidence during cleanup.
- Assess the personal data breach. Document facts, risks and measures. The processor informs the controller without undue delay.
- Notify where required. The controller notifies the competent authority without undue delay and, where feasible, within 72 hours of awareness, unless risk to rights and freedoms is unlikely. Late notification must be justified. Where high risk is likely, also inform affected people without undue delay, taking legal exceptions into account.
- Restore the process. Review the instructions, devices, permissions, supplier and training that enabled the failure.
The 72-hour period is not permission to wait or the general deadline for informing individuals. An initial notification may need to contain partial information, supplemented later. Sources: AEPD: breach management and notification and AEPD: informing affected people.
10. Managing a reputational crisis also means protecting people
Customers need to know what happened, what information of theirs was affected and what they can do. Generic reassurance does not replace those details. Avoid claiming everything is under control before evidence supports it, and provide a verifiable contact.
Separate confirmed facts, scope still under investigation and measures taken. Explain specific risks without disclosing other affected people’s information. Give useful instructions and state that the organisation will not request private keys or passwords to “protect” customers.
Response requires coordination of continuity, technical analysis, data protection and communication. Recovery is demonstrated by correcting the procedure that created the risk and supporting people, as well as restoring the system.
11. What your organisation can review this week
These questions start an operational review without waiting for an incident:
- Which forms request both sides of the DNI or the full passport, and what justifies each request?
- Where do files end up: applications, email, chats, Downloads, phones and backups?
- What data does each department and intermediary actually need?
- Are individual or representative certificates installed on shared devices?
- Who retains private keys, and what happens when advisers, directors or employees change?
- Are powers of attorney, substitutes and necessary resources ready before deadlines?
- What alternative exists if the system fails or someone has no mobile phone?
- Are authorisation and origin checked before releasing goods or clinical information?
- Is a public version of each file reviewed, including annexes and signature data?
- Do staff know whom to alert if they send documents to the wrong recipient?
12. If your business still has no controls: where to start
A privacy notice and a folder of contracts do not by themselves demonstrate appropriate processing. Compliance must show in what happens at reception, administration, the warehouse and customer support. Buying software is also insufficient if personal phones still hold copies and signatures remain shared.
Start by assigning tasks and verifiable evidence. This matrix is an organisational proposal, not a compliance certification or exhaustive list of obligations:
| Task | Coordinator | Useful evidence |
|---|---|---|
| Review requested documentation | Process owner with legal or data protection advice | Purpose, basis and necessary fields per procedure; corrected forms. |
| Control receipt and storage | Operations and IT security | Approved channel, copy map, individual permissions and access reviews. |
| Manage certificates and representation | Management, administration and IT security | Inventory, custodians, powers, expiry dates and departure and revocation procedures. |
| Review suppliers | Procurement and data controller | Defined roles, applicable contracts, security safeguards and return or deletion. |
| Publish case files | Publication unit with privacy review | Reviewed public version and original retained under appropriate access controls. |
| Respond to incidents | Designated owner and technical, legal and communications team | Record of facts, risk assessment, decisions and communications where required. |
Where a data protection officer exists, involve them according to their functions; they do not replace management’s or the controller’s responsibility. Check whether your activity requires appointment. Healthcare centres obliged to maintain medical records have a specific provision in Spain’s LOPDGDD, except professionals practising individually. LOPDGDD, Article 34.
Suggested initial plan: first, locate existing copies and credentials and contain excessive access without destroying necessary evidence. Next, review requests and alternatives, assign owners and define retention and contingencies. Finally, rehearse a wrong-recipient or lost-device case and verify staff know what to do. A month’s work can organise priorities; it does not guarantee resolution of every obligation.
13. Frequently asked questions about DNI, passports and digital certificates
Can a company request a copy of my DNI?
A justified need or specific obligation may exist, but copies should not be routinely requested for every contract. The company must assess purpose, legal basis and proportionality. Showing the document or another verification method may suffice. AEPD criteria.
Can a hotel photocopy my DNI or passport?
The AEPD states that requesting a copy to comply with guest registration violates data minimisation. Accommodation must collect required details and verify identity appropriately, without using registration to justify a full copy. AEPD guidance.
What should I redact on a DNI copy?
Data unnecessary for the specific procedure, where a complete copy is not essential. Do not conceal a required field without checking. Confirm necessity with the recipient and ensure redaction is effective in the final file.
Is sending a DNI through WhatsApp or email safe?
An application’s name offers no guarantee. Recipient, devices, downloads, forwarding and copies matter. The AEPD advises avoiding emailing the copy. Request an official channel with controlled access; a web form can also be poorly protected.
Does a watermark prevent identity theft?
No. It may discourage casual reuse and record the intended recipient, but can be manipulated. It does not replace checking the recipient, minimising data and limiting retention.
Can someone sign using a photograph of my DNI?
The photo does not by itself provide the private key of your DNIe or digital certificate. It may contribute to identity fraud if combined with other information or insufficient verification. Sharing keys or codes changes the risk.
Should I give my digital certificate to my administrative adviser?
Do not surrender your private key or password so another person can sign as you. Review the accepted power of attorney or representation mechanism. The AEAT permits certain third-party procedures using the representative’s own certificate and the corresponding authorisation. AEAT: representation.
Can I use the director’s certificate with their permission?
Internal permission does not by itself resolve custody conditions or signing traceability. Use authority and credentials appropriate to the person acting. A business must distinguish who prepared, approved and signed.
Does changing the password remove copies of my certificate?
No. A previously exported copy may retain its earlier password. If you suspect disclosure of the private key, contact the issuer for revocation and review previous use; changing other account passwords does not revoke the certificate.
Can healthcare staff request identification?
They may need to verify the patient or person requesting information. This does not automatically justify retaining a full copy for every procedure. Protocols must protect care, identity and confidentiality, with emergency contingencies.
How long can a company retain a copy?
There is no single period for all cases. It depends on purpose, sector obligations and required retention. Establish a period or criteria and apply erasure or blocking where appropriate; do not keep it indefinitely accessible “just in case”.
Does transparency law require publication of my DNI as a supplier?
It requires publication of certain contractual information, not automatically a complete DNI copy. Consider the situation and data protection limits. Partial identification criteria do not apply identically to every publication. Law 19/2013.
What if my company has never applied these controls?
Inventory requests, documents, copies and certificates; assign an owner for each process; justify necessary collection; restrict access and prepare channels and contingencies. Obtain specialist support to review your sector’s obligations and any exposure already detected.
Must every DNI-related error be reported to the AEPD?
Not automatically. Document and assess the breach. Authority notification depends on risk to individuals, and communication to affected people on likely high risk, subject to the corresponding legal exceptions. Do not confuse the two duties.
Prevention · Response · Recovery
At OnbrandinG, we address digital identity protection alongside privacy, security and reputation. An improperly requested document, poorly safeguarded key or excessive publication needs a response adapted to its context and the people affected.
Explore our digital protection capabilities and review with your team how you request, receive, verify and retain documentation.
OnbrandinG guide for businesses, professionals and individuals. Primary scope: Spain and the European Union. Official sources consulted on 5 October 2026. Examples are fictional and operational proposals must be adapted to the procedure and applicable sector obligations.