Data retention schedule
Retention periods for the hosted service are not set yet. We’ll share them before accounts open.
1.Current public website
The public site is a static presentation and has no account, post, message, or payment database. The production host and its server-side request or security-log retention settings have not been confirmed. The website host receives the request needed to deliver each page. Its records, fields, and retention settings have not been confirmed. We’ll add the host’s data and retention details to the Privacy Notice and this schedule after the live setup is checked.
2.Hosted service retention schedule
No hosted-service retention periods or deletion cycle have been established. “Until no longer needed” is not a useful schedule by itself: the published version will identify a duration or a concrete deletion event, the reason for retaining the record, and any exception. These are possible data categories, not a list of information the hosted service currently collects. We’ll confirm which apply before accounts open.
| Record category | Current status | Details to publish |
|---|---|---|
| Account and profile records | No hosted accounts are available today. | Closure trigger, active-system removal, lawful records retained, and exceptions. |
| Clips, images, comments, messages, and stories | No user content store is available today. | User deletion behavior, copies shared by others, backup expiry, and story behavior. |
| Reports, appeals, copyright, and support records | No in-app report or appeal process is available. | Purpose, authorized access, review period, and end-of-retention event. |
| Security and service logs | Production host and logging settings are unknown. | Provider, fields, access controls, duration, and deletion method. |
| Backups and legal preservation | The hosted service has no confirmed backup schedule yet. | Backup cycle, expiry, restore behavior, hold authority, and release criteria. |
3.How the schedule will work
Each period must be tied to a real purpose, responsible system owner, and applicable legal basis. The schedule will explain when deletion starts, whether data remains in backups until a cycle expires, and how narrowly scoped legal or safety preservation exceptions are handled. A story timer or an account-closure button alone does not prove that every copy has been erased. The operator will distinguish content removal from account closure, active-system deletion, and backup expiry.
Source: Regulation (EU) 2016/679 — General Data Protection Regulation (EUR-Lex) (European Union) · Checked October 8, 2026
Source: Serbian Law on Personal Data Protection — Official Gazette No. 87/2018 (Serbia) · Checked October 8, 2026
4.Deletion checks and exceptions
Before publishing a period, the operator will map where a category is stored, which service providers can access it, and what happens when a user requests deletion. A retention exception should identify its legal or safety reason, restrict who can access the preserved record, and end when the reason no longer applies. No exception should be described as unlimited or routine without evidence and legal review.
5.Review and accountability
The schedule’s responsible contact and review interval have not been confirmed yet. We’ll publish them with the schedule. We’ll check deletion across active systems and backups and update the schedule when providers, features, or storage arrangements change. A verified retention schedule and review date are not available yet. No specific retention period is promised until the schedule is published.