This policy explains what data Cryptorify processes when you use the platform, why we process it, where it is stored and what control you have. It is written to be read, not to hide behind legal density.
1. Data we collect
Account data: email address, authentication identifiers, display name and preferences. Passwords are handled by Supabase Auth and are never stored in plaintext or accessible to application code.
Workspace data you create: trade plans, journal entries, token scans, signal records, watchlists, alerts and notes. This data belongs to you and is used only to provide the service.
Billing data: subscription status, plan identifier, and PayPal or Skrill subscription and transaction references. We do not store card numbers; payment instrument data stays with the payment provider.
Technical data: request metadata, error logs and security events required to operate and protect the service.
2. Why we process data
To provide the features you request, to enforce plan limits, to process subscriptions, to secure the platform and to communicate service messages.
We do not sell personal data, and we do not use your private trading records to train third-party models. If an AI feature is used, the relevant records are sent to the configured provider only to produce the response you requested.
3. Storage and security
Data is stored in Supabase PostgreSQL with Row Level Security enabled on every user-owned table. Authorization is enforced server-side; client-supplied user identifiers are never trusted.
Optional exchange credentials are encrypted with AES-GCM using a key held as a Cloudflare secret and are never returned to the browser.
- TLS in transit, encryption at rest at the database provider
- Row Level Security scoped to the authenticated user
- Administrative access separately authorized and audited
- Secrets stored as Cloudflare Worker secrets, never in the repository
4. Processors
We use infrastructure and service providers to operate the platform: Supabase (database and authentication), Cloudflare (hosting, CDN and security), PayPal and Skrill (subscriptions and fallback payments), Resend (transactional email), plus the market-data, blockchain-data, news-feed and AI providers configured by the operator.
Each processor receives only the data necessary for its function.
5. Retention and deletion
Workspace data is retained while your account exists. You can delete individual records at any time and request full account deletion from Settings.
Billing records may be retained for the period required by tax and accounting obligations even after account closure. Security and audit logs are retained for a limited period.
6. Your rights
Depending on your jurisdiction you may have the right to access, correct, export, restrict or delete your personal data, and to object to certain processing. Data export and account deletion are available directly in the application.
Requests can also be sent to the support address listed on the contact page.
7. Cookies
Essential cookies are used for authentication sessions and security. Analytics cookies are only set when an analytics provider is configured and, where required, after consent. See the Cookie Policy for details.
8. Contact
Privacy questions and requests can be sent to the support address published on the Contact page. We aim to respond within 30 days.
This document is a template prepared for the platform owner and is not legal advice. Before launch, have it reviewed by a qualified lawyer in the operating jurisdiction and update the legal entity name, address and contact details.