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 Connected Platform Data 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. Purpose
This policy governs data obtained through Customer-authorised integrations such as Discord and Discourse.
2. Minimum access
Connectors request only permissions/data necessary for enabled features. Strimeta does not use platform access to discover unrelated communities or collect unrelated content.
3. Discord-specific restrictions
Strimeta will not use Discord API Data to:
- profile individual Discord users, identities or relationships;
- sell, license or broker API Data;
- target or sell advertising;
- contact users outside Discord without the permission required by Discord and applicable law;
- re-identify de-identified data;
- train AI/ML on message content without Discord's express permission where required.
Strimeta's intended metrics are community/cohort-level activity, retention, response and moderation-workload analytics. Individual identifiers may be used transiently or minimally where necessary to compute lawful aggregates, permissions or deduplication, but not to create a prohibited behavioural dossier.
4. Message content
Strimeta's default architecture discards message content and stores metadata/aggregates needed for analytics. A future feature requiring persistent message content cannot launch without a new platform-rule review, DPIA/privacy review, retention change and Customer notice.
5. Discourse and other platforms
Customer remains responsible for lawful configuration, API credentials, notices and permissions. Strimeta follows the platform's applicable API/Developer terms and will disable a connector feature if continued processing would violate those rules.
6. Deletion and revocation
Disconnecting an integration stops new ingestion as soon as technically practicable and triggers deletion/retention rules for existing Customer Data. Revoked API tokens are removed or invalidated promptly.
Strimeta Connected Platform Data 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. Purpose
This policy governs data obtained through Customer-authorised integrations such as Discord and Discourse.
2. Minimum access
Connectors request only permissions/data necessary for enabled features. Strimeta does not use platform access to discover unrelated communities or collect unrelated content.
3. Discord-specific restrictions
Strimeta will not use Discord API Data to:
- profile individual Discord users, identities or relationships;
- sell, license or broker API Data;
- target or sell advertising;
- contact users outside Discord without the permission required by Discord and applicable law;
- re-identify de-identified data;
- train AI/ML on message content without Discord's express permission where required.
Strimeta's intended metrics are community/cohort-level activity, retention, response and moderation-workload analytics. Individual identifiers may be used transiently or minimally where necessary to compute lawful aggregates, permissions or deduplication, but not to create a prohibited behavioural dossier.
4. Message content
Strimeta's default architecture discards message content and stores metadata/aggregates needed for analytics. A future feature requiring persistent message content cannot launch without a new platform-rule review, DPIA/privacy review, retention change and Customer notice.
5. Discourse and other platforms
Customer remains responsible for lawful configuration, API credentials, notices and permissions. Strimeta follows the platform's applicable API/Developer terms and will disable a connector feature if continued processing would violate those rules.
6. Deletion and revocation
Disconnecting an integration stops new ingestion as soon as technically practicable and triggers deletion/retention rules for existing Customer Data. Revoked API tokens are removed or invalidated promptly.