Skip to content
Product
Overview→ Workflows→ Studio workspace→ AI and review→ Integrations→
Features Security Request a demo Sign in
ClaimEvidence/Security & compliance/Data protection impact assessment summary

Compliance document

Data protection impact assessment summary

Structured assessment of necessity, proportionality, risks and mitigations.

Document edition Edition dated 30 August 2026 · effective from 2026-08-30CLE-PUB-16-ENThe Italian version is the controlling legal text.
Download PDF

SHA-256 ec12c42970fba2bcd1dc6e8d59465dec566286ddf4a7848619188ac482298230

Document contents
  1. Preamble, nature and effect of this document
  2. Personal and material scope
  3. Definitions and interpretation
  4. Specific duties and safeguards
  5. Scope and roles
  6. Data, purposes and bases
  7. Risks and measures
  8. Outcome and consultation
  9. Scope, audience and status of this document
  10. Exceptions, non-conformity and escalation
  11. Review, change and improvement
  12. Nature of the summary and ownership of the decision
  13. Risk factors to examine
  14. Allocation of responsibility and reliance limitations
  15. Evidence, review, requests and governing law
  16. Official references
Download PDF

Preamble, nature and effect of this document

Nil Tech Europe S.r.l., with registered office at Via Calmaggiore 5, 31100 Treviso (TV), Italia, VAT No. IT 05614380268 (“Niltech”), adopts this document in order to summarise description, necessity, proportionality, risks to people, measures, residual risk and the controlled DPIA decision.

This document is a corporate transparency and accountability record. It is not a third-party certification, legal opinion addressed to persons other than the company, absolute security warranty or blanket compliance statement; contractual commitments arise solely from the applicable agreements.

This summary reflects the method required by Article 35 GDPR and Guidelines WP248 rev.01. The full assessment remains a controlled accountability record; where high risk cannot be mitigated, processing may not commence without the determinations required by Article 36 GDPR.

Personal and material scope

The objective scope includes ClaimEvidence, its public interfaces and processing strictly connected with the described functions. The corporate website and document library are published on claimevidence.tech; the application service is available through the separate app.claimevidence.tech domain. Hostinger provides infrastructure and, according to the applicable configuration, mail transport. MySQL/MariaDB is software running in the controlled environment and not a separate subprocessor unless a distinct managed service is used. OpenAI provides API services only for enabled functions; any separate email provider must be identified and assessed before use.

The relevant operations concern guided photo and document collection, case organisation, completeness checks, configurable analytical support, human review and export. Potential information categories are: demo and security-pack requests on the site; in the application, case identifiers, authorised contacts, photographs, documents, notes, session metadata and assisted outputs. The actual privacy role, lawful basis and extent of processing depend on the contractual relationship and the lawful instructions of the party determining purposes and essential means.

Definitions and interpretation

  • “Service” means the ClaimEvidence functions made available under the agreement.
  • “Customer” means the legal person or professional entering into the agreement with Niltech.
  • “Authorised User” means an individual enabled by the Customer to use the Service under its responsibility.
  • “Customer Data” means data, documents, images, instructions and other content submitted or generated on the Customer’s behalf.
  • “Assisted Output” means a result produced through automated rules or artificial-intelligence components and subject to the stated controls.
  • “Further Supplier” means a third party providing Niltech with a technical service relevant to the documented scope.
  • “Incident” means an event compromising or capable of compromising confidentiality, integrity, availability, authenticity or resilience.
  • “Business Day” means a day other than Saturday, Sunday or an Italian national public holiday.

Specific duties and safeguards

1. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall map purposes, roles, subjects, data, sources, recipients and flows. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

2. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall document lawful bases, transparency, minimisation, quality and rights. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

3. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall consider special data, vulnerability, scale, monitoring and new technologies. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

4. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall assess access, exclusion, error, bias and loss-of-control risks. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

5. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall link measures to evidence and assess effectiveness. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

6. Within its assigned role and without prejudice to the Customer’s responsibilities, Niltech shall stop or consult where unmitigable high risk remains. The applicable file identifies the owner, scope, dependencies, acceptance criterion and evidence; absent those elements, the safeguard is not treated as demonstrated.

Scope and roles

The corporate website and document library are published on claimevidence.tech; the application service is available through the separate app.claimevidence.tech domain. Hostinger provides infrastructure and, according to the applicable configuration, mail transport. MySQL/MariaDB is software running in the controlled environment and not a separate subprocessor unless a distinct managed service is used. OpenAI provides API services only for enabled functions; any separate email provider must be identified and assessed before use.

The customer is normally controller for operational data; Niltech processor. Niltech is controller for its own administrative and security data.

Data, purposes and bases

demo and security-pack requests on the site; in the application, case identifiers, authorised contacts, photographs, documents, notes, session metadata and assisted outputs

Purposes: guided photo and document collection, case organisation, completeness checks, configurable analytical support, human review and export.

Bases and necessity must be confirmed by the controller for the specific use; special-category data requires an additional condition.

Risks and measures

Risks: improper access, disclosure, excessive retention, wrong output, loss of control, transfer and supplier dependency. Measures: minimisation, access, logging, contracts, human review, incident handling, retention and supplier review.

Outcome and consultation

The full DPIA is in the controlled pack. Residual risk must be accepted by the competent owner; if it remains high without adequate mitigation, use does not proceed and authority consultation is considered.

Scope, audience and status of this document

This document is intended for customers, prospects, authorised users, advisers and control functions needing to understand the ClaimEvidence scope. Its specific objective is to summarise description, necessity, proportionality, risks to people, measures, residual risk and the controlled DPIA decision. It applies to the stated document revision and date and must be read with the applicable agreement, order, DPA, technical specifications and controlled procedures.

