Privacy
Privacy policy
What Deltaship collects, why, where it is kept and for how long. Draft of 22 October 2026.
Draft, pending legal review; not yet in effect.
This text describes how Deltaship works today. Items marked [OWNER: ...] are choices the owner still has to make.
Who this covers
Deltaship is operated by [OWNER: legal entity name, registered address and country] ("Deltaship", "we"). This policy covers the deltaship.dev website, the Studio dashboard, the player portal and the launcher services that studios use to distribute their games.
There are two kinds of people whose data we handle:
- Studios and their staff, who sign up for Deltaship. For this data Deltaship decides why and how it is used (we are the controller).
- Players, who use a studio's launcher or portal. The studio decides who its players are and why they sign in; Deltaship stores and processes that data on the studio's behalf (we are the processor). A player's questions about their data should go to the studio first.
What we collect and why
| Whose | What | Why |
|---|---|---|
| Studio staff | Email address, a salted password hash (never the password), whether the email is verified, role in each studio, sign-in sessions, studio name and web address. | To run accounts, sign you in and enforce who may do what. |
| Studio content | Games, release files, news and patch notes, launcher design (colors, logo, background art, links), team invitations. | To store and deliver what the studio publishes. |
| Players | Email address, a salted password hash, status (invited, active, disabled) and whether the email is verified, per studio; launcher sign-in tokens and portal sessions. The same email at two studios is two separate records. | So a studio can limit its launcher to its own players, and so players can sign in. |
| Download and install statistics | For each download: studio, game, release, channel and bytes served. For install events: installs, updates and repairs, with release, platform and version. No player identifier is recorded. | To show studios how their releases are doing and to measure fair use. |
| Security records | Counters of sign-in and request attempts per network address and account, kept briefly to stop abuse; an audit log of important actions in a studio (who, what, when); short, logged sessions when Deltaship staff help with a studio. | To protect accounts and investigate problems. |
| Billing | Plan, subscription state and payment-provider reference numbers. Card and payment details are handled by Paddle and never reach Deltaship. | To charge for plans and apply limits. |
| Messages we send (verification, invitations, password resets, billing and inactivity notices) and a log that records one send per event and recipient. | To run the service and avoid duplicate emails. |
The deltaship.dev website uses no analytics, advertising or tracking scripts, sets no cookies, loads its fonts from its own servers and makes no requests to third parties.
We do not sell personal data.
Cookies
| Cookie | Where | Purpose and lifetime |
|---|---|---|
| __Host-udtk_s | Studio dashboard | Keeps a studio member signed in. Strictly necessary, HttpOnly and Secure; expires after 30 days without use. |
| udtk_p | A studio's player portal | Keeps a player signed in to that portal only. Strictly necessary, HttpOnly and Secure, limited to that portal's path. |
| __Host-udtk_i | Dashboard, during staff help | Marks a short, logged support session opened by Deltaship staff; ends after 30 minutes. |
These are all strictly necessary, so no cookie banner is needed for them. A development-only variant of the session cookie exists for testing on a local computer and is never used in production. There are no advertising or third-party cookies.
Where data is kept and who processes it
Deltaship runs on Cloudflare: application servers, database, file storage, delivery and download statistics. Studios may instead serve their game files from their own storage account; those files then sit with the studio's chosen provider under the studio's own agreement with it.
| Provider | What it does for Deltaship | Data involved |
|---|---|---|
| Cloudflare, Inc. | Hosting, database, file storage, delivery and statistics; bot checks on sign-up forms where enabled. | All data described above. |
| Paddle | Merchant of record: takes payment, calculates tax, issues invoices. It is an independent controller of payment data under its own privacy terms. | Studio billing contact and payment details. |
| Email provider | Sends the emails listed above. | Recipient address and message content. |
[OWNER: name the email provider and link its data processing terms] [OWNER: data location and region, and the legal basis for any transfer outside the studio's country] [OWNER: add or remove subprocessors before this policy takes effect]
How long we keep data
- Dashboard sessions end after 30 days without use. Invitation links last 7 days, password reset links 1 hour and email verification links 24 hours, and each works once.
- Attempt counters for abuse prevention are deleted daily once their time window has passed.
- Free studios that go quiet are handled by an inactivity rule: warnings by email at 60 and 75 days, downloads paused at 90 days and the studio's release files deleted at 120 days. Signing in, uploading, a player download or upgrading resets the clock. Account records are not removed by this rule.
- If a payment fails, a studio becomes read-only after 14 days and moves to the Free plan after 44 days. Its data is not deleted for this reason.
- Statistics are kept as aggregate data points in Cloudflare's analytics service.
[OWNER: audit log retention period] [OWNER: statistics retention period; confirm Cloudflare's setting] [OWNER: how long account, player and billing records are kept after a studio asks for deletion or closes, and any records kept by law]
How we protect it
- All traffic uses HTTPS.
- Passwords are stored only as salted hashes. Sign-in tokens are stored only as hashes.
- A studio's access is separated from other studios in every request, and a role change applies immediately.
- Storage keys that studios give us for their own bucket are encrypted, and are never shown again after saving.
- Releases are signed so launchers can check they are genuine before installing.
Your rights
Depending on where you live, you may ask to see, correct, export or delete your personal data, to object to or restrict how it is used, and to complain to a data protection authority. If you are a player, ask the studio first; if you ask us, we will pass the request to the studio or help it answer. If you are studio staff, write to privacy@deltaship.dev [OWNER: confirm the privacy contact and, if required, the data protection officer or representative].
[OWNER: laws that apply (for example GDPR, UK GDPR, UAE or Egyptian data protection law) and the legal bases relied on]
Children
Deltaship is for studios and is not aimed at children. A studio that distributes a game to children is responsible for getting any permission the law requires. [OWNER: minimum age for studio accounts]