SIDUS PRIVACY

Privacy notice

This notice explains how SIDUS handles personal information when you visit our public website, request a demo, or communicate with us about SIDUS.

Last updated August 3, 2026

Scope

This notice covers SIDUS public website visitors and people who submit or discuss a demo request. An organization using an authenticated SIDUS workspace may also be governed by its customer agreement and workspace-specific notices.

Information we collect

When you request a demo, we collect your name, work email, role, company, location-count range, and the operational challenge you describe.

We also record limited context needed to operate and protect the request experience.

  • Entry page, referring site, campaign parameters, and the presentation variant when available.
  • Your demo-follow-up purpose, privacy-notice evidence, and optional marketing choice.
  • Limited browser, timing, and network-derived abuse signals. Long-lived prospect records do not store a raw network address.
  • Messages and request details you later exchange with the SIDUS team.

How we use information

We use this information to:

  • Review your request, contact you, and arrange a relevant demo.
  • Maintain an accurate record of your request, consent choices, and follow-up status.
  • Protect the form, investigate abuse, and keep the public service reliable.
  • Understand which first-party entry paths and campaigns lead to relevant requests.
  • Meet legal obligations and enforce the security of SIDUS systems.

Demo follow-up and marketing

Requesting a demo allows SIDUS to respond to that request. It does not subscribe you to ongoing product marketing.

The marketing checkbox is separate and off by default. If you select it, SIDUS records that choice independently. You may withdraw that choice in later correspondence without affecting the original demo request.

Cookies and tracking

The public website and demo-request page do not require an SIDUS account, an application session cookie, or a tracking cookie. The demo request can be accepted without advertising cookies.

Authenticated workspace pages use a necessary session cookie to keep a signed-in user within the correct access boundary. Transactional demo receipts have open and click tracking disabled unless a later, separately approved notice says otherwise.

Service providers and disclosure

Accepted demo requests are stored as SIDUS-owned records. SIDUS may use configured providers for hosting, database services, transactional email, abuse prevention, and a limited customer-relationship-system copy.

Provider availability does not determine whether SIDUS accepts a request, and provider records do not replace the SIDUS record. We limit provider access to the information needed for the configured service. SIDUS does not sell demo-request personal information.

Retention and deletion

Unless a different period is required by law or agreed with you, SIDUS targets a maximum retention period of 12 months for personal information from an unconverted demo request or prospect.

Challenge evidence is retained for up to 24 hours and minimized abuse evidence for up to 30 days. When personal information is deleted, SIDUS may retain de-identified consent, decision, and delivery evidence needed to show what occurred without retaining the original personal content.

Security

SIDUS uses access controls, scoped service identities, separated provider credentials, bounded public-write controls, and redacted operational evidence to protect request information. No internet service can guarantee absolute security, but provider failure is isolated from the authoritative request record and does not silently overwrite it.

Your choices and requests

You may ask SIDUS to explain, correct, or delete demo-request information, or withdraw an optional marketing choice. Depending on where you live, local law may provide additional access, objection, restriction, portability, or complaint rights.

Use the monitored support address included in your request receipt or subsequent SIDUS correspondence. Include your opaque receipt reference when available; do not send passwords, API keys, or unrelated sensitive information.

Changes to this notice

SIDUS may update this notice as the public experience, providers, or legal requirements change. The page will show a revised last-updated date. Each accepted demo request separately records the internal notice version presented with that request so later wording changes do not erase the original evidence.