Privacy Policy
What we store about you
| Data | Why |
|---|---|
| Email address | Account login, identifying your projects |
| Password | Stored only as a bcrypt hash — we cannot see or recover your actual password |
| Project configuration | Your chosen algorithm, limits, and project name |
| Project API key | Used to authenticate your own application's calls to /v1/check |
| Monthly usage count | Requests per project, shown on your dashboard |
| Payment/order IDs | Linking a completed Razorpay payment to your plan upgrade — we never see or store your card details, Razorpay handles those directly |
Your end-users' data
When your application calls /v1/check with an
identifier (e.g. one of your own users' IDs or IP
addresses), that identifier is used to key a short-lived rate-limit
counter in Redis. These counters expire automatically (typically within
minutes to a few hours, depending on the algorithm and window you
configured) and are not linked back to your account's email or used for
any purpose beyond enforcing your configured rate limit.
Where it's stored
All data lives in a Redis database on infrastructure we operate. Backups are taken automatically; see the main repository's README for operational details on data retention and persistence.
What we don't do
- We don't sell or share your data with third parties for advertising.
- We don't read the content of what your application is rate-limiting — only the identifier string and request counts.
- We don't store payment card details; Razorpay processes and stores those under its own policies.
Deleting your data
Delete a project from the dashboard to immediately remove its API key, configuration, and associated rate-limit data. To delete your account and email entirely, contact us via the channel below.
Contact
Questions about this policy: reach out via the GitHub repository's issue tracker.