LaCrew

Legal

Privacy

This is a pre-launch placeholder. LaCrew's product stance: the cloud should not hold root keys or custody funds. Session keys are short-lived; revocation is user-driven.

What we intend to collect

  • Account display name and tenant metadata for the hosted control plane
  • Billing identity when Stripe checkout is enabled (F2.10 / F2.15)
  • Operational logs for orchestrator health — not private keys

Analytics

This site measures product usage with Google Analytics 4 — pageviews, and named events for things like which call to action was pressed, how far a page was read, and where the onboarding funnel drops off. GA4 sets a first-party cookie. Advertising storage and ad personalisation are denied outright: the site runs no ads and does not build advertising profiles.

  • Send Do Not Track or Global Privacy Control and analytics is not loaded at all — no script, no cookie, no events.
  • Events carry page paths and short labels. Addresses, hashes, and copied values are deliberately excluded from event payloads.
  • Self-hosted deployments ship without any analytics id configured, and send nothing.

The contact form

A message sent from /contact is delivered as email to the team address for the topic you pick, and a copy goes to the address you gave so you hold a record of what you sent. The form stores nothing else: there is no database row, no marketing list, and no third-party form host between you and the mail.

What we do not hold

  • Human-root seed phrases or passkey private material
  • Custodial control of org treasuries

Contact: privacy@lacrew.xyz · Full policy after legal review (PRD F2.15).