Privacy Policy

Last updated: 2026-02-05

This Privacy Policy explains how Westh Creative (“we”, “us”) handles personal data when you visit our website or contact us about our work. We aim to collect as little as possible and keep things transparent.

1. Data we may collect

• Basic technical data such as browser type, device information, timestamps and IP address (typically via server logs).
• Contact details you provide voluntarily (e.g., name/email) when you reach out.
• Message content you send to us (e.g., project description or questions).

2. Why we process data

• To operate and secure the website (fraud prevention, troubleshooting, performance).
• To respond to inquiries and provide support.
• To meet requirements for developer portals and app reviews (e.g., stable policy URLs and support contact).

3. Legal basis

• Legitimate interests — operating and protecting the website and responding to requests.
• Consent — when you voluntarily provide information via email or other channels.

4. Sharing and third parties

We do not sell personal data. Data may be processed by service providers required to run the website (e.g., hosting). If you work with us on integrations, third-party platforms (such as TikTok/Meta/Google) may have their own policies and terms.

5. Data retention

We retain contact messages only as long as needed to handle the request and maintain reasonable records. Server logs are retained for a limited time according to hosting and security practices.

6. Your rights

Depending on your jurisdiction, you may have rights to access, correct, delete, or object to processing of your personal data. To exercise these rights, contact us using the email below.

7. Cookies

This website does not use tracking cookies by default. The hosting provider may use strictly necessary technical cookies or logs to ensure site functionality and security.

8. Contact

Support email: support@westhcreative.com

Note: This policy is designed to meet typical developer portal requirements (policy URL + support contact). If you later operate a public user-facing product (accounts, payments, analytics), the policy should be expanded accordingly.