Privacy Policy

Last updated: 2026-05-28. This page explains what data we collect, why, how long we keep it, and your rights.

1. What we collect

From your WordPress site: nothing automatically. Files, database rows, and post content stay on your host. The plugin only sends content to our server when you explicitly trigger an AI action.

From the AI session: when you chat with the AI we send your chat messages, the relevant code or file contents you reference, and the tool calls the agent decides to make. These pass through our server, are sent to the LLM provider (OpenAI / Anthropic / DeepSeek / etc.), and the response comes back.

What we store on our server:

• Account: email, password hash (scrypt), creation date.
• License: key, status, tier, associated site URLs.
• Subscription: tier, status, Stripe customer ID, current period.
• Chat memory: last ~12 turns per session for the "remember context" feature, in the conversation_turns table.
• Run metadata: session ID, model used, timestamps, success/error status, in the runs table.
• Server logs: HTTP access logs, error traces. Rotated automatically.

What we do NOT store: we don't keep persistent copies of your full WordPress files, your database contents, or full LLM response bodies beyond the session memory window.

2. Why we collect it

• To provide the Service: the AI needs context to be useful.
• To bill you: Stripe needs to know what plan you're on.
• To improve the product: we look at aggregated patterns (top prompts, where the AI gives up, where tools fail) to fix gaps. See §5 for opt-out.
• To detect abuse: we look at sudden spikes, ToS violations, or fraud indicators.
• Legal compliance: if law enforcement requests data under valid legal process.

3. Who we share it with

• LLM providers — chat content goes to whichever provider answers (OpenAI, Anthropic, DeepSeek, OpenRouter, Groq). Each provider has its own privacy policy. We use API endpoints (not consumer ChatGPT), which providers commit to NOT train on by default.
• Stripe — credit card data goes directly to Stripe; we never see it. We only see Stripe customer IDs and last-4 card digits.
• Cloud infrastructure — our server runs on Contabo (Germany); data sits at rest in SQLite on disk.
• No third-party trackers on api.wordvibe.io. No Google Analytics, no Facebook pixel, no Hotjar.

4. Retention

• Account + license + subscription: kept while you have an active account, deleted within 30 days of account closure.
• Chat memory: last 12 turns per session, indefinite while you're active. You can clear it from the chat UI.
• Run metadata + server logs: 90 days, then aggregated and the raw records purged.
• Billing records: kept for 7 years as required by tax law.

5. Your rights

You can at any time:

• Access — request a copy of all data we have on you.
• Correct — fix anything that's wrong, including via your account dashboard.
• Delete — request full erasure (subject to billing-record retention required by law).
• Object — opt out of the "improve product" use of your chat data. Toggle "Exclude my conversations from analytics" in Settings, or email us.
• Export — request a JSON dump of your account + chat memory.
• Withdraw consent — for any processing based on consent.
• Complain — to your local data protection authority (DPC in Ireland, ICO in UK, etc.).

Email [email protected] for any of these. We respond within 30 days.

6. GDPR / EU users

If you're in the EU/EEA/UK, GDPR applies. Our legal basis for processing chat content is legitimate interest (Art. 6(1)(f)) — providing the AI service you asked for. Aggregation for product improvement also relies on legitimate interest, with the opt-out described above. Billing is processed under contractual necessity (Art. 6(1)(b)).

We do not currently transfer personal data outside the EEA except to LLM providers (US-based, covered by Standard Contractual Clauses) and Stripe (covered by their published GDPR adequacy commitments).

7. California (CCPA / CPRA)

California residents have the same access / correction / deletion rights as listed above. We do NOT sell or share personal information for cross-context behavioral advertising. We don't have a "Do Not Sell" link because we don't sell.

8. Children

WordVibe is not directed to anyone under 16. We don't knowingly collect data from children. If you believe we have data from a child, email us and we will delete it.

9. Security

Account passwords are stored as scrypt hashes. License keys and chat content sit in a SQLite database on the server's encrypted volume. Server access requires an SSH key. We don't currently encrypt chat content at rest with per-user keys — on our roadmap. Connections to the server are HTTPS with Let's Encrypt certificates.

Breach notification: if we believe your data has been accessed by an unauthorized party, we will notify you within 72 hours of confirmation, by email.

10. Changes to this policy

Material changes will be announced by email and on this page with a new "Last updated" date. Continued use after the change means you accept it.

11. Contact

Data Protection lead: [email protected]. Postal: [LEGAL ADDRESS — to be filled].

Heads up: this is a first-draft template. Legal-address and jurisdiction-specific clauses will be filled in, and the document reviewed by counsel, before WordVibe scales past initial soft-launch.