Dmytro Bondarets · Tallinn, Estonia
General information for readers, not legal advice
Notes on using AI tools with care
This page explains thoughtful use of the AI apps listed on this site. It covers four habits worth keeping: checking a source before you rely on it, deciding what never goes into a prompt, reading how a tool handles what it holds, and knowing where a person has to stay in the loop.
Questions about how this site handles a message you send go to [email protected].
Check sources before you share
A confident sentence is not a checked one. The confidence lives in the phrasing; the fact lives somewhere else.
Open the cited page. Follow the link the assistant gave you and read the source itself. A citation that does not exist, or that does not say what the answer claims it says, is the failure that costs the most time later.
Confirm dates and names. A tool can attach last year's figure to this year's question. Check the publication date, the version, and the spelling of every name before any of it goes into your document.
Keep quotes tied to their source. When you copy a sentence, copy where it came from in the same step. Rebuilding that trail a week later takes longer than saving it now.
Find a second source for numbers. For study work or a client deliverable, one figure from one place is still a draft. Two independent sources, or a note saying where the figure came from, is what makes it usable.
Do not publish AI output as fact without this step, and say where a figure came from when you pass it on to someone else.
Mind what you paste
A prompt box is a place where text leaves your machine. Once a sentence is sent it sits with the tool's account, its logs and its retention rules — not with you, and not on your terms. The moment to decide is before the paste, not after the answer.
Never goes into a public tool
- Passwords and access codes. A shared login pasted into a chat is a credential you can no longer control, and no answer is worth that trade.
- Client personal data. Names, addresses, case details and contact lists stay out. If the task needs the situation, describe it without identifying anyone.
- Medical details. Your own or someone else's. Health information carries tighter handling rules than a general draft, and a general chat tool is not built for it.
- Unpublished business terms. Prices, contract clauses and quotes still under negotiation are not public information yet, and a summary of them is still them.
Where a draft genuinely needs the detail, prefer a work account that states its retention settings, anonymise the input, or summarise it by hand first. Small teams do best with one written sentence about what never goes into a prompt — agreed once, and short enough to repeat.
Understand tool-side handling
Each app sets its own rules on what it stores, whether your inputs may be used to train a model, and how long a conversation stays retrievable. Two tools that look identical on screen can behave differently here, and the difference usually sits in a settings page rather than in the chat.
- Retention
- How long a conversation is kept, and whether you can delete a single item or only a whole account. If the answer is not in the settings, ask support before you put sensitive work in it.
- Training use
- Whether your inputs may be used to improve the model. Some plans offer a switch for this; others set the policy at account level and do not expose it at all.
- Workspace access
- Who inside a shared workspace can open, search or export what you wrote. A private chat inside a shared workspace is not always private to that workspace.
Enterprise tools your workplace runs, such as Workday, carry separate administrator controls. The person who manages that account decides what is switched on, so ask them rather than assuming your own experience of the same name applies at work.
Keep a short record of which tools hold which data. One line per tool is enough: the name, the kind of material that goes in, and who on the team can open it.
Working on paper first is one way to strip identifying details out before anything reaches a tool.
Verification for study and hiring
Coursework and hiring decisions carry consequences for the person on the other end of them. A tool can organise the material and produce a first draft; it cannot carry the responsibility. That keeps a person as the final step.
For coursework
- Verify every citation in an essay before it is submitted: open the source, check the page, confirm the author and the year.
- Treat a generated summary as a first pass on the reading, not as a substitute for doing the reading.
- Check that the answer addresses the question that was actually set, not a nearby one the tool found easier to answer.
For hiring
- Confirm CV facts before shortlisting: the dates, the employers, and the specific work that is claimed.
- Use a tool to organise applications, not to rank people on a summary it wrote about them.
- Keep human review as the final step, and be able to say who made the decision and why.
AI can organise and draft. Responsibility for the decision stays with you.
Retention on this site
This informational site does not run accounts and does not store reader files. There is no login, no dashboard and no history of which pages you read here.
If you email a question, the message is used to reply to you and to improve the guidance on these pages. You may ask for deletion of your message by writing to the contact address below.
For tool-specific retention — what an assistant, a research app or a coding tool keeps — consult that tool's own documentation. This page can describe how this site works; it cannot speak for another company's settings.
- Kept
- Your message, the reply, and the date it arrived.
- Not kept
- Accounts, uploaded files, or a record of your visit.
- Deletion
- Available on request, from the address you wrote from.
Rights and contact
You may request information about messages you sent here and ask for correction or deletion. Write from the same address you used and the message can be found without guesswork.
Contact details
Phone
Address
Ümera tn 2-152, Lasnamäe linnaosa, Tallinn, Harju maakond, 13817, Estonia
What to include
Write from the same address you used so the message can be found. Include the date you sent it and the subject line you used.
For a correction, quote the sentence you want changed and say what it should say instead. For a deletion request, the date is usually enough on its own.
Replies
Replies come from Tallinn on working days, Monday to Friday, 9:00–18:00.
A question about a tool's own retention or training settings usually gets an answer that points you to that tool's documentation, since the setting lives in your account and not in this one.