Privacy Policy

1. Data we process

The data depends on the features you use.

• Username, email, password hash, authentication details, and account settings.
• IP address, technical and anti-abuse data, application and access logs.
• Votes, reviews, reports, support requests, messages, and notifications.
• Payment transaction provider, amount, status, and internal balance operations.
• Uploaded logos, branding creatives, and server data.
• Google Analytics data only after analytics consent.

2. Purposes and legal grounds

Data is used to provide features, perform user requests, secure the service, prevent abuse, account for payments, moderate content, provide support, and meet legal obligations.

• Analytics is based only on voluntary consent.
• Necessary processing supports service operation, performance of these terms, and legitimate security interests.

3. Recipients and infrastructure

Data may be processed in MariaDB, file storage, and hosting infrastructure. Payment data is shared with the selected provider as needed for a transaction. Google receives analytics data only after consent.

• The service has an international audience, so processing may involve cross-border transfers within the infrastructure used.
• The service does not store full payment card details.

4. Retention

Accounts and user content are retained while the account or related feature is used. Financial and administrative audit records, security logs, and backups may be retained longer as required by law and reasonably needed to protect rights.

• Removing public content does not always immediately remove audit or backup records.
• Retention may be shortened after a verified request where continued storage is unnecessary.

5. User rights

Users may request access, correction, deletion, or restriction and may withdraw analytics consent. Requests remain subject to mandatory law and the need to protect the service and others.

• Submit requests through Support Requests or the operator email.
• Identity or account ownership verification may be required.

6. Security and changes

Access controls, logging, authentication checks, and other reasonable safeguards are used. Absolute transmission and storage security cannot be guaranteed. Updates are published with a new effective date.