Privacy Policy

This Privacy Policy explains how Quarry Software (“we”, “us”) collects and uses personal information when you use Insidr.

1. What we collect

• Email address — when you subscribe to system-status alerts on /status, create Form 4 email alerts on /alerts, join an optional product email list if offered, or subscribe via Stripe Checkout.
• Email alerts — if you create an alert on /alerts, we store your email, alert type (ticker or filer), the watch value (symbol or person name), confirmation status, and unsubscribe token. Related rows live in Postgres tables alerts, alert_tokens, and alert_deliveries (queued/sent Form 4 match notifications). Nothing is emailed until you confirm via a 24-hour magic link.
• Checkout intents — when you start Stripe Checkout we store the session id (and email if known) so we can send a single abandon reminder if payment never completes. Completed checkouts are marked and are not emailed.
• Billing identifiers — Stripe customer and subscription IDs, subscription status, and current period end, stored so we can deliver Pro access. Card numbers are handled by Stripe, not stored on our servers. Pausing Pro via /billing uses Stripe pause_collection (you keep access while invoices are voided for a limited period).
• Referral codes — Pro members receive a short code tied to their billing email (referrals / referral_redemptions). When someone checks out with that link we record the redemption and may apply Stripe customer-balance credits to both parties.
• IP address — used in-memory for rate limiting API requests. We do not sell IP data and do not use it for advertising profiles.
• A session cookie (insidr_access_email) after a successful Pro checkout so the browser can show unlocked trades.
• Product analytics — we use PostHog (US cloud, us.i.posthog.com by default) to understand how the product is used. The client SDK may set first-party ph_* cookies and records pageviews plus product events (for example checkout started/completed, alert created/confirmed, ticker/person page views, feed return). We do not use this for advertising pixels or sell cookie data to advertisers.
• Local / session storage — after Pro unlock we may store your billing email in localStorage (insidr_access_email) for restore/upgrade UX on that device; a referral code (insidr_referral_code) when you arrive via a Pro invite link; a feed-day key (insidr_feed_day) for return analytics; and short-lived sessionStorage keys for locked-row teaser motion on the feed. These are not used for advertising.

We do not collect biometric data, government ID numbers, precise geolocation, health information, or other sensitive personal information as those terms are commonly used in privacy law.

2. Why we collect it

• Deliver the Service (feed access, Pro unlock, account email).
• Process payments and manage subscriptions via Stripe.
• Send Form 4 email alerts you opted into (after email confirmation).
• Send optional system-status alerts when Insidr flips between operational and degraded (only if you opted in on /status).
• Measure product usage via PostHog so we can improve the Service.
• Send at most one checkout-reminder email if you start Pro Checkout and do not complete it within about 24 hours (stored as a checkout_intents row; we do not keep emailing about the same abandoned session).
• Protect the Service (rate limits, abuse prevention).
• Respond to deletion or support requests.

We do not use personal data to give personalized investment recommendations.

3. We do not sell personal data

We do not sell, rent, or trade your personal information to third parties for money. We share data only as needed to run the Service: Stripe (payments), Resend (transactional email), PostHog (product analytics), Apify (congressional disclosure data fetch on our behalf — public filing data, not your account profile), and Vercel/Neon (hosting and Postgres). Public trade data shown in the product comes from SEC and congressional disclosure sources and is not your personal data.

4. Storage and retention (Postgres / Neon)

Email waitlist, subscription, alert, and related records are stored in Postgres hosted by Neon (via Vercel). We retain personal records as follows:

• Waitlist / free-tier emails (no Pro subscription): until you request deletion, or 24 months of inactivity, whichever comes first.
• Email alerts — until you unsubscribe from that alert, delete your account, or the unconfirmed alert expires (confirm links expire in 24 hours). Delivery history is removed when the parent alert is deleted (database cascade).
• Checkout intents — until the session completes, an abandon reminder is sent or closed (no email / already Pro / cooldown), then retained as needed for abuse prevention and debugging.
• Status-alert emails — until you unsubscribe via the link in each status email, or request deletion.
• Active Pro subscription records: for the life of the subscription.
• Post-cancellation subscription / billing records: for 7 years after cancellation, consistent with common financial record-keeping practice (including typical Australian tax/accounting retention).
• Refund and deletion request logs: kept as needed for legal and dispute-resolution purposes.
• Rate-limit counters: not durable; cleared automatically from in-memory storage.

Cached trade filings are public-market data stored as JSON files (local disk or ephemeral serverless cache), not a profile of you.

When you confirm account deletion (FAQ → email link → confirm), we remove personal records we control for that email: waitlist (subscribers), Pro subscription row (subscriptions) when not blocked by an active plan, status-alert signup (status_subscribers), filing alerts and confirm tokens (alerts / alert_tokens; alert_deliveries cascade), and we clear the Pro access cookie on the confirming browser. We log the request in account_deletion_requests (kept as needed for legal and dispute-resolution purposes). Stripe may retain payment history under its policy. Active Pro must be canceled before deletion succeeds. Self-serve deletion is available on the FAQ.

5. Your rights

You may request access to, correction of, or deletion of personal information we hold about you. Depending on where you live (including Australia and, if applicable, the EU/UK), you may have additional rights. Start with the FAQ self-serve tools, or email support@insidr.so from the address you used with Insidr. We may need to verify the request.

6. Cookies

Essential: the signed Pro access cookie insidr_access_email (httpOnly) so your browser can show unlocked trades after checkout or restore-access.

Analytics: PostHog may set ph_* first-party cookies for distinct visitor identity, pageviews, and the product events described above.

We do not run third-party advertising pixels and do not sell cookie data. We do not currently show a cookie consent banner. You can opt out of analytics by contacting us; the essential Pro access cookie is still required to use paid features. Browser storage used for Pro UX and feed motion is described in §1.

7. International processing

Infrastructure may be located outside your country (including the United States and the European Union, depending on Vercel, Neon, Stripe, Resend, PostHog, and Apify regions). By using the Service you understand your information may be processed in those locations.

8. Contact

Check the FAQ first. Privacy requests: support@insidr.so.