Skip to content

What keeps your flags private

Controls

  • Rules never leave the server

    The app gets only the values it asked for. Rules, other people's ids and segment lists never reach a device. Client keys get values only. Server keys also get the reason.

  • Names are hashed for client keys

    A client key receives each value under a hash of its name, made with that key, so names are not sent in clear to apps. A hash hides names that cannot be guessed. Someone who holds a key can test a guessed name, and the app you ship contains the names it asks for. Rules and other people's data never reach a device either way.

  • Apps cannot lie about who they are

    The server fills in segments and the channel from the key, so a request cannot claim a different segment or channel.

  • Keys are hashed and scoped

    A key is stored only as a SHA-256 hash and shown once. Each key covers one project, one environment and one channel. A revoked key stops working within 30 seconds.

  • Removed people lose access within an hour

    New sign-ins are blocked at once.

  • Protected environments need a reason

    Every change in a protected environment carries a written reason. Every change is in the audit log with before and after values.

  • Admin is a separate app

    It has its own sign-in pool, apart from the app your teams use.

Request access

Open a ticket and your workspace owner adds you.

Request access