How Rigel Solutions handles your data
Three places data touches our platform — the lead-capture form on the pricing page, Stripe-hosted checkout, and the /contact form. Each is treated the same way: stored encrypted, used only for the purpose described, and never sold or shared with advertisers.
Lead Capture
What we collect when you sign up for the pricing feed
The pricing page gates the live rate card behind a short form so we can deliver the tier comparison to a real human, not a bot. The form asks for:
- Email address — used to send the requested pricing-tier breakdown and, with your consent, the daily micro-purchase opportunity digest.
- Name — salutation on the digest emails and on the personal-sales follow-up a human reviewer sends when the chosen tier warrants it.
- NAICS filter — the small-business category chooser narrows the daily feed to postings your business can actually bid on; the chosen code is stored alongside your account, never sent off-platform.
Stored against the email proxy’s retention window and tied to your account session — never resold, never shared with a third party for advertising.
Stripe-Hosted Checkout
How Stripe handles your card data
Checkout is hosted entirely by Stripe — the billing form, the card-number input, and the 3-D Secure step all render inside Stripe’s domain, not ours. We never see, store, or transmit your card number, CVV, or full card expiry date.
What we doreceive from Stripe is a tokenized reference (the last four digits, the brand, the expiry month/year) and the receipt event — enough to render the billing dashboard and let you cancel or upgrade from inside the app. Stripe’s own privacy policy governs everything inside their checkout frame; refer to it for the full data flow on the payment side.
/contact Submissions
How contact-form messages are stored and delivered
Messages sent through /contact are handled by the contact-form module: each submission is persisted to the app’s own database (your name, your email, the message body, and a timestamp) and the same payload is delivered to the team inbox through the platform’s email proxy.
Submissions are kept for the support window needed to respond and to keep an audit trail for follow-up questions — typically under one year. They are not used for marketing, never shared with a third party, and you can ask us to delete a specific submission at any time by replying to the confirmation thread.
Looking for the legal terms governing the subscription? Read Terms →