Revision 2026-09-22 · updated 22/09/2026
This Policy explains what data Crypterm collects, why, and how long it is kept. It forms an integral part of the Terms of Service.
— the email address given at sign-up;
— the password, only as an irreversible hash; the password itself is never stored and is not available to the Operator;
— the sign-up date, subscription status and its end date;
— the fact, date and version of the Terms you accepted;
— the interface language you chose;
— technical data recorded by the infrastructure: IP address, browser type, request time.
The Service does not ask for or store payment card details, private keys, or exchange API keys with withdrawal permission.
— to create your account and let you sign in;
— to determine what your subscription gives you access to;
— to send service email: address confirmation, password recovery, notice of changed terms;
— to keep the Service secure and investigate abuse.
The Operator does not sell data and does not pass it to third parties for advertising.
Processors are engaged to run the Service: Supabase (database storage and authentication), the website hosting provider, and the email delivery service.
Data may be disclosed on a lawful, reasoned request from a competent authority.
The Service uses strictly necessary cookies only: the Supabase authentication session cookies and a cookie holding your chosen interface language.
No advertising or analytics trackers are used in the dashboard.
Account data is kept while the account exists and is deleted within 30 days of its removal.
Records of acceptance of the Terms and payment documents are kept for the period required by law, as evidence of the agreement concluded.
You may request access to your data, its correction, deletion or portability, and you may withdraw your consent to processing.
Send the request to support@crypterm.io from the address you registered with; a reply follows within 30 days at the latest.
Withdrawing consent results in deletion of the account, because the Service cannot be provided without processing the data listed above.
Database access is constrained by row-level security policies: each user can read only their own rows.
Traffic between the browser and the server is protected with TLS.
Data controller: [FILL IN: legal entity, registration number, address]
Email: support@crypterm.io