Before public launch, the publisher must add its legal identity, support contact and applicable retention/deletion procedures.
Desktop platform login sessions, media, creator lists and task history are stored locally. The application sends media requests to the selected platform and its media providers. Platform sessions are not sent to billing.
Billing sends purchase codes and a random installation identifier to the publisher's service. The service stores hashed purchase codes, provider checkout references and an installation binding. Creem collects payment and billing details under its own policies. This draft does not add advertising or usage analytics.
Keep activation keys and platform credentials private. Diagnostic logs may contain sensitive source information: review and redact them before sharing. Source-code access and license terms must accompany the public release.
Back