Keystone

Privacy Policy

Last updated: 2026-10-26

1. Who we are and what we collect

Keystone (keystone-core.pro) is run by a private individual, Igor Saenko, Serbia ("we"). If a company takes over the service, we will name it here and tell you before the change. We are the controller of the personal data described here. Contact: runafterasun@gmail.com.

Keystone stores architecture diagrams. Your source code never reaches us: the AI tool you connect reads it on your own machine and sends Keystone only the diagram.

  • Account: email, name, password hash (never the password), avatar if you upload one, account dates. From you, or from Google or GitHub when you choose that provider. GitHub sign-in also stores its permanent numeric account ID to keep the same account after a GitHub login or email change.
  • Project content: diagrams, tables, scenarios, decisions, comments, notes, drawings, version history. From you, your team and the AI tools you connect.
  • Organizations and access: memberships, roles, project access, invitations. From you and your team.
  • AI tokens: a hash of each token (never the token itself), its name, scope and expiry. From you.
  • AI activity: proposals, validation and antipattern reports the AI sends, with their author. From the AI tools you connect.
  • Feedback: your messages, status and replies from application administrators.
  • First-party analytics: page-view totals, normalized route labels, referrer domains and a hash of a random browser identifier for unique-visitor counts. We do not record URL queries, fragments, private project IDs or browser fingerprints in analytics.
  • Technical data: IP address and browser data in server logs, sign-in attempts, last-seen time. From your browser.

We do not collect your source code, repository contents or the values of secrets in your configuration. We run no advertising and no third-party analytics.

When you choose GitHub sign-in, we read your public profile and verified primary email, including a private primary email. We do not request repository permissions or retain GitHub access tokens after sign-in.

2. Why we use it, who helps, where it lives

We use your data only to run Keystone for you; we never sell it.

  • Your account, projects, collaboration and AI connections: to perform our contract with you (GDPR art. 6(1)(b)).
  • Security — sign-in limits, blocking abuse, logs: our legitimate interest in a safe service (art. 6(1)(f)).
  • Records the law requires: legal obligation (art. 6(1)(c)).

Processors. Friendhosting LTD hosts our servers in Sofia, Bulgaria (EU). Google LLC signs you in when you choose "Sign in with Google" and then shares your email, name and profile picture with us. We do not send email yet; when we do, we will name the provider here. The AI tool you connect (Claude Code, Cursor and others) is your own choice and runs under its provider's terms; it is not our processor.

Storage and transfers. Your data is stored in the EU. Google sign-in may involve a transfer to the US under the EU-US Data Privacy Framework.

Retention. Account and project data: until you delete them or your account. Diagram history: the last 50 saved versions per diagram (140 for interview diagrams). Server metrics: 30 days. Server logs: rotated automatically, at most 50 MB per service, so only recent entries are kept. Database backups: 30 days, then deleted. Daily analytics totals are retained indefinitely. Daily browser-identifier hashes are retained for 366 days; they are not linked to account names, email or routes.

Cookies and local storage. Keystone uses a session cookie, a "remember me" cookie for 30 days, and a CSRF protection cookie. Our own analytics also uses keystone-visitor, a random browser identifier lasting up to 365 days, to distinguish repeat views from unique visitors. Your browser's local storage keeps interface preferences such as language and panel width. We use no third-party advertising cookies.

3. Your rights and how we protect data

You can see, export, correct and delete your data yourself, and ask us for anything else at runafterasun@gmail.com. We answer within 30 days.

  • Access and portability: export any project to a file from its menu; ask us for a copy of your account data.
  • Correction: change your name, avatar and password in your profile.
  • Deletion: delete your account in the profile; your personal projects go with it. Projects of an organization stay with the organization and the links to your account are removed, but your name stays on comments you wrote there until the organization removes them or you ask us to.
  • Objection and restriction: write to us; you may also complain to your data protection authority.
  • California residents (CCPA/CPRA): you have the same rights to know, delete and correct. We do not sell or share personal information for advertising.

Security. HTTPS everywhere, passwords stored as hashes, AI tokens stored as hashes and limited to the projects and rights you choose, access checked on every request. No system is perfectly secure; we will tell you of a breach that affects you as the law requires.

Children. Keystone is not meant for anyone under 16, and we do not knowingly collect their data.

Changes. We will post changes here with a new date and email you about important ones before they apply.