Privacy Policy
Last updated: June 2, 2026
Observable Code (“Observable Code”, “we”, or “us”) helps developers see whether their tracked functions ran. This policy explains what we collect and why. We collect as little as possible.
What we collect
When you add the @observable.track() decorator to a function, each run sends us a small event: the function name, whether it completed or failed, its duration, and any error type or message you surface. These events are tied to a randomly generated session identifier, not to your identity.
If you join the waitlist, we store the email address you submit so we can contact you about availability. If you create an account (a future feature), we store the email address used to sign in.
The anonymous view
A session’s live event view is reachable at a URL containing an unguessable session identifier (a version-4 UUID). Anyone who has that link can watch that session’s events in real time; the link itself is the access control. We never expose a way to list or enumerate other sessions’ events. Treat your session link like a secret.
What we do not do
We do not sell your data, we do not use third-party advertising trackers, and we do not read the contents of your functions — only the event metadata you explicitly send. Events are retained for a limited window and then deleted.
Contact
Questions about this policy? Email privacy@observable.codes.