Privacy Policy
Last updated: September 4, 2026
1. Scope
This Privacy Policy describes how Gutschow LLC (“Gutschow,” “we,” “us,” or “our”) handles information when you:
- Visit gutschow.xyz and related marketing pages (including Webflow-hosted forms);
- Use docs.gutschow.xyz, sandbox.gutschow.xyz, api.gutschow.xyz, or dashboard.gutschow.xyz;
- Subscribe to updates, request sandbox or production access, or otherwise communicate with us; or
- Access our B2B clearing, settlement, and treasury automation software (collectively, the “Services”).
2. Who we are
Gutschow LLC
Princeton, New Jersey, United States
Privacy inquiries: info@gutschow.xyz
3. Information we collect
Depending on how you interact with us, we may collect:
| Category | Examples | Typical source |
|---|---|---|
| Business contact data | Name, work email, company, job function, inquiry topic, message content | Contact form, sandbox signup, email |
| Account & authentication data | API key identifiers (gsk_sandbox_… / gsk_live_…), organization IDs, operator email (via Cloudflare Access), configuration metadata | Onboarding, dashboard sign-in |
| Transaction & compliance metadata | Settlement payloads, wallet IDs, corridor, counterparty fields, Travel Rule / KYB attributes, sanctions screening inputs, status transitions, webhook delivery logs | API ingest, compliance gates |
| Technical telemetry | IP address, user agent, timestamps, request IDs, rate-limit counters, error diagnostics | Edge proxy, API gateway, ops monitoring |
We do not intentionally collect sensitive categories (e.g., government ID images) through the public marketing site. KYB documentation for production onboarding may include additional materials submitted through secure channels agreed during onboarding.
Blind Ingress Privacy: Where enabled, sensitive ingress fields may be redacted or processed in short-lived memory enclaves before persistence. This is operational privacy engineering — not zero-knowledge cryptography.
4. How we use information
We use information to:
- Provide, operate, secure, and improve the Services;
- Authenticate API and operator access and enforce tenant isolation;
- Run compliance screening (sanctions, velocity limits, Travel Rule metadata validation) and fraud prevention;
- Reconcile ledgers, investigate incidents, and maintain immutable audit trails;
- Respond to sales, support, and onboarding requests;
- Send product updates you have opted into;
- Comply with law, regulatory requests, and contractual obligations.
5. Legal bases (EEA / UK visitors and Customers)
Where GDPR or UK GDPR applies, we rely on: contract performance (providing the Services); legal obligation (financial-crime and sanctions compliance); legitimate interests (securing infrastructure, preventing abuse, improving B2B products); and consent where required (e.g., optional marketing cookies or newsletters).