Terms placeholder without unsupported claims.
These pages describe the intended product policy surface while formal legal, security, vendor, and Enterprise reviews are still gated by the operational readiness register.
- Reviewed by
- GetFileURL technical team
- Last updated
What this page answers
Current GetFileURL terms placeholder covering acceptable use, file URL lifecycle, API use, support targets, and unsupported legal claims.
Use this page when the workflow needs file bytes available at a direct URL with predictable metadata, lifecycle controls, and a cleanup path.
Updated
GetFileURL provides controlled file URL infrastructure.
Users are responsible for the files they upload, the systems they connect, the retention settings they choose, and the downstream use of returned URLs.
API credentials
API keys must stay in trusted runtimes and should be scoped to the minimum required capability.
Lifecycle
Expiry, deletion, signed delivery, scanner state, and webhook events are part of the file URL contract.
Availability
Public status and incident evidence exist, but contractual uptime claims require Enterprise terms.
Some commercial terms are deliberately deferred.
Billing is placeholder-only for now. Upgrade intent can be captured, but no payment, invoice, tax, refund, or subscription claims should be made until Stripe is integrated.
Plans
Plan keys and entitlements exist in the control plane for product behavior.
Payment
No real checkout or invoice flow is active in this placeholder state.
Enterprise
Enterprise terms require custom review for SLA, residency, DPA, subprocessors, and support targets.
Answers before the workflow breaks
Are paid terms live?
No. Billing remains a visible placeholder until the payment system is implemented.
Can I rely on an SLA?
Only after an Enterprise contract explicitly grants one.
Can I use GetFileURL for illegal or abusive files?
No. The acceptable use placeholder and abuse workflow apply.