You decide what it learns. You can see and delete what it kept.
Four answers first, then every control and every commitment, each with what stands behind it and whether it is live today.
- Who sees it?
- You, and the engineer who builds it under a written agreement. Nobody else. People in your record become role types before storage, so even the store holds no names.
- Does it train models?
- No. Your record is never used to train general AI models, ours or anyone else's. Model calls go through API terms that exclude training, and we re-verify those terms on a schedule.
- Can I leave with it?
- Yes. Export everything, with its source citations, in open formats, any time. Delete one node, one source, or everything, and it is gone from your engram at once and from backups within thirty days.
- What if you close?
- At least ninety days' notice and a full export. Two personal-AI products closed in 2025 with export windows of fourteen days and one month. We wrote ours down before taking a customer.
Your controls.
See every node
Each one with its source, its dates, and what superseded it.
Delete
A node, a source, or everything. The next answer stops citing it.
Pause
Everything, in one tap. Disconnect any source. Take over any thread, and the helper stops drafting there.
Export
All of it, with the citations, in JSON and Markdown.
Approve
Nothing goes out, gets paid or gets promised without your OK, unless you set a rule inside a limit you set. An approval lifts a hold, never a limit.
Revoke
Any colleague's access, where you granted some. Queued sends wait in a delay you can stop.
A sample engram, on a fictional person. Tap a node. Delete one.
A rule Sam statedA decision Sam madeA preference Sam showedHow Sam handles a situationHow Sam says things
What we commit to, and what stands behind it.
Each one is marked live where it is true today, and planned where the product makes it true before launch. Nothing here is a promise we have not written down.
- planned
AI disclosure on every outbound message
Every message your helper sends says it was drafted by your AI, and carries a machine-readable tag.
Because: The EU AI Act's transparency duty, in force since 2 August 2026, and the plain decency of telling people.
- planned
Approval by default
Nothing goes out, gets paid or gets promised without your OK, unless you set a rule that allows it, inside limits you set. No standing rules for money or commitments at launch.
Because: Traide's method: people hold the irreversible, and an approval lifts a hold, never a limit.
- planned
Export
Take your engram and its source citations with you, any time, in open formats.
Because: The export windows the closed products gave their users were fourteen days and one month.
- planned
Deletion
Delete one memory, one source or everything. Deleted means gone from your engram at once, and from backups within thirty days.
Because: Your right to erasure, and the thirty-day backup window we chose to state.
- planned
No training of general models
Your record is never used to train general AI models, ours or anyone else's.
Because: Model calls only through API terms that exclude training, re-verified on a schedule.
- planned
People in your record
Before anything is stored, the people in your record become roles, like "a buyer at a restaurant group". We keep no message bodies. If you appear in someone's record and want your mentions removed, write to us.
Because: Redaction at ingestion is how the pipeline is built; a request path is how a third party uses it.
- live
Nothing ambient
It learns only from sources you connect and corrections you make. No microphone. No screen capture.
Because: Passive capture is what people reject, and rightly.
- live
Text only
Duplikate writes. It does not clone voices or faces.
Because: Voice and likeness law is moving fast, and a text-only helper needs none of it.
- planned
If we are sold or close
You get at least ninety days' notice and a full export.
Because: A written wind-down plan, before the first customer.
- live
Only true security claims
We publish what is true today, and no badge before an audit. Report a vulnerability to the address below with "security" in the subject.
Because: A badge earned later is worth more than one claimed now.
- planned
Consent for a shared engram
Where a firm keeps an expert's know-how, the expert owns the engram, chooses its sources, and can revoke the firm's access.
Because: The law on who owns a working twin is still being written; consent settles it before it is tested.
- live
Not a companion
Duplikate is a helper for your work and your life's logistics. It is not a companion, and we do not market it as one.
Because: Companion chatbots carry rules of their own, and that is not what this is.
Disclosure is built in, not optional.
A message your helper drafts and you approve carries a visible line, "Drafted by Sam's AI, approved by Sam", and a machine-readable marker in its headers. A recipient never has to guess.
- From
- Sam
- To
- A buyer at a restaurant group
- Subject
- Your reorder
Thanks for the reorder. I can do 8% and move you to 60-day terms. Shall I confirm the 40 cases at that?
Drafted by Sam's AI, approved by Sam.
Show the machine-readable tag
X-Drafted-By: ai
X-Approved-By: ownerAn illustration: the tag's final format follows the standard the product adopts.
Google user data.
No Google connector exists yet. The first builds are import-first: you export your own mail and hand it to us. When a connector exists, this section will carry the disclosure Google's Limited Use policy requires, in its words, and the security assessment it passed.
Security, as it is today.
The site is static, served from a content delivery network, and stores nothing of yours: the form on the Start page sends only what you type in it, over an encrypted connection, and the demos run on fictional data in your browser. Audit badges come when audits have been passed, not before.
Vulnerabilities: hello@thetraide.com
Who processes what, by category.
- The site's host and network
- Serves these pages and receives the Start form.
- An email delivery service
- Sends us a copy of the form you submit, and nothing else.
- Analytics, only if you allow it
- Which pages help. Off until you say otherwise, and nothing is stored before then.
- AI model providers, through their API
- Receive the retrieved nodes and the situation for each decision, under terms that exclude training. Never your raw record.
What people ask first.
- Do you read my emails?
- A senior engineer scopes the sources with you under a written agreement, and the pipeline reads what you connect. Of it, only what you wrote becomes nodes; received mail is parsed as context for your replies and never stored. Names become roles before storage, so the store itself holds none.
- Is my data used to improve Duplikate for other customers?
- No. Each engram is its own store, built from one person's record for that person. We improve the pipeline from our own founder's record and from what customers choose to tell us, never from a customer's record.
- What does the recipient of a message see?
- A visible line that the message was drafted by your AI and approved by you, and a machine-readable marker. If you edit a draft heavily before sending, the line still says the draft began with your AI.
- Where is it hosted?
- Agreed per build. The default is a store we run in the region you choose; your own infrastructure is an option. Either way, export gives you all of it at any time.
- Who do I write to about privacy?
- Write to hello@thetraide.com. A person reads it. The privacy policy names what we collect on this site and what the service processes, and this page is kept in step with it.
Read the policies, or ask.
Ask us anything on this page.
You'll talk to a senior engineer, not a sales rep, and leave knowing what your engram would be built from and how it would be measured.