Privacy policy

Effective date November 2026

Datum handles account information and benchmarking research to provide and secure the service

What we collect

DataWhat it includesWhere it comes from
AccountName, username, work email address, workspace and roleYou, at sign-up or in your profile
Sign-up requestName, email address, the time you accepted the terms, and whether the request was approvedYou, at sign-up
Sign-in codesA one-time code, stored only in a form that cannot be read back, valid for 10 minutesGenerated by Datum
Research contentProjects, goals, frameworks, organizations researched, answers, conclusions, source links, quoted passages and, in the web app, uploaded or retained source materialYou, directly or through a connected service
Connected appsWhich services you connected, when, and the tokens that let them act for youCreated when you connect an app
Activity recordWho changed what and when, kept so changes can be tracedGenerated by Datum
Technical dataIP address and request details used for security and troubleshooting, and a session cookie that keeps you signed inYour browser or app

Datum uses a session cookie to maintain sign-in. You can clear it in your browser.

How we use it

  • To provide the service: sign you in, store and show your research, and let connected apps read and save it for you.
  • To send service email: sign-in codes, sign-up confirmations and notices about your account.
  • To keep the service secure: limit repeated requests, trace changes, and investigate misuse.

Who receives it

  • People with project access. Workspace members with project permissions can access the research available to their role. Datum may access information to provide support, investigate misuse or handle requests.
  • Connected services. A service you authorize can receive your Datum username, workspace name, role and permissions. It can retrieve or update project data within the access you grant. Datum receives the inputs needed for each requested action, such as a project ID, a finding or a source quote. Datum integrations do not request full conversation histories. Each service handles the data it receives under its own privacy policy.
  • Anyone with a share link. If you create a share link for a project, anyone holding it can read that project's research, without signing in, until you revoke the link. Recipients can forward the link or copy the research. Revocation stops future access through the link. Copies already made may remain.
  • Email delivery. Service emails are sent through an email provider (Mailgun, in the United States), which receives the recipient address and the message.
  • AI providers for research run by Datum. If research runs within Datum, the AI provider configured for the workspace receives the research inputs and relevant evidence. For research you run in a connected service, that service handles its own processing.
  • Legal requests. We disclose data when the law requires it.
  • Support, complaints and privacy requests. When you contact Datum, we receive your contact details, message and any information you provide.

We do not sell personal data or share it for advertising.

How long we keep it

  • Accounts. We keep account records while your account is active. After routine account closure, we remove account records from live systems within 90 days. We keep incomplete sign-up requests for 30 days from submission and declined requests for 90 days after the decision. For approved users, we keep the record of terms acceptance with the account.
  • Research and source files. We keep these while the workspace needs the project. After authorized project closure, we remove them from live systems within 90 days. Shared workspace research may remain after an individual account closes.
  • We handle privacy erasure requests separately and remove eligible data sooner where required by applicable law.
  • Sign-in codes: usable for up to 10 minutes. We delete used and expired code records during the next daily cleanup.
  • Connected apps: access tokens expire after 1 hour and refresh tokens after 30 days. Disconnecting revokes access in Datum. We keep connection records while the service is connected and remove eligible expired or revoked token records during the next daily cleanup.
  • Activity records and backups. We keep routine activity records for 90 days and backups for 30 days from creation.
  • Routine server and proxy logs. We keep these for 30 days from creation.
  • Support and complaints. We keep correspondence while the case is open and review it for deletion 12 months after closure. We may keep relevant correspondence longer when needed for a dispute or legal obligation.

Your choices

  • Change your name in your profile.
  • Disconnect a service at any time to revoke its access to Datum. Use that service's privacy controls to manage information it already received.
  • Revoke a project's share link at any time to stop future access through it.
  • Email privacy@rkitect.io to raise a privacy complaint or request access, correction or deletion. Tell us which Datum account the request concerns. We may verify your identity and explain what can be deleted, including any records kept for legal obligations or held in a shared workspace.