Legal
The documents, and what each one answers
Six documents, three of them published. They are written from what the product actually does rather than from a template, which is why they talk about adaptation licences and an immutable audit log instead of about user-generated content in general.
Published documents
Terms of Service
The agreement itself. Who owns what you write, what publishing permits and what it does not, the terms you name when you make a Concept adaptable, responsibility for Agents, and the fact that export keeps working for 30 days after an account ends.
Version 0.113 September 2026Read it
Answers questions like
- Do I keep copyright in what I write?
- What does making something adaptable actually grant?
- What does it cost?
Privacy Policy
What we hold and for how long, across account data, content and the audit log. Who else touches it. Why the audit log does not forget, and what that means when you ask to be deleted. The rights we extend to everybody rather than to whoever happens to live in the right country.
Version 0.113 September 2026Read it
Answers questions like
- What happens if I ask you to delete everything?
- Can an owner see who rated their Concept?
- Where does the data physically sit?
Acceptable Use Policy
What may not be published, as eight numbered rules. How to report something and what we commit to doing about it. The ladder of responses, from a note to termination. How to appeal a decision, and who reviews it.
Version 0.113 September 2026Read it
Answers questions like
- Can I import this thing I found?
- Something here is infringing my work.
- You restricted my Concept and I think you were wrong.
Coming before general availability
Named here rather than left out, so nobody has to ask whether they were considered.
Not yet written
Data Processing Addendum
The formal terms for us processing an organization's content on its instructions. Every serious buyer's legal team asks for one.
Not yet written
Sub-processors
The standing list of who else touches the data, with purpose and region, and a way to be told when it changes. Named today inside the Privacy Policy.
Not yet written
Security and disclosure
The scope of good faith research, what we will not pursue, and the response commitment the contact page already makes.
There is no cookie policy, and there is not going to be one unless something changes. We set a single session cookie and run no advertising trackers, so a section inside the Privacy Policy is proportionate to what there is to say. If analytics are ever added, that becomes its own page and asks before it measures anything.
Where to write
- legal@takeida.com
- Questions about these documents, and copyright complaints.
- privacy@takeida.com
- Access, correction, deletion and the rest of section 12 of the Privacy Policy.
- abuse@takeida.com
- Reporting something published here.
- appeals@takeida.com
- Appealing a decision made under the Acceptable Use Policy.
A person reads each of these. Anything that does not fit one of them is on the contact page.