Datapraxis
A cold, empty Estonian state office at three in the afternoon, a closed folder on a ruled desk under high-left window light with a red stop switch on a grey console.

Responsible AI at Datapraxis OÜ

AI help you can audit before you adopt it

We write and consult about practical AI adoption for Estonian teams and public-sector offices. This page describes how we handle data, who approves the output, what we log, and when a question belongs with your own data protection contact instead of with us.

General information, not legal advice. Sector rules and special-category data need qualified Estonian counsel.

  1. 01 Decide what data the pilot may touch
  2. 02 Name who approves the output
  3. 03 Log the decisions and stop when it drifts

Scope

Who runs this page, and what it covers

Operator

The operator of datapraxis.ee is Datapraxis OÜ, Pärnu mnt 22, Kesklinna linnaosa, Tallinn, Harju maakond, 10141, Estonia.

Office hours
Monday to Friday, 9:00 – 18:00 (Tallinn time)

What it does not cover

Third-party tools you test on your own are outside this page. Their terms, retention and training practices are theirs, not ours.

Read each provider's own notice before you paste work into it — particularly for anything naming people, health, or payroll.

Operating rules

Four working rules for a safe pilot

What a pilot must decide before it starts

Four decisions we ask every team to write down in one page, before anyone connects a data source. They are the same four on a customer-service inbox, a contract reading task, or a shift-scheduling draft.

On this page they read as notes. In practice each one takes a meeting and one owner.

  1. 01

    Data minimisation

    Use the smallest set that still tests the question. Drop duplicates, old drafts, and any field the task does not need. For support pilots, exclude identity numbers and health details unless the task truly requires them.

  2. 02

    Human oversight and stop rules

    Name one person who approves external output. Define the uncertain cases that pause for manual handling. If corrections spike, pause the pilot and fix the source material before turning it back on.

  3. 03

    Security habits for small teams

    Limit accounts with export rights. Use separate test folders rather than live customer stores wherever the tools allow it. Note retention periods for logs and drafts, and brief everyone who will press approve on what to check.

  4. 04

    Updates and corrections

    We date every article and correct errors from the source. When a programme or a product changes its stated function, we update the page and note the change. Readers can report an issue by email with the page address and the sentence.

Oversight and stop rules

Someone has to be able to stop the pilot

A hand reaches for a red stop switch on a console beside a closed folder and a printed checklist.

Who approves, and what pauses

For every pilot we name one person inside your team who approves anything that leaves the building. That role is not the AI, and it is not the vendor. Drafts that the approver flags as unclear go into a manual queue; the pilot resumes only after the source material is corrected.

On public-sector workflows the final decision stays with your staff. The AI contribution is noted in the record — what was suggested, what was changed, what was approved — so the file can be reconstructed later without opening a laptop.

The log a pilot leaves behind

  • Drafts — what the tool produced, kept for the pilot period.
  • Corrections — what the reviewer changed and why.
  • Approvals — who signed the output out.
  • Source list — which folders and systems the pilot may reach.

Retention is set per pilot, in writing, before the first run. We keep the log inside your environment where the tools allow it.

An operator watches a monitor with an abstract trend line and a highlighted review point in a dim office at night.

Oversight is a working posture, not a policy paragraph. Someone reads the output at the end of the day, marks what needs a second pair of eyes, and closes the laptop.

Boundaries

Where our notes stop and your adviser starts

Sector rules, employment questions, and special-category data need qualified advice in Estonia. Bring three things to that conversation and it stays short: your pilot scope, your data list, and your oversight plan.

Our pages help you prepare those three items. They do not replace review by your data protection contact or counsel.

Before the pilot starts

Three items to prepare

  1. 01 Pilot scope — one page, plain words.
  2. 02 Data list — every source, and who owns it.
  3. 03 Oversight plan — approver, stop rules, log.

Read the two policies this page sits beside.

Questions

[email protected]

Daily habits

Small habits that carry most of the weight

These are the everyday behaviours behind küberturvalisus in a small Estonian team. None of them need a large tooling budget. Review them at the start of each pilootprojekt and again when it closes.

Limit export rights

Not everyone needs to pull a full table out of the system. The pilot works fine with read-only access for most of the team and one named exporter.

Use test folders

Where the tool allows it, separate the pilot from the customer stores. Copies and duplicates are simpler to delete when they never touched a live folder to begin with.

Note retention

Drafts and logs need a date when they go away. Write the retention period into the pilot brief so nobody has to guess later.

Brief the approvers

Anyone who presses approve should know what to look for. A short list of the three most common fixable mistakes beats a long policy.

Review at open and close

Run through the same short checklist when the pilot starts and when it ends. Habits tend to drift quietly in between; a second pass catches that.

Report back

If you find an error in an article, write to us with the page address and the sentence. We correct from the source and note the change on the page.

We do not use tracking beyond what our cookie notice describes. For details, see the Privacy Policy and Cookie Policy.

Bring us three items and we will read the fourth with you

If a pilot is on your desk and the governance side is still open, send us the scope, the data list and the oversight plan. We will read them the way this page describes — as preparation, not as legal review — and tell you plainly which parts belong with your own adviser.

Talk to Datapraxis OÜ See how pilots work

Datapraxis OÜ · Pärnu mnt 22, Tallinn 10141 · Mon–Fri, 9:00–18:00