Privacy Policy
What we collect
The Reelier CLI (open source, runs on your machine) collects nothing. There is no telemetry and no phone-home. When you record or replay a skill, any LLM calls made during recording use your own API key, sent directly to the model provider you choose (BYOK — bring your own key). Nothing about your machine, your skills, or your runs leaves it unless you explicitly run reelier push.
Reelier Cloud (reelier.com)collects only what’s needed to run your account:
- When you sign in with GitHub, we store your GitHub id, username, email, and avatar URL.
- Run records you push with
reelier push, or that your scheduled replays generate — the same receipt data (steps, outcomes, tokens, timing) shown in your dashboard. - API keys are stored only as SHA-256 hashes. We never store the raw key after it’s first shown to you.
How we use it
Solely to operate your account: authenticate you, show your ledger and dashboard, and run your scheduled replays. We do not sell your data, and we do not use it for advertising.
BYOK / your model keys
Your LLM provider API keys are never received or stored by Reelier Cloud. Level-0 replay — the deterministic tool-call replay that powers scheduled runs — calls no model at all, so there is no key for Reelier Cloud to hold in the first place.
Where it’s stored
Reelier Cloud runs on Vercel (hosting) with a Neon PostgreSQL database, both in the United States.
Your rights / control
Your skills are plain markdown files that live in your own repository — portable, exportable, and never locked to Reelier. You can request deletion of your Reelier Cloud account and stored data by contacting us (below). The engine is AGPL-3.0, so you can also self-host and never share any data with us at all.
Every run is private by default; a run only becomes publicly viewable (via its receipt page and badge) when you explicitly click “Share” on it in your dashboard, and you can make it private again at any time with “Unshare.”
GitHub sign-in scopes
We request the minimum GitHub OAuth scopes needed to identify you: read:user and user:email. We do not request access to your repositories.
Third parties
We share data only with the infrastructure providers needed to run the service: GitHub (authentication), Vercel (hosting), and Neon (database). No data is shared with any other third party.
Changes to this policy
If this policy changes materially, we’ll update the effective date above. Continued use of Reelier Cloud after a change means you accept the update.
Contact
Questions or deletion requests: max@seldonframe.com or open a GitHub issue. This service is operated by Fixlyai LLC, governed by the laws of the State of Texas, United States.