Privacy Policy
Effective
About gerberize
gerberize is operated by Sovereign ATX LLC in Austin, Texas. It provides CLI, MCP, and API tools for PCB validation, simulation, manufacturing exports, and guarded sandbox ordering. This policy describes the current hosted website and service. Contact: kavinlingham1@gmail.com.
Information the service handles
| Information | What it is used for |
|---|---|
| Google sign-in information | Google supplies identity and profile claims when you sign in. gerberize uses your Google account identifier, verified email address, and name to create or identify your account and initialize its display name. The application does not store or display your Google profile picture. |
| Account information | Account ID, email, display name, preferences such as time zone, administrator status, any account-specific cloud allowance, creation time, and deactivation status support your workspace and account settings. |
| Authentication and security records | Browser-session and API-key hashes, key names and prefixes, access scopes, creation/expiry/revocation records, browser user-agent information, and session activity times support sign-in and access control. Temporary OAuth transaction and CLI device-authorization records verify sign-in requests. Request-derived rate-limit identifiers and counts help control abuse. |
| Project and job information | Project names, uploaded file names and contents, file checksums and sizes, job options, validation/simulation results, status, and timestamps allow the service to run and retrieve your requested work. |
| Ordering information | Saved quotes, spending limits, approvals, order identifiers, amounts, test payment references, provider status, tracking information when supplied, and event history support sandbox ordering and spending controls. |
| Subscription information | Stripe customer, subscription, price, and Checkout identifiers; Checkout retry information; subscription status and billing periods; and processed webhook identifiers support billing and cloud-job allowances. Invoice details and links are retrieved from Stripe for your workspace. |
| Waitlist and correspondence | A submitted waitlist email and timestamp are saved for the signup list. If you contact us, your email address and message are handled through the support mailbox. The current application does not send waitlist or invoice emails. |
The backend stores uploaded files and results in its database. Workers read those files into temporary work directories to execute the requested native tools. Locally executed CLI checks do not require a hosted account or upload; cloud commands upload their inputs. An MCP client or AI agent you configure can separately handle files and command results under that provider's practices.
The application does not persist Google access, refresh, or ID tokens. Existing accounts are not merged based only on a matching email: linking a Google identity to an existing account requires owner authorization.
Services that handle information
- Google processes the Google sign-in flow and provides the identity information described above.
- Website hosting and network services deliver the site and route API traffic. The current deployment uses Vercel and Tailscale routing to an operator-managed backend, database, and native worker. Those services handle network requests and associated technical information under their own practices. Request delivery and operational logging are distinct from the account records listed above.
- Stripe, when test billing is configured and used, receives an internal gerberize user ID as customer/subscription metadata and the price, customer, and transaction information needed for the requested billing operation. The application does not send the account email when it creates a Stripe customer. Information you enter on Stripe-hosted Checkout or billing pages is provided directly to Stripe. gerberize does not store card numbers. Current billing accepts Stripe test mode only.
- Fabrication providers, if an implemented external sandbox adapter is configured and you request it, receive the supported quote or status request parameters. The built-in sandbox provider runs locally without contacting a manufacturer. Live fabrication checkout is disabled; several external adapters remain unavailable. Consult the integration status before selecting a provider.
- Support email services handle messages you choose to send to the contact address above.
These descriptions cover implemented service flows. They are not a statement that third-party services follow gerberize's storage or retention practices.
Your controls and retained information
In the workspace, you can update your display name and time zone, revoke agent keys, revoke individual browser sessions, or sign out all browser sessions. Signing out browser sessions does not revoke agent keys. You can also manage gerberize's Google connection from your Google Account; doing that is separate from revoking existing gerberize sessions or deactivating this account.
Account settings provide a JSON export of account and workspace records, including uploaded files and available subscription metadata. Authentication secrets are excluded. Interactive exports have size limits; contact us if an export is too large.
Deactivation disables access; it is not data deletion. It revokes browser sessions, API keys, device authorizations, and outstanding approval access. Deactivation is blocked while a subscription or Checkout requires resolution, while jobs are queued or running, or while orders remain outstanding. Account, project, file, job, order, and billing records remain stored after deactivation, and database backups can also contain them. The current service does not automatically erase those records after a fixed period.
Contact kavinlingham1@gmail.com with an access, correction, or deletion request, including the account email and the information involved. Deletion is not currently self-service and requires operator review. Do not send passwords, API keys, or payment card numbers with a request.