Privacy Policy

Scope of this policy

This policy applies to the public Solurnis website, preview and audit intake forms, the private client portal, checkout flows launched from Solurnis, account access and recovery flows, and direct support follow-up tied to those services.

Solurnis operates the site and can be reached at [email protected] for privacy questions, access requests, correction requests, or deletion requests.

Information Solurnis collects

Preview requests

• Name, email address, optional phone number, business name, city or service area, website URL, website status, and the preview goal or improvement request.
• Request metadata such as source page, campaign value, status updates, and anti-spam honeypot fields.
• Preview-processing identifiers returned by Site Screener when a request is routed into that workflow.

Audit requests

• Business name, contact name if provided, email address, main need, scope/problem summary, timeline, city or service area, and website URL or no-site status.
• Request metadata such as source page, request status, relay status, and anti-spam honeypot fields.
• If the requester asks Solurnis to review and identify the issues, that choice is stored with the request.

Support and account access records

• Emails or support requests sent directly to Solurnis, plus any project notes or follow-up records needed to respond.
• Client account records tied to portal access, including sign-in or recovery-link requests, password setup or change events, optional federated sign-in when enabled, email-change requests, and account settings updates.
• Card and access-security records such as referral or recovery codes, replacement card issuance, trusted-device or session security events, revocation events, and related timestamps.

Client portal and project records

• Client name, client email, preview title, preview path, approved feature selections, account-linked access records, and project notes used to run the portal.
• Private preview, report, and delivery records used to present the assigned workspace, checkout selections, and ongoing support context.

Billing and checkout metadata

• Checkout email, selected item identifiers, Stripe checkout session identifiers, Stripe customer identifiers, subscription identifiers, invoice identifiers, and payment status metadata.
• Solurnis does not receive or store full payment card numbers. Card payments are handled on Stripe-hosted checkout pages.

Technical and security data

• Essential cookies and similar technologies needed to keep the client portal secure, maintain signed-in sessions, remember the current preview or recovery context on the same browser, and prevent abuse.
• Standard hosting, delivery, security, and request logs created by infrastructure and security providers used to run the site.

How Solurnis uses information

• To review preview and audit requests, respond to inquiries, and send the right next step.
• To prepare previews, scopes, quotes, portals, support follow-up, and project delivery.
• To create and manage private client portal access, card or referral access, account recovery, password updates, and approved checkout options.
• To process billing, recurring service setup, invoices, receipts, and post-checkout support using hosted payment providers.
• To prepare previews, reports, demos, websites, automation recommendations, or scoped AI-assisted work when a client or prospect asks for those services.
• To prevent abuse, keep the site secure, troubleshoot problems, and maintain service records.

When Solurnis shares information

Solurnis does not sell personal information. Solurnis may disclose information to service providers that operate the workflow, including:

• Payment and billing providers for hosted checkout, invoices, subscriptions, receipts, and payment-status data.
• Authentication, database, and portal providers for private client logins, account recovery, and portal data storage.
• Preview, concept, and reporting providers for preview intake routing, website concepts, and business-review workflows tied to a request.
• Email delivery and mailbox providers for support notifications, account access links, recovery emails, and ongoing project communication.
• Hosting, CDN, DNS, and security providers for site delivery, abuse prevention, logging, and infrastructure operations.
• Service-specific AI providers only when a client engagement or demo actually includes automation, reports, voice, or AI-assisted workflow work. Ordinary website visitors are not automatically routed into those tools just for visiting the site.
• Professional advisers or authorities when reasonably necessary to enforce rights, comply with law, prevent fraud, or respond to a valid legal process.

Cookies and similar technologies

Solurnis uses cookies and similar technologies that are necessary to run the site, maintain secure client portal access, remember the current preview or recovery flow on the same browser, and protect account and card-access security.

This public page does not publish internal cookie names, internal security identifiers, or other internal implementation details. Solurnis also stores related server-side security records so lost-card, revoke, or reissue requests can be handled without exposing raw security values in the browser.

As of the last update on this page, Solurnis is not using advertising pixels or cross-site behavioral tracking cookies on the public site. If that changes, this policy should be updated before those tools go live.

Some browsers offer a “Do Not Track” setting. Because Solurnis does not currently run cross-context behavioral advertising on the public site, Solurnis does not use a separate Do Not Track response model at this time.

How long Solurnis keeps information

• Preview and audit request records are generally kept long enough to review the request, follow up, support future scoping, and maintain a business record of the interaction.
• Client portal, invite, and project-access records are generally kept for the duration of the project or support relationship and for a reasonable period afterward to support follow-up, billing, and recordkeeping.
• Billing and transaction metadata may be kept longer when needed for accounting, tax, fraud prevention, or dispute handling.
• Infrastructure and security logs are retained according to provider limits and operational needs.

Security and handling standards

Solurnis uses a mix of hosted providers, access controls, account-verification steps, session safeguards, provider-managed authentication, and operational security practices intended to protect business and contact information. No internet-facing system can be guaranteed perfectly secure, so Solurnis cannot promise absolute security.

California and US privacy requests

California residents and other US-based requesters may email [email protected] to request access, correction, or deletion of information Solurnis controls, subject to lawful exceptions and the need to verify the requester.

• Solurnis does not sell personal information.
• Solurnis does not knowingly share personal information for cross-context behavioral advertising.
• Solurnis will not discriminate against someone for making a good-faith privacy request.

Children’s privacy

Solurnis is built for business and professional service inquiries. It is not directed to children under 13, and Solurnis does not knowingly collect personal information from children through this site.

Changes and contact

Solurnis may update this policy as the preview, audit, portal, account, payment, reporting, demo, or automation workflows change. Material updates should be reflected on this page with a new last-updated date.

Privacy questions, correction requests, deletion requests, and notice requests can be sent to [email protected].