TruStacks

Trust

How we handle your data.

What we collect, where it lives, who can see it. The marketing site is intentionally minimal in its data footprint; the product is where customer state actually lives.

  1. 01

    The marketing site holds essentially no customer data.

    trustacks.com has no accounts, no logins, no preferences, no personalization. The only inbound data path is the contact form on /contact, and even then only the fields you choose to type.

  2. 02

    Where the form data goes.

    Contact-form submissions go through a Next.js Server Action over HTTPS, get validated server-side (length bounds, email format, honeypot for bots), and are forwarded by email to a TruStacks-controlled inbox. The forwarding provider will be listed on the privacy notice once selected. Server logs capture only non-PII metadata — whether fields are present and the length of the message — so names and emails do not enter the log stream.

  3. 03

    Where the marketing site runs.

    Vercel hosts the site (US-based, SOC 2 Type II and ISO 27001 certified). Most pages are statically prerendered, so a typical page view does not touch any database. The only runtime path is the contact form’s Server Action.

  4. 04

    Analytics.

    Vercel Analytics — cookieless, IP-free, privacy-respecting, aggregate-only. No third-party trackers, ad networks, session recorders, or fingerprinting tools have been wired up. We will surface any change to that posture on the privacy notice before it ships.

  5. 05

    Customer state lives in the product, not here.

    The TruStacks product UI runs at app.trustacks.com and is governed by a separate trust posture. Production credentials never live on the marketing side; never live on TruStacks-operated infrastructure at all. See /product/security for the supply-chain story.

  6. 06

    Verify yourself.

    Every TruStacks artifact — runner image, policy bundle — is cosign-signed against a publicly verifiable key. Nothing about our supply chain depends on you trusting our copy. The verification command is the same one you would run yourself; see /product/security.

Questions about how a specific piece of data flows?

We will not be vague. Send us the question and we will answer with specifics — repos, services, retention windows, and who has access.

Talk to salesRead the privacy notice