Privacy Policy

Regivana is operated by the individual or entity identified on the Stripe account and contact channels used for the service. For privacy questions, use the contact form.

Account information. When you create an account, we store information needed to operate it, including your email address, an internal user identifier, and your subscription plan status (Free, Trader, or Pro) as recorded in our database.

Email and password sign-in. If you register with email and password, authentication is handled through Supabase Auth. We do not store your password in plain text; Supabase manages credential verification.

Google Sign-In. If you choose Continue with Google, authentication is handled through Google and Supabase using the OAuth scopes configured for that flow (typically basic profile and email scopes used for sign-in, not Gmail, Drive, Contacts, Calendar, or other Google content). We receive only what Google and Supabase pass back to create or access your Regivana account, such as a Google account identifier, email address, and basic profile fields required for authentication.

Payments. Trader and Pro subscriptions are processed by Stripe. Regivana does not store full payment card numbers. Stripe processes payment and billing details under its own terms and privacy policy. We store subscription-related identifiers (for example Stripe customer and subscription ids) and plan status needed to grant access after a verified payment event.

Pro workspace data. When an account plan is Pro, we store the markets you follow, the alert rules you save (market, event, optional timeframe or target, and whether the rule is enabled), a dashboard checkpoint used for Since Last Check, and alert delivery records needed to send or retry a message. We use the email address on your account to send transactional market-alert emails when you enable alerts. Those emails are sent through Resend. They follow Regivana’s market observation cycle. They are not tick-by-tick, they are not guaranteed to arrive, and they are not trading signals or entry recommendations.

Usage and analytics. When production analytics environment variables are configured, the site may send limited product analytics events to PostHog (for example page views on public and market routes, market navigation, upgrade or checkout funnel steps, and auth or billing actions such as checkout started). Events are allowlisted in code and are not designed to include email, message content, or payment card data. If analytics is not configured, those events are not sent. We may also process standard server and hosting logs (for example request metadata needed to operate and secure the site).

Contact. If you use the contact form, we receive the email address and message you submit. An Enterprise enquiry also includes your name and organization, and may include an optional team size and use case. Submissions are delivered through Netlify Forms. They are not stored in the Regivana database.

We do not intentionally collect special categories of personal data through the product. Do not send passwords, full card numbers, or brokerage credentials through the contact form.

• Create, authenticate, and maintain your account
• Provide Free, Trader, and Pro access according to your plan
• Store followed markets, alert rules, the dashboard checkpoint, and alert delivery records for a Pro account
• Send transactional alert emails you enable, through Resend
• Process subscriptions and manage billing state through Stripe and our database
• Operate, secure, and troubleshoot the service
• Respond to contact and support requests
• Understand product usage through optional analytics
• Comply with applicable legal obligations and enforce these terms

We do not use Google account data for advertising.

Google Sign-In is used only to authenticate you and create or access your Regivana account.

We access only the information necessary for that authentication flow according to the OAuth scopes requested in the application configuration.

Regivana does not access Gmail, Google Drive, Contacts, Calendar, or unrelated Google account content through the sign-in flow described here.

Google user data is not sold and is not used for advertising.

We may share Google-related authentication data only with service providers that help us run authentication and hosting (such as Supabase), or when required by law. Where Google API Services user data is received, our use and transfer of that information will comply with the Google API Services User Data Policy, including the Limited Use requirements, to the extent they apply to our use of those APIs.

We use third-party providers to run Regivana, including:

• Supabase — authentication and database infrastructure
• Stripe — subscription checkout and billing
• Resend — transactional alert email when you enable alerts on a Pro account
• Netlify — hosting, deployment, and form delivery for contact messages
• PostHog — optional product analytics when enabled in production configuration

These providers process data on our behalf to deliver their services and are governed by their own policies where applicable.

We keep information for as long as reasonably necessary to provide the service, meet operational requirements, resolve disputes, and comply with applicable obligations. Account and billing records may be retained while your account exists and for a period afterward where needed for billing history, security, or legal compliance. You may request deletion of your account subject to limitations described below and applicable law.

We use industry-standard practices appropriate to a small SaaS product, including encrypted transport (HTTPS), access controls on infrastructure accounts, and separation between client-visible keys and server-only secrets. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

You may manage a paid Trader or Pro subscription through the billing management flow. You may disable an alert rule when your plan includes alerts. You may sign out at any time. Depending on where you live, you may have rights to access, correct, or delete personal data. To exercise those rights, contact us through the contact page. We may need to verify your request.

Regivana is not directed at children. We do not knowingly collect personal information from children.

We may update this policy from time to time. The “Last updated” date at the top will change when we do. Continued use of the service after an update means you accept the revised policy, subject to applicable law.

Questions: Contact.