Privacy Policy
Draft for review. This text has not been reviewed by a lawyer and items marked [__ __] must be completed by the owner before publication.
Last updated: [__DATE__]
1. Who is responsible
The data controller is [__OWNER_TO_CONFIRM__]. Privacy contact: [__OWNER_TO_CONFIRM__].
2. What we collect
Account: your email address, name (if you give it) and a salted hash of your password (we do not store the password itself). If you sign in with Google, the identity details Google shares with us for sign-in.
Your work: the strategies and projects you save, and your usage of limited features (for example how many backtests or exports you have used this month).
Payments: invoices, the plan, amount, your transaction reference and its verification status. We do not collect your wallet's private keys.
Support: tickets and messages you send us.
Technical: a sign-in session cookie, your language choice (stored in your browser), and security and audit logs that can include IP address and time of actions.
3. How we use it
To run your account and the service, apply plan limits, confirm payments, answer support tickets, send account emails (such as email verification and password reset) and protect the service from abuse.
4. Sharing
We use service providers to run Lupuso, such as hosting, email delivery and blockchain data lookups for payment verification. Google receives data only if you choose Google sign-in. We do not sell your personal data.
Full list of providers and their locations: [__OWNER_TO_CONFIRM__].
5. Cookies and storage
We use a session cookie to keep you signed in and your browser's local storage to remember your language and unsaved builder state. We have not confirmed the use of advertising or analytics cookies; this section will be updated if they are added.
6. Retention and deletion
How long we keep data and how to request deletion: [__OWNER_TO_CONFIRM__].
7. Your rights
Depending on where you live, you may have rights to access, correct, export or delete your data. To make a request, contact [__OWNER_TO_CONFIRM__].
8. Security
Passwords are stored as salted hashes. No system is perfectly secure, and we cannot guarantee absolute security.
9. Changes
We may update this policy. The date at the top shows the latest version.