Legal

Privacy Policy

Last updated: May 1, 2026

This Privacy Policy explains how MultiPub Pro ("we", "our", "us") collects, uses, and protects information when you use our website ( multipub.pro ) and the application at app.multipub.pro (together, the "Service").

We aim to collect the minimum data required to run the Service. We never sell your data. We never use the content you generate to train models or share it with third parties beyond the AI providers you choose to route through.

1. Data we collect

1.1 Account data

  • Email address — required to create an account, log in, recover the password, and receive transactional emails (verification, billing receipts).
  • Password — stored only as a salted bcrypt hash. We cannot read your password.
  • Email verification status and timestamp.
  • Login timestamps and IP address (for security audit and abuse detection).

1.2 Subscription & billing data

Payments are processed by Paddle.com, our merchant of record. We do not receive or store your card or banking details. Paddle returns to us only:

  • Paddle customer ID and subscription ID (linking your account to your subscription).
  • Subscription status (active, past due, canceled, etc.) and billing period dates.
  • Plan code (Free / Starter / Standard / Pro / Pro Max).

Paddle's privacy practices apply to the actual payment data — see paddle.com/legal/privacy.

1.3 Service-generated content

The following data is created as you use the Service and is stored to make the product work:

  • WordPress sites you connect: domain, network grouping, site authentication tokens (used by the WordPress plugin to talk to our backend over HTTPS).
  • Generation requests: keywords, topics, target sites, model selection, generation settings.
  • Generated articles: titles, content, metadata. We retain these so you can review history and export them.
  • Usage counters: monthly credits used, premium credits used, articles published — used for plan enforcement.
  • AI call logs: per-request metadata (vendor, model, latency, error type, credit cost) — kept while your account is active to support billing audit and operational diagnostics. We do not log the prompt or generated text in these records.
  • Credit ledger: every credit movement (charge / release / admin adjustment) with a link to the article that triggered it — kept while your account is active so the Billing → Usage breakdown can answer "where did my credits go" honestly.

1.4 BYO (bring-your-own) AI keys

If you connect your own OpenAI / Anthropic / DeepSeek / Runware API key, we store it encrypted at rest using Fernet (AES-128 with HMAC-SHA256) so even our database administrators cannot read it. The encryption key is held in our application environment, not in the database.

We use your BYO key only to make requests to the corresponding AI provider on your behalf when you trigger a generation. We never log the key plaintext, never share it with anyone, and you can disconnect or pause it at any time from Settings → AI Keys.

1.5 Cookies & technical data

  • Authentication cookie: a JWT stored in localStorage to keep you signed in. Expires after 7 days of inactivity.
  • CSRF protection: standard same-origin tokens.
  • Cloudflare may set anti-bot cookies on the public website.

We do not use third-party advertising trackers, retargeting pixels, or session-replay tools.

2. How we use your data

  • Provide the Service — generate articles, publish to your WordPress sites, enforce credit limits.
  • Bill you correctly — by tracking subscription status and credit consumption.
  • Communicate with you — verification, password resets, billing receipts, and important service notices. We do not send marketing emails without consent.
  • Detect abuse — IP and rate-limit data are used to block bots, brute-force attempts, and unfair use.
  • Improve the Service — aggregate metrics (e.g. error rates per AI vendor) help us pick better defaults. We do not look at your generated content to train anything.

3. Who we share data with

We share data with the following categories of subprocessors, only as needed to operate the Service:

  • AI providers (DeepSeek, OpenAI, Anthropic, Runware) — we send them the generation prompts you submit so they can return text or images. Each has its own privacy policy and data retention rules.
  • Paddle — payments and tax compliance.
  • Email provider (Resend / Postmark / Amazon SES, depending on configuration) — transactional email delivery only.
  • Hosting — Hetzner Cloud (Germany / EU) — application servers and database.
  • Cloudflare — DNS, DDoS protection, anti-bot challenges.

We do not sell, rent, or trade your personal data to third parties for marketing or profiling.

4. AI-generated content

When you trigger a generation, your prompt and parameters are sent to the AI vendor you selected (DeepSeek, OpenAI, Anthropic, Runware, etc.). The vendor's terms apply to that request:

  • OpenAI does not train on API requests by default (per OpenAI Enterprise / API terms in effect at the time of writing).
  • Anthropic does not train on API requests by default (per Anthropic API terms in effect at the time of writing).
  • DeepSeek's published terms allow them to retain and process API content for service improvement and may include model training. If you want stricter handling, switch to OpenAI / Anthropic via BYO keys, or check the current DeepSeek policy at platform.deepseek.com.

AI vendors update their privacy and training practices regularly — these summaries reflect our understanding at the "Last updated" date above. Always verify with the vendor directly before sending sensitive content.

If you bring your own API key, your requests are governed entirely by your direct agreement with that vendor — we are merely a transport layer.

5. Data retention

  • Active accounts: data is retained as long as the account exists. Posts older than your plan's retention window (Free 30 days, Starter 180, Standard 1 year, Pro 2 years, Pro Max forever) are auto-cleaned from the panel; copies on your WordPress are never touched.
  • Cancelled subscriptions: cancelling a paid subscription downgrades you to Free but keeps your account and data. You can reactivate at any time.
  • Account deletion: deleting your account (via Settings or by contacting us) is processed within 1–3 business days and removes all account data immediately, except billing records that we are legally required to retain for tax purposes (typically 7 years).
  • AI call logs & credit ledger: kept while the account is active. Removed when you delete the account (subject to the billing-record retention above).
  • Generated articles (in our panel): subject to the per-plan post-history retention above. Articles published to your WordPress are stored on your WordPress and are not affected.
  • Audit logs (login, password change, key add/remove, admin actions): kept while the account is active.

6. Your rights

If you reside in the EU, UK, California, or another jurisdiction with privacy laws, you have the right to:

  • Access the data we hold about you.
  • Correct inaccurate data.
  • Delete your account and associated data (self-service via Settings, or by emailing us).
  • Export your data in a portable format (we provide JSON / CSV exports of your sites and articles on request).
  • Withdraw consent for any optional processing.
  • Lodge a complaint with your local data protection authority.

To exercise any of these rights, email support@multipub.pro.

7. Security

We use standard industry practices to protect your data:

  • HTTPS / TLS for all traffic between your browser, our servers, and AI providers.
  • Bcrypt password hashing (cost factor 12).
  • Fernet symmetric encryption for stored BYO API keys.
  • HMAC-signed tokens for the WordPress plugin ↔ backend channel, with a 5-minute timestamp window to prevent replay.
  • Per-user data isolation enforced at the database query level (every tenant table is filtered by user ID).
  • Daily automated database backups with 30-day retention.
  • Rate limiting and IP-based abuse detection on authentication endpoints.

No system is 100% secure. If we ever discover a breach affecting your data, we will notify you within 72 hours of confirming the incident.

8. Children

The Service is not intended for users under 16. We do not knowingly collect data from anyone under that age. If you believe a minor has signed up, contact us and we will delete the account.

9. International transfers

Our servers are located in the European Union. AI providers may process your prompts in the US or other regions. Where required by law, we rely on Standard Contractual Clauses or equivalent mechanisms with our subprocessors.

10. Changes to this policy

We may update this Privacy Policy as the Service evolves. Material changes will be communicated by email at least 14 days in advance. The "Last updated" date at the top of this page reflects the most recent revision.

11. Contact

Questions, requests, or concerns? Email support@multipub.pro. We respond within 5 business days.