Privacy Policy
This policy explains what Regivion collects when you use Regivion, why, and what you can do about it.
About Regivion
Regivion is the public-facing brand of this financial-information and research platform. Privacy requests are available through your signed-in Account page.
What we collect
| Data | Why |
|---|---|
| Email address | To identify your account and contact you about it |
| Password (stored only as a salted hash) | To authenticate you. We never store your password itself and cannot read it |
| Account status and creation date | To operate the account |
| Email verification status and hashed, expiring verification tokens | To confirm control of an address when email activation is enabled |
| Account-linked successful sign-ins, authentication method and initiators of jobs or privileged actions; pseudonymous signup/resend rate counters | Account security and abuse prevention. No password, MFA code, raw verification token or raw client address is retained in this security store |
| Subscription status, plan and renewal date, plus Stripe customer and subscription identifiers | To give you access to paid features and to support billing |
| Record of which policy versions you accepted, and when | To evidence consent |
| Watchlists and portfolio entries you create | To provide the features you are using |
| Copilot conversations, where server-side storage is enabled | To maintain conversation context |
| Optional first-party website analytics after acceptance: pseudonymous visits, page categories, sanitized source/campaign, country if locally available, device/browser category and signed-in/admin category | To understand website use and campaign performance, separately from account records |
What we do not collect
The analytics store does not retain raw IP addresses, raw browser user-agent strings, account identifiers, email addresses, credentials or sensitive URL parameters. Regivion does not use browser fingerprinting or advertising trackers, follow you across other websites, or sell or share analytics with advertisers. Hosting and security logs are separate and may process connection information for operation and security. Regivion never sees your card details — those go directly to Stripe.
Purposes and lawful basis
- Providing the service — performance of our contract with you.
- Billing — performance of that contract and our legal obligations.
- Security, abuse prevention and service integrity — our legitimate interests.
- Consent evidence — compliance with our legal obligations.
- Optional website analytics — your separate consent, which you can decline or withdraw using Analytics privacy choices without losing access to the service.
- Account and subscription administration — operational reporting from existing account and verified subscription records, separate from individual visitor analytics.
We do not send marketing email and we do not collect marketing consent.
Service providers
We use a small number of providers to run the service:
- Resend — delivery of requested account-verification emails using the Regivion sender.
- Stripe — payment processing and subscription management.
- Market and fundamental data providers — to supply financial data. They receive the symbols the system requests, not your identity.
- Language-model provider — where Copilot's AI features are enabled, to generate responses.
- Hosting and infrastructure — to run the application and store its data.
The definitive list of providers, their roles and their locations is [[ RETENTION PERIODS - PENDING OWNER INPUT ]] — owner review item: this must be completed with the actual provider list and any international transfer safeguards before launch.
Retention
Security audit events are retained for up to 90 days. Email proof and job-initiator records are kept with the related account and job information; deletion requests are handled through the account controls. Verification links expire after one hour; expired token records are removed within the next retention cleanup after a one-day diagnostic grace period. Rate counters expire after two days. Existing accounts without email proof retain their access and are shown as Unverified in private administration.
Optional analytics uses a random visitor identifier with an absolute lifetime of up to 24 hours and sessions ending after 30 minutes of inactivity. Pseudonymous analytics events and separate operational daily request totals expire from reporting after 30 days (operational totals use 30 Madrid calendar days). An independent hourly housekeeping task deletes expired records, normally within one additional hour, even when the site is idle. The analytics store is capped at 16 MiB; events can be lost earlier at storage limits. Your analytics preference is remembered for up to 180 days. No IP address is sent to an external country-lookup service. See Analytics privacy choices for the fields, exclusions and measurement limitations.
We keep account data for as long as your account exists. After deletion, some records are retained where we are required or permitted to keep them — typically billing records for statutory accounting periods, consent evidence, and security logs. Specific retention periods: [[ RETENTION PERIODS - PENDING OWNER INPUT ]].
Backups are kept on a rolling schedule and expire automatically. Data can therefore persist in a backup for a period after deletion from the live system; it is not restored into the live service except in a disaster-recovery event.
Your rights
Subject to applicable law you may request access to your data, correction, deletion, a portable copy, restriction of processing, or object to processing. You can also complain to your local data protection authority.
Signed-in users can request a copy of their data or the deletion of their account from the Account page, where those features are enabled. Requests are handled by a person, not instantly by the system — see the Account page and our Terms for what actually happens and when. You can use those account controls for privacy requests.
Security
Passwords are stored using salted PBKDF2-SHA256 hashing. Sessions use signed,
HttpOnly cookies. Forms are protected against cross-site request
forgery. Application logs are automatically scrubbed of email addresses,
identifiers, credentials and file paths. Where per-account databases are in
use, each account's data is held separately.
Children
Regivion is not intended for anyone under [[ MINIMUM AGE - PENDING OWNER INPUT ]]. We do not knowingly collect data from children.
Cookies
See the Cookies and Local Storage page for exactly what is stored in your browser.
Changes
If this policy changes materially we will update the version and effective date above, and may ask you to acknowledge the new version when you next sign in.