Privacy Policy

Account information: name, email address, company (optional), and a hashed password. We never store your password in plain text.

Usage and billing data: which sandboxes you launch, GPU/provider selections, runtime, and the resulting charges — needed to operate quotas, billing, and the usage dashboards the Service itself shows you.

Pilot-access intake data: if you apply for early access, the workload, pain-point, and GPU-provider answers you submit, along with a verification link (e.g. a GitHub profile) used for pilot-cohort screening.

Abuse-prevention signals:the IP address a request came from, and (with your browser's cooperation) a client-side browser fingerprint — used only to detect one person claiming multiple limited pilot slots under different email addresses. Best-effort: if your browser blocks the fingerprinting script, your submission still goes through.

Secrets:API keys/tokens you optionally store (e.g. for Hugging Face, W&B, GitHub) are encrypted at rest and are never displayed back to you or anyone else after you save them — only injected as environment variables into sandboxes you launch.

We do not access the contents of your compute workloads (your code, models, or data running inside a sandbox) except as needed to operate the Service, to investigate a suspected Terms violation, or as required by law — see the Terms of Service, Section 5.

• To provide, maintain, and bill for the Service;
• To communicate with you about your account, including verification codes and support requests;
• To screen pilot-access applications against a limited cohort;
• To detect and prevent abuse of limited pilot slots or free quota;
• To improve the Service (e.g. understanding which features are used).

Compute Providers(e.g. RunPod, Vast.ai, Lambda Cloud, Shadeform, AWS): only what's needed to provision a sandbox you requested — never your account password or stored secrets beyond what you've explicitly configured to inject into that launch.

Payment processing: billing is handled by a third-party payment processor (Stripe); NuovoForte does not store your raw card number.

Service providers who help us operate the platform (e.g. email delivery, hosting), bound by confidentiality obligations.

We do not sell your personal information.

We retain account and billing data for as long as your account is active, and as needed to comply with legal, tax, or accounting obligations after that. Pilot-access intake data for an application that never converts to an account is retained for a limited period for cohort-integrity purposes, then deleted or anonymized.

You can review and update your account information from within the Service, and can request account deletion or a copy of your data by contacting support@nuovoforte.com. Depending on where you live, you may have additional rights (e.g. under GDPR or CCPA) to access, correct, or delete your personal information, or to object to certain processing.

We use essential cookies/local storage to keep you signed in, and a client-side browser-fingerprinting library (FingerprintJS, open-source, no external network calls) solely for pilot-slot abuse prevention during signup. We do not use third-party advertising trackers.

We may update this Privacy Policy from time to time. Material changes will be reflected in a new version (shown above) and, where practical, notified to active accounts.

Questions about this Privacy Policy: support@nuovoforte.com