Privacy policy

The data controller for personal data processed through the Service is the operator of eContent Manager, reachable at support@econtentmanager.com. We operate the website econtentmanager.com and the application behind it.

Where a payment processor, OAuth provider, social network, or AI inference vendor processes data for its own purposes (for example, fraud screening or its own product improvement under its contract with you or with us), that vendor is an independent controller or a joint controller for that processing. Their privacy notices also apply.

This Policy covers visitors, registered users, workspace teammates, newsletter subscribers, people who message a public chatbot widget, and people whose information you upload or paste into the Service. It does not cover third-party websites you reach from the Service.

If you use the Service as a teammate, the workspace owner is also responsible for making sure they have a lawful basis to invite you and to process your activity in that workspace.

We collect only what we need to run, secure, bill, and improve the Service. Categories include:

• Account data: name, email address, password hash (we never store your password in plain text), optional profile image, language preference, affiliate code, and affiliate payout email.
• Authentication data: session tokens; optional authenticator (TOTP) secret, stored encrypted; Google or Facebook account identifiers if you sign in with those providers.
• Billing data: plan, subscription status, credit balance, invoices, and payment references (Stripe customer/subscription IDs, PayPal order IDs, Razorpay order IDs). We do not store full card numbers, CVV, or bank account numbers. Those are handled by the payment provider you choose.
• Workspace content: prompts, generated text, images, audio, video, titles, folders, templates you fill, articles, chat messages, chatbot names and training sources, voice samples you upload to clone, site pages, and support tickets.
• Connected accounts: OAuth tokens and profile handles for social networks you connect (for example X, LinkedIn, Facebook, TikTok) so we can publish or fetch insights you request.
• Bring-your-own keys: vendor API keys you save, stored encrypted at rest.
• Usage and logs: feature used, credits charged or refunded, timestamps, login activity, IP address, user agent, and security events (failed sign-in, Turnstile failures).
• Communications: emails we send you (transactional and, if you subscribe, newsletter), and messages you send to support.
• Public widget traffic: messages submitted to an embeddable chatbot, plus bot-check tokens. Those messages are billed to the bot owner’s workspace.

We do not require government ID. We do not intentionally collect special-category data (health, biometrics for identification, precise geolocation). Do not paste that kind of data into prompts unless you accept that it will be processed as ordinary workspace content and sent to inference providers.

We use personal data to:

• Create and secure your account, including two-factor authentication and abuse prevention.
• Provide generation, storage, billing, teams, affiliates, social publishing, and support.
• Meter credits, prevent double-spend, and refund credits when a live generation fails as described in the Terms.
• Send transactional email (sign-in, password reset, invoices, team invites, security notices).
• Send newsletter email only if you subscribe via the footer form or an equivalent opt-in.
• Understand how the site is used (page views, referrer, browser, and approximate country via Umami) so we can improve the Service. This is not advertising.
• Monitor errors and reliability (for example Sentry) so we can fix outages.
• Comply with law, enforce the Terms, and protect the Service, users, and third parties.

Lawful bases (where GDPR/UK GDPR apply): performance of a contract (providing the Service you asked for); legitimate interests (security, fraud prevention, product reliability, Umami traffic measurement, limited analytics of errors) balanced against your rights; consent (newsletter; optional cookies/local storage that are not strictly necessary; connecting a social account); and legal obligation (tax, accounting, responding to lawful requests).

To generate text, images, audio, video, embeddings, or speech, we send the relevant prompt, attachment, or snippet to the inference provider configured for that job. Depending on workspace settings and available keys, that may include DigitalOcean Gradient serverless inference and/or other vendors such as OpenAI, Google, Anthropic, xAI, Fal, ElevenLabs, Stability, and similar providers listed in Admin → Providers.

• We do not operate our own foundation models, and we do not use your prompts or outputs to train an eContent Manager model.
• Inference vendors process your content to return a result. Whether they retain content, use it to improve their models, or offer zero-retention depends on that vendor’s terms, your contract with them (including BYOK), and how the vendor account is configured. Read those terms before you paste confidential material.
• Plagiarism and AI-detector checks, when enabled, are sent to the configured integrity vendor (for example Copyscape or GPTZero), not treated as a generic chat completion.
• Chatbot training uses embedding providers to vectorize sources you add. Public widgets send visitor messages to the same stack and bill the bot owner.

You must have the right to submit everything you upload or paste. Do not submit other people’s personal data unless you have a lawful basis and the authority to do so.

Paid plans and credit packs may be settled through Stripe, PayPal, and/or Razorpay. Those companies collect and process payment instrument data under their own policies. We receive confirmation, identifiers, amounts, and status so we can grant credits or a subscription. Chargebacks and payment disputes are handled with the relevant processor and may lead to suspension as described in the Terms.

We use cookies and local storage that are required to run a signed-in product, plus a small number of preference settings.

