Tento dokument je momentálně dostupný pouze v anglickém originále. Přepněte prosím jazyk pomocí tlačítka vpravo nahoře, nebo si přečtěte anglickou verzi níže.
Strimeta Data Retention and Deletion Policy
Product: Strimeta
Operator / Provider: Jakub Marcinka, trading under jmarcinka.cz
IČO: 21474672
Business address: Na Kopci 1210/10, 460 14 Liberec XIV-Ruprechtice, Czech Republic
Contact: jmarcinka@email.cz
Website: https://jmarcinka.cz
Version: 1.0
Effective date: 9 September 2026
Status. This is Strimeta's operational legal documentation prepared for launch. Mandatory law prevails over contractual text. Because international privacy, tax, consumer and platform rules change, the regional launch gates and vendor list must be re-checked before entering a new market or materially changing the product.
1. Principle
Strimeta retains identifiable data only for a documented operational, contractual, security or legal need. Retention is measured by data category rather than indefinite account-wide storage.
2. Default operational periods
Unless a Customer selects a shorter supported period or law requires otherwise:
- raw/event-level community metadata: 90 days;
- derived community/cohort metrics that remain identifiable: 13 months maximum;
- de-identified aggregate statistics that cannot reasonably be linked back to individuals: may be retained longer for trend/capacity purposes;
- application/security logs containing personal data: 180 days unless a security investigation requires a legal hold;
- closed support cases: 24 months unless a shorter period is sufficient;
- inactive account profile data: deleted or anonymised within 90 days after termination after the exit period, except legal/accounting records;
- billing/accounting/tax records: retained for the statutory period required of the Provider in the Czech Republic or another applicable jurisdiction.
3. Backups
Strimeta may maintain daily, weekly, monthly and quarterly recovery points across Contabo, the Provider's workstation and NAS. Customer/community personal data must not intentionally remain recoverable in the operational backup chain for more than 90 days after deletion from active systems. Longer-term quarterly archives, if kept, must be limited to non-customer system configuration, de-identified material or records that Strimeta is legally required to preserve.
Backups are encrypted and are not searched or restored for ordinary product use. If a disaster restore reintroduces records previously scheduled for deletion, the deletion queue/instructions are re-applied.
4. Termination
Customer receives a reasonable export/exit window. After that window, Customer Data is removed from active production according to the deletion workflow. Account/billing records required for tax, fraud, sanctions, dispute or legal claims may be retained separately with restricted access.
5. Individual deletion requests
Where Strimeta acts as controller, verified deletion requests are actioned subject to statutory exceptions. Where Strimeta acts as processor, it follows Customer's lawful deletion instruction. Immediate erasure from every backup is not required where the backup is isolated from use, securely protected and expires through a documented rotation, but deleted data will not be intentionally restored to active use.
6. Legal holds
A documented legal hold temporarily overrides ordinary deletion only for data reasonably necessary for litigation, investigation, regulatory or legal obligations. Holds are reviewed and lifted promptly when no longer required.
Strimeta Data Retention and Deletion Policy
Product: Strimeta
Operator / Provider: Jakub Marcinka, trading under jmarcinka.cz
IČO: 21474672
Business address: Na Kopci 1210/10, 460 14 Liberec XIV-Ruprechtice, Czech Republic
Contact: jmarcinka@email.cz
Website: https://jmarcinka.cz
Version: 1.0
Effective date: 9 September 2026
Status. This is Strimeta's operational legal documentation prepared for launch. Mandatory law prevails over contractual text. Because international privacy, tax, consumer and platform rules change, the regional launch gates and vendor list must be re-checked before entering a new market or materially changing the product.
1. Principle
Strimeta retains identifiable data only for a documented operational, contractual, security or legal need. Retention is measured by data category rather than indefinite account-wide storage.
2. Default operational periods
Unless a Customer selects a shorter supported period or law requires otherwise:
- raw/event-level community metadata: 90 days;
- derived community/cohort metrics that remain identifiable: 13 months maximum;
- de-identified aggregate statistics that cannot reasonably be linked back to individuals: may be retained longer for trend/capacity purposes;
- application/security logs containing personal data: 180 days unless a security investigation requires a legal hold;
- closed support cases: 24 months unless a shorter period is sufficient;
- inactive account profile data: deleted or anonymised within 90 days after termination after the exit period, except legal/accounting records;
- billing/accounting/tax records: retained for the statutory period required of the Provider in the Czech Republic or another applicable jurisdiction.
3. Backups
Strimeta may maintain daily, weekly, monthly and quarterly recovery points across Contabo, the Provider's workstation and NAS. Customer/community personal data must not intentionally remain recoverable in the operational backup chain for more than 90 days after deletion from active systems. Longer-term quarterly archives, if kept, must be limited to non-customer system configuration, de-identified material or records that Strimeta is legally required to preserve.
Backups are encrypted and are not searched or restored for ordinary product use. If a disaster restore reintroduces records previously scheduled for deletion, the deletion queue/instructions are re-applied.
4. Termination
Customer receives a reasonable export/exit window. After that window, Customer Data is removed from active production according to the deletion workflow. Account/billing records required for tax, fraud, sanctions, dispute or legal claims may be retained separately with restricted access.
5. Individual deletion requests
Where Strimeta acts as controller, verified deletion requests are actioned subject to statutory exceptions. Where Strimeta acts as processor, it follows Customer's lawful deletion instruction. Immediate erasure from every backup is not required where the backup is isolated from use, securely protected and expires through a documented rotation, but deleted data will not be intentionally restored to active use.
6. Legal holds
A documented legal hold temporarily overrides ordinary deletion only for data reasonably necessary for litigation, investigation, regulatory or legal obligations. Holds are reviewed and lifted promptly when no longer required.