Edific

POLICIES

Privacy policy

Last updated  -Mar 19, 2026

This Privacy Policy explains how Edific ("we", "us", or "our") collects, uses, and protects your information when you use our website, services, and systems (the "Service").

By using the Service, you agree to the collection and use of information in accordance with this policy.

1. Information We Collect

We collect only what is necessary to operate and improve our systems.

1.1 Information You Provide

  • Name, email address, and contact details
  • Business information shared during onboarding
  • Inputs, data, and content you provide to our systems

1.2 Automatically Collected

  • Device and browser information
  • Usage data (pages visited, actions taken)
  • Log data and performance metrics

1.3 Third-Party Sources

We may receive data from tools and platforms you connect (e.g. APIs, integrations, analytics tools).

2. How We Use Your Information

We use your data to:

  • Deliver and operate AI systems and workflows
  • Improve system performance and reliability
  • Communicate updates, support, and service information
  • Monitor usage and prevent abuse
  • Develop new features and capabilities

We do not sell your personal data.

3. Data Usage in AI Systems

  • Your inputs may be processed by AI models to generate outputs
  • Data is used only to deliver requested functionality
  • We do not use your data to train public or shared models without explicit consent

You are responsible for ensuring that any data you provide complies with applicable laws.

4. Data Sharing

We do not share your data except when necessary:

  • With trusted service providers (hosting, infrastructure, analytics)
  • To comply with legal obligations
  • To protect the security and integrity of our systems

All third parties are required to handle data securely.

5. Data Retention

We retain data only as long as necessary to:

  • Provide the Service
  • Meet legal and operational requirements
  • Improve system performance

You may request deletion of your data at any time.

6. Security

We implement appropriate technical and operational measures to protect your data, including:

  • Secure infrastructure
  • Access controls
  • Data encryption where applicable

No system is completely secure, but we take reasonable steps to protect your information.

7. Your Rights

Depending on your location, you may have the right to:

  • Access the data we hold about you
  • Request corrections or updates
  • Request deletion of your data
  • Object to certain processing activities

To make a request, contact us using the details below.

8. Cookies and Tracking

We use cookies and similar technologies to:

  • Understand how users interact with the Service
  • Improve performance and usability

You can control cookies through your browser settings.

9. Third-Party Services

Our Service may integrate with third-party tools. We are not responsible for their privacy practices. You should review their policies separately.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Continued use of the Service after updates constitutes acceptance.

11. Contact

For any privacy-related questions or requests:

Email: hello@edific.uk
Address: Lisbon, Portugal

Acknowledgement

By using Edific, you acknowledge that you have read and understood this Privacy Policy.

Questions worth asking

Asked before, answered plainly

The questions worth asking before you send us a document. Can’t find your answer here?

Nowhere. Edific runs on your own server or VPS; it is never sent to us or a third party. That is a design decision, not a setting you can turn off.

Edific. A named point of contact owns your engagement end to end — the same person you talk to signs the DPA and stands behind the result. Less brand, more accountability.

On our published test — 3 hard receipts, ~15% for standard OCR — Edific got 18 of 18 fields correct. Small, deliberately hard sample, presented as exactly that. The number that matters is the one from a pilot on your own documents.

Its job is to be wrong loudly. The evaluation gate flags uncertain fields for human review before export, and any slip is traceable in the audit log and fixed at the source.

Scoped per engagement, not per seat — it follows volume, document types, and infrastructure. You get a fixed quote after a pilot. No pilot, no quote.

Yes, structurally. Processing happens on your own infrastructure, and the Art. 28 DPA describes the architecture as it actually works.

Next step

See it on your own documents

Not a deck. Not a demo dataset. Send a batch of your real documents — the difficult ones — and get back verified, structured data with every field scored and logged. Then decide.

Runs on your infrastructure. Covered by a DPA. Edific accountable for the result.