Privacy
What we collect and why.
A plain summary of how personal data is handled in the beta. A full privacy policy and terms of service are being prepared and will replace this page before general release.
What we collect
- Account details: your name, email address, role and sector, and your password (held as a hash by Supabase Auth).
- What you enter: companies, directors and their DINs, PANs and DSC dates, counterparties and exposure amounts, meeting content, register entries, insider-trading entries, and documents clients upload to your requests.
- Usage data: page views and device details through Google Analytics.
- Optional: a Telegram chat ID if you link alerts.
Why
To run the product for you: build your calendar, send your alerts, produce your documents. We do not sell your data and we do not use it to train models.
Who handles it
Railway hosts the application and its storage, in US West (California). Supabase handles sign-in. Google Gemini and OpenRouter process text when you use an AI feature. Google Analytics records page views. Razorpay handles payments once billing starts. The security page lists each one and what it sees.
Your control
You can export your calendars, registers, insider-trading logs and risk lists, and archive companies and counterparties. Tools for full deletion and export requests under the Digital Personal Data Protection Act are not built yet.
Third parties' data
Directors' names, DINs and PANs, and insider-trading entries, belong to people who are not our users. They are used only to produce the records you ask for. PANs are masked on screen.