Last updated: November 8, 2026

Privacy Policy

This Privacy Policy describes how FairForge LLC, the controller ("Stored", a product of FairForge; "we", "us"), collects, uses, and protects your personal data when you use our S3-compatible object storage service at stored.cloud (also served at stored.ge and stored.pics).

Contents

• Lawful Basis for Processing
• Data Categories
• Retention Periods
• Data Subject Rights
• Sub-processors
• International Transfers
• Security Measures
• Changes to This Policy
• Contact

Lawful Basis for Processing

We process your personal data under the following lawful bases as defined by the General Data Protection Regulation (GDPR):

• Performance of a contract, processing necessary to provide the storage service you signed up for, including account management, billing, and service delivery.
• Legitimate interest, processing necessary for service security, fraud prevention, abuse detection, and service improvement, where these interests are not overridden by your rights.

Data Categories

We collect and process the following categories of personal data:

• Account data, email address, company name, hashed password, account creation date, email verification status.
• Usage data, storage consumption, bandwidth usage, API request counts, bucket and object metadata (names, sizes, content types, ETags). We do not read or analyse the content of your stored objects; our engine handles object bytes only to store them (chunking, deduplication, compression) and returns them unchanged.
• Billing data, subscription plan, payment method (processed by Stripe; we do not store card numbers), invoice history, Stripe customer ID.
• Session data, IP address, user agent, session creation and last-active timestamps, used for active session management and security.
• Site statistics, cookieless daily totals for the public pages (stored.cloud, docs, changelog, legal pages): page viewed, referring site (host only), campaign labels in the link you followed, country (from our CDN), device class (phone/tablet/desktop), and named interactions on the landing page such as opening the pricing section. No identifier is stored. To count distinct visitors per day we hash the IP address and user agent with a secret that changes every day and is never written anywhere; the hashes are deleted after two days and only the daily count is kept. The one third-party measurement is Cloudflare Web Analytics, a cookieless beacon our edge provider injects on the public pages: it reports the page URL, the referrer and page-load timing to Cloudflare, sets no cookie, uses no fingerprint and builds no profile; nothing else of yours is sent to any analytics service.

Important: We never read, analyze or profile the content of objects you store in our service. Object content is encrypted in transit (TLS) and treated as opaque data.

Retention Periods

