Skip to content

Privacy notice

This notice describes the hosted beta of Fractaloom run by [Operator name]. Text in square brackets is a placeholder the operator replaces with their own legal wording before inviting an organization; the factual statements about the product are kept accurate by the team that builds it (docs/11-security.md in the repository names the code behind each one).

Who is responsible

[Operator name], [address], reachable at [contact email], operates this instance of Fractaloom for the organizations taking part in the beta. For the data of your organization, your organization decides what is connected and who may sign in; [Operator name] processes that data on its behalf to provide the service. [Jurisdiction and governing law.]

What we hold

For each organization that takes part:

  • The text of the documents, messages, tickets and files read from the systems its administrator connected (GitHub, Slack, Google Drive, Notion, Jira), with the permissions those systems report for each item.
  • What Fractaloom derives from that text: entities, facts, decisions, events, relationships, embeddings.
  • The questions people and agents ask, the answers given, the feedback and corrections they add, the notes they write in Memory, and the runs of the agents they create.
  • Account data: name, email address, role, group memberships and sign-in sessions of the people who use it; the organization's connection credentials for the connected systems, stored encrypted.
  • Operational records: a request log (method, path, status, duration, user id, request id; never question text or document content), an audit log of meaningful actions, and, when the operator turned it on, error reports without request bodies or user identifiers.

Where it is and who can reach it

  • Everything lives in one PostgreSQL database and the services around it on Render.com, in the region named here: [region, e.g. Oregon, United States]. Render keeps daily backups of the database for the period its plan provides.
  • Document text and the permission-filtered context of a question are sent to Anthropic's API to extract knowledge and to write answers; the operator's agreement with Anthropic governs that processing. Embeddings are computed on the instance itself.
  • Nothing is sent to anyone else, except: alerts about a failing connection to the operator's own channel (which never contain your content), and error reports to the operator's error-tracking project when that is turned on.
  • Each organization is a separate tenant: every query is scoped to it, and a person only ever sees what the source systems already allow them to see.
  • On the operator's side, only [the named administrators] can reach the database, the logs and the backups, for the purpose of running the service and investigating a problem you report.

How long

  • Document text and derived knowledge: for as long as the source is connected, then removed when the administrator deletes the source or the organization leaves the beta.
  • Questions, answers and the audit log: [365] days, then deleted by housekeeping.
  • Personal notes: [365] days; agent memory: [90] days; team and organizational notes: until deleted.
  • Backups: the platform's retention period, after which they expire.

Your rights and the people's rights

  • An administrator can disconnect or delete any connected source at any time; the knowledge that only it supported is deleted with it.
  • A person can ask to be forgotten: their name, email and external ids are replaced, their sessions revoked, their memberships, personal notes and questions deleted; documents they wrote in the connected systems remain the organization's records. Ask your administrator or write to [contact email]; it is done within [30] days.
  • At the end of the beta, or on request, the whole organization is deleted with one command, and this is confirmed in writing.
  • Anyone can ask [contact email] what is held about them and receive it; GET /export returns what a signed-in person may see.

Changes

This notice is dated [date]. Changes are announced to the organization's administrator before they apply.