Privacy Policy

Effective: [DATE] · Last updated: [DATE] · Version 1.0

1. About this policy

Appneck is a developer platform for WordPress plugin companies, operated by [LEGAL ENTITY NAME], [REGISTERED ADDRESS]. This policy explains what data we handle, why, and what control you have over it.

2. Two different groups of people

This policy covers two groups, and the rules differ for each.

Appneck customers are plugin companies and their team members who hold an Appneck account. For their data, Appneck is the data controller.

Site owners are people who install a WordPress plugin that includes the Appneck SDK. For their data, the plugin company is the data controller and Appneck is the processor acting on that company's instructions. If you are a site owner with a question about your data, contact the plugin company first — they decide what is collected and how long it is kept.

3. Data we collect from Appneck customers

When you create an account we collect your name, email address, and a hashed password. We never store passwords in readable form. We also store your organisation name, the products you register, your team members and their roles, and any content you enter in the dashboard.

Payments are handled by Stripe. We store a customer reference, plan, and invoice history. We never see or store your card number.

We keep normal server logs, which include IP addresses and browser user-agent strings, for security and debugging.

If you contact support, we keep that correspondence.

4. Data the SDK collects from WordPress sites

The Appneck SDK collects nothing until the site owner explicitly agrees. Consent is fail-closed: with no recorded consent, no telemetry is sent or stored.

Once consent is given, the SDK may send: the site domain, the administrator email address, the plugin version, PHP version, WordPress version, WooCommerce version where present, site locale and timezone, an approximate country derived from the request IP, whether the site is a multisite network, the server type, and install, activate, deactivate, reactivate and uninstall events.

The SDK also sends a periodic heartbeat — a short "still active" signal used to count live installations.

Plugin companies can define their own custom events, such as a feature being used. What those events contain is decided by the plugin company, not by Appneck.

If the plugin company enables it, the SDK can report PHP and fatal errors raised by their plugin.

When a plugin is uninstalled, the SDK may show an optional feedback form. Answering it is voluntary.

5. What the SDK never collects

The SDK does not read or transmit the content of your site: no posts, pages, media, comments, orders, customers, form submissions, database contents, or files. It does not collect personal data about your site's visitors. It does not collect passwords, API keys, or credentials of any kind.

7. How we use data

Customer account data is used to run the service: authentication, access control, billing, support, and service notices.

Telemetry is used to produce the analytics the plugin company sees — install counts, version adoption, feature usage, error trends, and uninstall feedback. Individual site data is only ever shown to the company that owns the plugin installed on it. No plugin company can see another company's data, and no site's data is shared between companies.

We do not sell data. We do not use telemetry for advertising or share it with advertising networks.

8. Service providers

We use a small number of providers to run Appneck: [HOSTING PROVIDER AND REGION] for servers and databases, Stripe for payments, and Resend for email delivery. Each processes data only to provide its service to us.

We may disclose data where legally required, or to protect the rights and safety of our users.

9. How long we keep data

Raw telemetry events are kept for a limited window — 90 days by default — and then deleted automatically. Summarised analytics derived from those events, which contain no site-identifying detail, are kept indefinitely.

Installation status history is kept for as long as the product exists, because churn and reactivation reporting depends on it.

Account data is kept while your account is active and for [NUMBER] days after closure, after which it is deleted or anonymised. Billing records are kept for as long as tax law requires.

Temporary demo sites created through trymywp.com are deleted automatically when they expire, along with their contents. The email address supplied to create a demo is kept by the plugin company that owns the demo.

10. Security

All connections use HTTPS. SDK requests are signed with a per-installation secret and rejected if the signature or timestamp fails, which prevents tampering and replay. Secrets are encrypted at rest and license keys are stored as hashes. Access inside the platform is controlled by role-based permissions, and each organisation's data is isolated from every other organisation's. We take regular backups.

No system is perfectly secure, but we treat any incident affecting personal data seriously and will notify affected parties as required by law.

11. Your rights

Depending on where you live, you may have the right to access your data, correct it, delete it, receive a copy in a portable format, restrict or object to processing, and withdraw consent at any time. Withdrawing consent does not affect processing that already happened.

If you are in California, you also have the right to know what is collected, to request deletion, and not to be discriminated against for exercising these rights. We do not sell personal information.

To exercise any of these rights, contact us at the address below. If your request concerns telemetry from a specific plugin, we may need to refer you to the plugin company, since they control that data.

12. Contact

Privacy questions and data requests: [email protected]

Postal: [LEGAL ENTITY NAME], [REGISTERED ADDRESS]

13. Cookies

appneck.com uses cookies that are strictly necessary: session and authentication cookies to keep you logged in, and a theme preference cookie. We do not use advertising or cross-site tracking cookies.

14. Children

Appneck is a tool for professional developers and is not directed at anyone under 16. We do not knowingly collect data from children. If you believe we have, contact us and we will delete it.

15. International transfers

Our servers are located in [REGION]. If you access Appneck from elsewhere, your data is transferred to and processed there. Where required, we rely on appropriate safeguards such as standard contractual clauses.

16. Changes

We may update this policy. The version number and last-updated date at the top always reflect the current version. For material changes we will notify account holders by email, and the SDK will record consent against the policy version in effect at the time.