• Authentication cookies (Auth.js / session): keep you signed in. Essential. Duration: session or a rolling login lifetime set by the auth configuration.
• locale: stores English or Arabic UI preference for about 12 months (max-age 31,536,000 seconds). Preference.
• ecm_maint_bypass: lets an operator bypass a maintenance screen. Essential for operations. About 24 hours.
• ecm_impersonate: used only when an administrator impersonates a customer for support. Essential for that admin action. About four hours.
• Cloudflare Turnstile: a bot check on sign-in, registration, password reset, public widgets, and similar forms. Security. Subject to Cloudflare’s notices.
• Theme (light/dark): stored in the browser (typically localStorage via the theme library), not as a tracking cookie.
• Optional PWA service worker: if you install or keep the app open, the browser may register a service worker that retries same-origin page loads when the network fails. It does not cache /api/ responses.
• Umami (script from fickanalytics.phluit.net): privacy-oriented pageview measurement. It records the URL, referrer, browser, OS, device type, and approximate country. It does not set an advertising cookie and is not used for cross-site ads. If your browser sends Do Not Track, Umami will not record the visit.

We do not use advertising pixels or cross-site marketing cookies on the marketing site. Blocking essential cookies will prevent sign-in. You can delete preference cookies from your browser.

We do not sell personal data. We share it only as needed to operate the Service:

• Infrastructure: hosting, database, object storage (for example local disk or Cloudflare R2 when configured), and Redis/job queues on the environment that runs econtentmanager.com.
• AI and media vendors you or the operator enable (see section 5), including DigitalOcean Inference and any other provider listed in Admin → Providers.
• Payment processors: Stripe, PayPal, and/or Razorpay (section 6).
• Email delivery (SMTP2GO or the configured mail API) for transactional and newsletter messages.
• Cloudflare Turnstile for bot protection.
• Error monitoring (Sentry / Bugsink or the configured DSN) for diagnostics. Request bodies are not intentionally sent as marketing profiles.
• Umami, hosted at fickanalytics.phluit.net, for cookieless pageview statistics.
• OAuth login providers (Google, Facebook) and social platforms you connect.
• Integrity vendors (for example Copyscape, GPTZero) when you run those checks.
• Workspace teammates and the workspace owner, for content and usage inside that workspace.
• Professional advisers or authorities when required by law or to defend legal claims.
• A successor operator if the Service is transferred, under this Policy or a notice to you.

Vendors and infrastructure may process data in the United States, the European Economic Area, India (for example Razorpay), and other countries. Where GDPR/UK GDPR require a transfer tool, we rely on the vendor’s published mechanism (such as Standard Contractual Clauses) and your contract with that vendor when you use BYOK. By using the Service you understand that your content may leave your country to fulfil a generation request.

• Account and workspace content: kept while the account is active so you can reopen history, billing, and bots.
• After you delete your account in Settings, we disable login, replace the email with a non-working placeholder, clear the password, authenticator secret, and payout email we hold, and delete generations, conversations, chatbots, social connections, tickets, uploaded voice profiles, site pages, and personal API keys we store for that user, as implemented in the product.
• Billing records, credit ledgers, and fraud logs may be kept longer where tax, accounting, or anti-abuse law requires it, or until a dispute is closed.
• Newsletter addresses are kept until you unsubscribe or we delete the list record.
• Backups, if any, expire on the backup rotation of the hosting environment.
• Inference vendors may retain copies according to their own retention schedules, which we do not control.

We use HTTPS, hashed passwords, encrypted storage for secrets you save, session authentication, optional TOTP, Turnstile on public forms, and role checks for admin tools. No method is perfectly secure. You must keep your password and authenticator device confidential and use a unique password. Notify us immediately at the contact below if you believe an account is compromised.

Depending on where you live, you may have the right to access, correct, delete, restrict, or object to certain processing, to withdraw consent (without affecting prior lawful processing), to data portability, and to lodge a complaint with a supervisory authority.

• Export: signed-in users can download a JSON export of profile, generations, payments, usage, conversations, chatbots, social metadata, tickets, affiliate commissions, and recent logins from Settings (Download my data).
• Deletion: signed-in users can delete their account from Settings. This is irreversible. Workspace owners should export anything they need and remove teammates first. Some billing identifiers may remain with payment processors.
• Newsletter: stop messages by using the unsubscribe path in the email or by contacting us.
• California (CCPA/CPRA): we do not sell or share personal information for cross-context behavioral advertising. You may request know/access, delete, and correct via support@econtentmanager.com. We will not discriminate against you for exercising these rights.
• EEA/UK: you may contact your local data protection authority. You can also email us; we will respond within the time required by applicable law.
• Other US state privacy laws (for example Virginia, Colorado, Connecticut, Texas): where they apply, you may request access, correction, deletion, and to opt out of targeted advertising or sale. We do not sell or share personal information for targeted advertising. Email the address below.
• Automated processing: credit metering, rate limits, Turnstile, and fraud checks run automatically so we can provide and secure the Service. We do not make solely automated decisions that produce legal effects about you (for example creditworthiness) without a way to contact a human at support@econtentmanager.com.
• Do Not Track: Umami honors a DNT signal and will not record that visit. We do not run third-party advertising pixels on the marketing site.

To exercise rights, email support@econtentmanager.com from the address on the account, or use in-product export/delete. We may need to verify the request. We will not fulfil a request that would violate law or the rights of others (for example, deleting another teammate’s account).

The Service is for people 18 years or older. We do not knowingly collect personal data from children. If you believe a child has created an account, email us and we will delete it.

We may update this Policy. The “Last updated” date at the top of the page will change. Material changes will be posted on this page and, where required, notified by email or an in-app notice. Continued use after the effective date constitutes acceptance of the updated Policy.

Privacy requests: support@econtentmanager.com. Website: econtentmanager.com.