• Account data, retained for the lifetime of your account. A deletion request starts a 30-day grace period during which you can cancel; on the date the account is closed, the subscription is cancelled and our deletion job erases your objects, keys and account records (see the Terms); database backups age out within 30 days of the erasure. Large objects are stored in deduplicated blocks: the blocks of your objects are released on that date and deleted by the storage collector once its seven-day safety period has passed, except a block that is byte-for-byte identical to one another customer stores, which remains as that customer's data.
• Session records, expire 24 hours after sign-in and are purged hourly. S3 access logs, retained 30 days, then automatically purged (request-level logs are only kept for buckets whose owner has enabled server access logging; error records are kept for every bucket for support, for the same 30 days). Developer request records (each S3 request's access key id, operation, bucket, object name, status, error code and request id; no IP address, no user agent, no content), kept for every account so you can find a request on the dashboard's Developers page, retained 7 days, then automatically purged. API/dashboard event logs, quota usage events and payment-provider event records, retained 90 days, then automatically purged. Public-link (CDN) access logs, aggregated into daily counts and the raw entries purged after 2 days. Webhook delivery records, retained 30 days. Agent connection records (an AI agent's registration with our sign-in service: its name and return addresses; and the one-time codes of a connection you approve), a registration deleted once no one has used it for 30 days and no live connection names it, the internet address it was registered from blanked after 2 days (it limits how many registrations one network may make a day), a code 24 hours after it was made. Invitations to an account's team or family (the invited e-mail address), deleted 30 days after they were accepted or expired; an invitation naming you is deleted with your account. Sign-in and administrative audit records, retained for the life of the service as our security record; your own entries are removed with your account. Waitlist sign-up IP address and user agent, removed 90 days after sign-up (the address itself is kept until launch or your request; the sign-up's country code is kept with it). Site statistics, daily totals are kept indefinitely; the visitor hashes behind the daily unique count are deleted after 2 days. Data exports, the file produced by a data-export request is kept for 7 days, then automatically deleted; the record that an export was requested stays with the account.
• Billing records, retained for 7 years to comply with financial reporting and tax obligations. Our payment ledger (each payment's amount, the period and storage it bought, and our receipt number) is not purged automatically: it is our accounting record. When your account is erased, its entries keep no link to you, and any cryptocurrency address, transaction id or note on them is removed.
• Object metadata, deleted when you delete the corresponding object (version records on versioning-enabled buckets remain until the bucket is deleted), and with the account records after account deletion.

Data Subject Rights

Under the GDPR, you have the following rights regarding your personal data:

• Right of access, request a copy of all personal data we hold about you.
• Right to data portability, receive your data in a structured, machine-readable format: a JSON export requested from the account settings page or the management API, prepared within minutes and downloadable for 7 days.
• Right to erasure, request deletion of your account and all associated personal data, subject to a 30-day grace period.
• Right to rectification, correct inaccurate personal data (e.g., update your email or company name via account settings).
• Right to restrict processing, request that we limit how we use your data while a dispute is resolved.
• Right to object, object to processing based on legitimate interest.

To exercise any of these rights, contact us at privacy@stored.cloud. We will respond within 30 days.

Sub-processors

We use the following third-party sub-processors to deliver our service:

• iDrive Inc. (United States; EU regions on request), object storage for Standard-tier objects in a region you choose other than the default, and a second copy of default-region objects, in the United States, when one is kept.
• Seagate Technology (Lyve Cloud) (United States), object storage for Standard-tier objects in the default region (in Virginia), for the resilient tier and as a failover leg, and the parity second copy of Vault-tier objects.
• Geyser Data Inc. (United States, Los Angeles), tape archive for Vault-tier objects (GLACIER / DEEP_ARCHIVE), whatever the bucket's region.
• Cloudflare Inc. (global edge), CDN, DDoS protection, TLS termination and the cookieless Web Analytics beacon on the public pages; the bytes of an upload to the S3 endpoint s3.stored.cloud pass through its edge in transit to the storage backend (never stored there); Cloudflare R2 holds the objects of public-read buckets served on cdn.stored.cloud, and the point-in-time archive of our database, encrypted on our server before it leaves it.
• Microsoft Corporation (United States), cloud storage infrastructure: internal parity copies of objects, when enabled.
• Sync.com Inc. (Canada), the encrypted off-site copy of our database backups, and a standby location for the parity copies of Vault-tier objects.
• Blomp (United States), a second encrypted off-site copy of our database backups.
• Stripe Inc. (United States), payment processing and subscription management.
• Resend Inc. (United States), transactional e-mail, when enabled.
• Google LLC / GitHub Inc. (United States), sign-in with Google or GitHub, only if you choose it (we receive your verified e-mail address).

Each sub-processor is bound by a Data Processing Agreement that requires GDPR-equivalent protections.

International Transfers

Your data may be transferred to and processed in the United States. We ensure adequate protection for international transfers through:

• Standard Contractual Clauses (SCCs) approved by the European Commission.
• Sub-processor agreements that incorporate GDPR-equivalent data protection terms.

Security Measures

• All data in transit is protected by TLS 1.2 or higher; HSTS is enforced at our edge.
• Passwords are hashed using bcrypt (cost factor 10, the Go library default).
• Sessions use cryptographically random tokens with HttpOnly, Secure, and SameSite cookies.
• Two-factor authentication (TOTP) is available for all accounts.
• Access to production systems is restricted to authorized personnel with SSH key authentication.

Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated via email to registered users at least 30 days before they take effect. The "Last updated" date at the top of this page reflects the most recent revision.

Contact

For privacy-related inquiries, data subject requests, or complaints:

• Email: privacy@stored.cloud
• Entity: FairForge LLC
• Jurisdiction: State of Utah, United States