Privacy Policy
Last updated November 20, 2026
This policy explains what Rindkey collects, why, and what we do with it. Rindkey (rindkey.com) is operated by Upleads LLC, doing business as Rindkey (“Rindkey”, “we”, “us”). Questions or requests: hello@rindkey.com.
1. Who this covers
Rindkey has two kinds of users:
- Sellers: people and businesses who create a Rindkey account to issue license keys, host files and run a customer portal for their products. For seller account data we decide how it's used, so we are the data controller.
- Sellers' customers: people who bought something from a seller and use a license key, download a file or open the seller's customer portal. We process their data on the seller's behalf and on the seller's instructions. The seller is responsible for telling their customers how their data is used. For questions about a specific purchase, contact the seller first; we will help them answer.
Visitors to rindkey.com who do neither are covered too (see “Website visits” and “Metrics”).
2. What we store
- Seller accounts: store name, email address, a public store handle (used in portal links), your plan, a hash of your API key (we can't read the key itself), and settings. If you connect Stripe, your Stripe webhook signing secret and optional Stripe API key are stored encrypted (AES-256-GCM).
- Products: names, activation limits, license length and the Stripe price IDs you enter.
- License keys and activations: each key, its status and expiry, the product it belongs to, the customer's email and name (when provided by the seller, Stripe or a Lemon Squeezy import), order and subscription references from Stripe or Lemon Squeezy, and for each activation an instance ID, the instance name your app sends (often a device name) and when it was created.
- Files: product files that sellers upload or import are stored privately in Cloudflare R2, with their name, size and version. They are only served through signed links that expire within 15 minutes and stop working when a key is revoked.
- Emails we send: sign-in links, license key emails and other service messages are sent through Cloudflare Email Service. We keep a record of each message (recipient, subject, body, delivery status) for up to 90 days after it is sent so we can troubleshoot delivery, then delete it automatically.
- Waitlist: if you join the waitlist, your email address and, if you choose, what you sell.
- Billing: when a seller subscribes to a paid plan, Stripe handles the payment. We store the Stripe customer and subscription IDs, the plan, billing interval and status. We never see or store card numbers.
3. The free readiness check and Lemon Squeezy keys
The readiness check at /check and the dashboard import ask for a Lemon Squeezy API key. That key is used in memory for that single request, only to read your Lemon Squeezy data (the import then writes the products, keys, activations, customers and files it reads into your Rindkey account). The key itself is never written to our database, storage or logs. Lemon Squeezy keys can't be limited to read-only, so we recommend creating a key just for this and deleting it afterwards. If you add an email address to the readiness check, it is added to our waitlist.
4. Signing in with Google or GitHub
If you choose “Continue with Google” or “Continue with GitHub”, we ask only for your basic profile: your email address and name (Google scopes openid, email, profile; GitHub scopes read:user and user:email). We use your verified email address to find or create your Rindkey seller account and your name to label your store. We do not store the access token, we do not access your contacts, files, repositories or anything else, and we do not post anything on your behalf.
Google API Services: Rindkey's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to sign you in and run your account. We do not sell it, use it for advertising, or use it to train AI or machine-learning models, and humans do not read it except for security, legal compliance, or with your permission to help with a support request.
5. Cookies and sessions
We use only the cookies needed to run the service. There are no advertising or tracking cookies.
rk_s: keeps a seller signed in to the dashboard. HttpOnly, Secure, lasts 30 days or until you sign out.rk_oauth: holds a one-time security value while you sign in with Google or GitHub. HttpOnly, Secure, deleted after sign-in or within 10 minutes.
Customer portal and email sign-in links carry a signed, expiring token in the link itself instead of a cookie.
6. Metrics and website visits
Our own metrics are daily counts only (for example, how many times the homepage was viewed, how many readiness checks ran, how many sellers signed up). If you arrive from a link with a ref or utm_source tag, we also count which tag it was (for example, how many readiness checks came from a given article). The tag travels in the page link, not in a cookie. These counts contain no IP addresses, cookies or personal data, and known bots are excluded.
We also use Cloudflare Web Analytics, which loads a small script from static.cloudflareinsights.com on our pages to measure page views and how fast pages load. Cloudflare says it doesn't use cookies or local storage for this and doesn't fingerprint individuals by IP address or browser details. We see only aggregate reports (for example, page views, top pages, referring sites and countries), not a profile of any one visitor. Cloudflare processes the request details as described below. We don't use any other analytics or advertising tools.
Like any website, our hosting provider Cloudflare processes your IP address and request details to deliver pages, block abuse and keep short-lived logs. We use your IP address briefly for rate limiting (sign-up, sign-in and other forms); those counters expire within about two hours. Pages load fonts from Google Fonts, so your browser connects to Google to fetch them.
7. Who we share data with
We don't sell personal data. We share it only with the providers that run the service, and only as needed:
- Cloudflare: hosting, database (D1), file storage (R2), key-value storage, email sending, security and aggregate web analytics.
- Stripe: payments for Rindkey plans; for sellers who connect Stripe, the purchase events Stripe sends us to issue keys.
- Google and GitHub: only if you choose to sign in with them; Google Fonts for web fonts.
- Lemon Squeezy: only when you give us a key to read your own Lemon Squeezy data.
We may also disclose information if required by law, or to protect the rights, property or safety of our users or the public.
8. How long we keep data
- Seller account data, products, keys, activations, customers and files: for as long as the seller's account exists. When a seller deletes their account (email hello@rindkey.com), we delete this data within 30 days.
- Email delivery records: deleted automatically 90 days after sending.
- Waitlist entries: until you ask us to remove them or we stop running the waitlist.
- Billing records: as long as needed for accounting and tax law.
9. Security
Data is sent over HTTPS. Stripe secrets are encrypted at rest, API keys are stored only as hashes, download links and sign-in links are signed and expire, and access to production systems is limited. No system is perfectly secure; if we learn of a breach that affects your data, we will notify you as required by law. We do not currently hold security certifications such as SOC 2 or ISO 27001.
10. Your choices and rights
You can ask us to access, correct, export or delete your personal data, or object to how we use it, by emailing hello@rindkey.com. Depending on where you live (for example under the GDPR or California law) you may have additional rights, including the right to complain to your local data protection authority. Sellers' customers should contact the seller first; we will act on the seller's instructions. You can revoke Rindkey's access in your Google or GitHub account settings at any time.
11. Children
Rindkey is a business tool and is not directed to children under 16. We do not knowingly collect their data.
12. International transfers
Our providers may process data in the United States and other countries. Where required, we rely on the safeguards those providers offer, such as standard contractual clauses.
13. Changes and contact
If we change this policy we will update the date above, and for significant changes we will email sellers before they take effect. Contact: Upleads LLC, doing business as Rindkey, hello@rindkey.com.