Skip to content
Too Many AI Projects

Security

Too Many AI Projects stores API keys and tokens for the analytics, search, revenue, newsletter, AI billing and code hosting services you connect. This page describes how accounts and those credentials are protected.

Signing in

  • Passwords are stored only as bcrypt hashes. Nobody, including the operator, can read your password.
  • Failed sign-in attempts are counted for each pairing of email address and IP address (8 failures in 15 minutes) and for each email address across all IP addresses (40 failures in 15 minutes). Reaching either limit blocks further attempts for 15 minutes. There is no separate limit on one IP address trying many different email addresses.
  • Failed passkey sign-ins, and sign-ups that use an email address which is already registered, are counted per IP address (8 in 15 minutes). Password reset emails are limited to 5 per email address in 15 minutes.
  • Wrong two-factor codes and wrong passwords entered inside the app are counted per account, with the same limit of 8 in 15 minutes and the same 15-minute block.
  • These limits are a backstop: if the database that holds the counts cannot be reached, the attempt is allowed through instead of being blocked.
  • The session cookie is HttpOnly, sent only over HTTPS, and expires after 30 days.
  • Changing or resetting your password signs out every other session. Resetting it by email also removes any passkeys on the account, so they have to be added again.
  • Password reset links are single-use and expire after one hour. Only a hash of the link's token is stored.

Two-factor authentication and passkeys

  • You can require a six-digit code from an authenticator app (TOTP) whenever you sign in with your password. Each code is accepted once.
  • Turning it on gives you ten single-use recovery codes. Only their hashes are stored, so they are shown once.
  • Turning two-factor authentication off needs both your password and an authenticator or recovery code.
  • Passkeys (WebAuthn) let you sign in with a fingerprint, face or security key. The passkey must verify you on the device, so a passkey sign-in does not ask for the authenticator code as well.
  • For each passkey the app stores its public key and credential ID, a signature counter, how the device connects (for example USB or built in), whether it is a single-device or synced passkey and whether it is backed up, the name you give it, and when it was added and last used. No private key and no fingerprint or face data is stored.

Credentials you connect

  • API keys, tokens, Google refresh tokens and Google service-account keys are encrypted with AES-256-GCM before they are written to the database. The encryption key is held in the server's configuration, not in the database.
  • One part of a key is kept unencrypted: the last four characters of each OpenAI, Anthropic and GitHub key, so the app can show which key is saved (for example "key ending 1a2b").
  • Stored credentials are used on the server to call the provider. Apart from those last four characters they are not sent back to your browser, and they are never included in a data export.
  • Google is connected by pasting a service-account key, which is used with read-only access to Analytics and Search Console.
  • Removing the last website that uses a Google connection deletes the stored key.
  • Two-factor secrets are encrypted the same way.

Keeping accounts separate

  • Every project, website, connection and alert belongs to one account. Each page and each change checks that the record belongs to the signed-in account before reading or writing it.
  • There is one exception, for the operator of the service. An admin page, open only to accounts whose email address is listed in the server's configuration, shows the 50 most recent failed or partly failed refreshes across all accounts, each with the owner's email address, the site's domain and the error text, along with overall counts of sites and refreshes.
  • Changes are refused if the session cannot be verified against the database at that moment.
  • Share links are read-only and show only a fixed set of portfolio fields. The link contains a random 256-bit token, only a hash of it is stored, and the page asks search engines not to index it. You can set a link to expire and revoke it at any time.

In the browser and on the network

  • Pages are served with a strict Content Security Policy: scripts run only when they carry a one-time value issued for that page load, and the signed-in app loads no third-party scripts.
  • The site is served over HTTPS with HSTS and cannot be embedded in a frame on another site.
  • When the server fetches an address you supply (an uptime check, or a self-hosted Plausible instance) it refuses private and internal network addresses.

Your data

You can download your data or delete your account from Settings at any time. Deleting the account removes everything linked to it. The records kept to limit sign-in attempts are not linked to an account, so they are not removed with it. The privacy policy lists what is stored, how long it is kept and which other services are involved.

Reporting a problem

If you find a security problem, please email support@toomanyaiprojects.com with enough detail to reproduce it.

Security · Too Many AI Projects