The corporate website and document library are published on claimevidence.tech; the application service is available through the separate app.claimevidence.tech domain. Hostinger provides infrastructure and, according to the applicable configuration, mail transport. MySQL/MariaDB is software running in the controlled environment and not a separate subprocessor unless a distinct managed service is used. OpenAI provides API services only for enabled functions; any separate email provider must be identified and assessed before use.

Executed agreements and actually approved configurations prevail in case of inconsistency. Public information describes the control programme; it does not turn optional provider capabilities into Niltech controls or automatically attest legal applicability or satisfaction.

Exceptions, non-conformity and escalation

A deviation is not accepted by custom. The owner records the affected requirement, cause, impact, exposed data and persons, compensating measures, approver, expiry and closure criterion. The exception is reviewed if risk changes or a measure does not work as expected.

Incidents, possible unlawful processing, loss of data control, outputs with severe impact, contractual breaches, unapproved suppliers or unreliable evidence must be escalated without delay. Current Legal and functional scope: Payment services are outside the scope described by this documentation.

  • contain risk and suspend the affected phase where needed
  • preserve evidence, timing, decisions and communications
  • involve privacy, security, product, legal or management owners as appropriate
  • resume only after measure verification and documented authorisation

Review, change and improvement

The document is reviewed at least every six months and earlier when purpose, audience, data, GDPR or AI Act role, supplier, model, architecture, location, contractual terms or legal requirements change. Incidents, complaints, failed tests and new vulnerabilities trigger an extraordinary review.

Each review records inputs, participants, decision, changes, superseded evidence, remaining gaps and next date. Material corrections are published without retroactively altering the prior document revision. Contact and requests: info@nil-tech.net.

  • check change register and related documents
  • retest affected controls
  • update manifest, PDF, HTML and hashes
  • notify recipients where the change affects their rights or duties

Nature of the summary and ownership of the decision

This summary describes the method and areas requiring assessment; it does not prove that a complete DPIA has been concluded for every Customer or configuration. The controller is responsible for determining whether processing is likely to result in high risk and, if so, completing the assessment before processing. Niltech provides information reasonably available to it as processor.

A DPIA must describe operations, purposes and any legitimate interest; assess necessity and proportionality; consider risks to rights and freedoms and their sources; define measures, safeguards and demonstration mechanisms; seek data-subject views where appropriate; record the DPO’s advice if one is appointed and the controller’s decision.

Risk factors to examine

Case photographs, documents and metadata may reveal faces, vehicle-registration numbers, locations, health conditions, minors or persons unrelated to the case. The Customer must establish collection instructions that avoid excessive capture, redact unnecessary elements where reasonably possible and document any applicable Article 9 and 10 GDPR conditions.

Volume and duration, monitoring, vulnerable individuals, source combination, transfers, supplier access, ability to challenge, AI error, professional reliance, security, deletion and material consequences are also considered. Necessity and proportionality are assessed against less intrusive alternatives.

Where high risk remains after measures and the controller cannot reduce it, processing does not begin before consulting the authority under Article 36 GDPR. Review is mandatory when risk, purpose, model, supplier, flow or law changes.

Allocation of responsibility and reliance limitations

Within its sphere of responsibility, the Customer warrants the lawfulness of submitted data and instructions, user authorisation, suitable lawful bases and notices, and professional verification of outputs. Niltech remains responsible for activities directly under its control and does not assume the Customer’s regulatory, professional or decision-making functions.

Outputs from ClaimEvidence are auxiliary. Unless expressly agreed and subject to mandatory law, they are not legal advice, an expert determination, insurance decision, liability finding, credit assessment or other reserved professional act. The recipient must examine sources, completeness, consistency and consequences before use.

Nothing excludes liability that cannot lawfully be excluded. Outside those cases, attribution, remedies, limitations and quantification principles follow the applicable agreement, taking account of contributory conduct, mitigation duties and foreseeability under the governing law.

Evidence, review, requests and governing law

Every material assertion must be traceable to a contract, approved configuration, register, minutes, test, log or other reliable evidence. Supplier statements and Niltech controls are kept distinct. Absence of incidents is not, by itself, proof that a measure is effective.

Revisions are dated, reasoned and approved. A later revision does not retroactively alter facts or commitments applicable to earlier periods. Published copies are identified by code, date and cryptographic digest; those elements evidence copy integrity, not the substantive effectiveness of described controls.

Reports, clarification requests, rights requests and complaints may be sent to info@nil-tech.net. Niltech verifies identity and authority where necessary, records the request, responds within applicable periods and communicates any reasoned extension or refusal.

Unless mandatory law or a written agreement provides otherwise, Italian law governs interpretation. The Italian text is controlling; the English translation is provided for convenience.

Official references

  • Regulation (EU) 2016/679 (GDPR)
  • Guidelines WP248 rev.01 on data protection impact assessment
  • Italian Data Protection Authority — Data protection impact assessment

Questions or rights requests

Contact Nil Tech Europe S.r.l. for privacy, security, contractual, or accessibility matters.

info@nil-tech.net

Guided collection, assistive AI and professional review for property claims.

Product

Overview Workflows Studio workspace AI and review Integrations Features Sign in

Trust

Security Website and contact-form privacy notice Legal notice and company information

Company

Nil Tech Europe S.r.l.

Via Calmaggiore 5, 31100 Treviso (TV), Italia

IT 05614380268

info@nil-tech.net

© 2026 Nil Tech Europe S.r.l.

The Italian version is the controlling legal text.