Data retention and deletion
Last updated November 6, 2026
How long Ravensight keeps each kind of data, how to erase one player, what deleting a game removes, and what is kept after a deletion and why. Every period on this page is the one the running service enforces.
How long each kind of data is kept
| Data | Kept for | How it ends |
|---|---|---|
| Raw gameplay events | 90 days by default. A studio owner can choose 180 or 400 days for a game, for a monthly storage charge. | Expire automatically, counted from each event's own time. Expiry is applied as the event store compacts its data, so an expired event can remain for a short while before it is gone. Extending retention never brings back events that have already expired. |
| Daily and monthly aggregates | As long as the game exists. | Deleted with the game. They hold counts, such as active players, sessions and event totals, not individual events. |
| Device registry | As long as the game exists. | One small record per game and device: the device identifier and the first day it was seen, so lifetime and new player counts stay right after events expire. Deleted with the game, or for one device by erasure. |
| Device acquisition records | As long as the game exists. | One record per game and device: the attribution source and the campaign, ad set and creative it came from, so later events can be credited after the first session has expired. A partner's install callback replaces what the SDK reported. Deleted with the game, or for one device by erasure. |
| Experiment assignments | While the experiment runs. | One record per device and experiment naming the variant it was given, so a player keeps the same variant. Deleted when the experiment is stopped or concluded, with the game, or for one device by erasure. Experiment results are computed from events, not from these records. |
| Behavioural segment members | While the device matches a segment that a remote config rule or a running experiment uses. | Device identifiers only, refreshed every hour: a device that stops matching is removed at the next refresh, and every member of a segment that nothing uses any more, including a deleted segment, is removed the same way. Deleted with the game, or for one device by erasure. |
| Test device marks | Until a developer removes the mark. | A device identifier and an optional label, up to 200 per game. Removed from the Event catalogue page, with the game, or for one device by erasure. |
| Network address records | 30 days. A block entry lasts until it expires or the developer removes it. | A keyed hash and a masked form only; the full address is never stored. Removed automatically, and with the game. |
| Player feedback | As long as the game exists. | Deleted with the game. To remove a single message sooner, write to support. |
| Player report messages | Until a developer removes the report, or the game is deleted. | Removed from the dashboard inbox or with the game. |
| Player report images | 90 days. | Expire automatically, or sooner when the report or the game is deleted. Extending event retention does not extend them. |
| AI analyst conversations | 365 days after the last message. | Expire automatically, and are deleted with the game. |
| Detected metric anomalies | 180 days. | Expire automatically, and are deleted with the game. |
| Audit log entries | 180 days. | Expire automatically. |
| Playtest session video and action transcripts (opt-in) | 90 days. | Expired by the storage bucket's own lifecycle rule, so expiry does not depend on any job running. Deleted sooner with the game. |
| Playtest reports, findings and briefs | As long as the game exists. | Deleted with the game. |
| Playtest model metering rows | 13 months (390 days). | Expire automatically. They hold no prompt or completion text. |
| Data export delivery records | 180 days. | Expire automatically. Ravensight never deletes anything from the bucket an export wrote to. |
| Billing and usage records | As long as the account exists. | See "What is kept after a deletion" below. |
Erasing one player
Players should send deletion requests to the developer of the game, who controls their data. To act on one, an owner or admin of the studio calls:
DELETE https://api.ravensight.io/api/v1/games/{gameId}/devices/{deviceId}
For that game only, it removes:
- the device's raw events from the event store, as a background deletion that normally completes within a few minutes;
- the device's entry in the device registry;
- feedback messages and player reports sent from that device, with their report images set to expire at once;
- the device's acquisition record (its campaign, ad set and creative);
- its experiment enrollments, behavioural segment memberships and test-device mark;
- the device's digest in the 30-day network address records.
Aggregates keep their counts, because they hold no per-device data. The audit log entry that records the erasure keeps only a short SHA-256 prefix of the device identifier, never the identifier itself, and expires after 180 days like every other entry.
The SDKs also give players two switches a developer can offer in the game's own settings: a reset call that discards the stored device identifier and starts a fresh random one, and an opt-out call that stops the SDK sending anything. Neither deletes events already stored; those follow the game's retention period or the erasure call above.
Deleting a game
An owner or admin can delete a game from the dashboard. That removes, together:
- the game record, its keys, its play sessions and its traffic records and block list;
- its raw events, as a background deletion in the event store;
- its daily and monthly aggregates and its device registry;
- its device acquisition records, attribution connections and imported ad spend;
- its experiment assignments, behavioural segment members and test device marks;
- its player feedback and player reports, with their images set to expire at once;
- its saved views, dashboards, segments, experiments, remote configuration, monitors and anomalies, digests, analyst conversations and the observations Huginn recorded about it;
- its source scan notes and the stored description of its codebase;
- its Playtest jobs, runs, findings, briefs and stored files;
- its nodes in the journey and studio graph.
The game's identifier is then retired for good, so no other studio can register it and inherit anything addressed to it.
What is kept after a deletion, and why
None of the records below holds raw events or event payloads.
- Monthly usage totals. The account's event count for the month is what billing and the included allowance are measured against. Deleting a game does not reset it, because those events really were received; otherwise deleting and recreating a game would reset a month's bill.
- Wallet and payment records. Top-ups, charges, refunds and the permanent identifier of every paid operation are kept for the life of the account. They are what prevents a charge or a refund from happening twice, and what a refund request is checked against.
- Playtest model metering rows, for their 13 months. The daily reconciliation and the AI provider's invoice are both read against them.
- Studio knowledge that spans games. Design documents, marketing touchpoints and patterns learned across several games stay with the studio. The deleted game's measured lift is removed from each touchpoint, and the game is detached from every pattern; a pattern that cited only that game is removed.
- Sales records, which belong to the title rather than to one game.
- Data export settings and delivery records, as billing history; delivery records expire after 180 days. The export stops with the game, and files it already wrote to your own bucket are yours and are not touched.
- The retired identifier, which holds only the game's identifier and when it was retired.
- Audit log entries, for their 180 days.
Backups
Our database providers keep their own backups. Deleted data can remain in a backup until that backup ages out on the provider's schedule; the current backup schedule is available on request.
Closing an account
To close an account, write to support@realityse.com. Deleting each game first removes its player data straight away. We refund unused prepaid balance on request, as the Terms of Service describe. How Ravensight handles data as a processor for your players is set out in the Data Processing Addendum.