Privacy Policy

Last updated: November 21, 2026 Effective date: May 24, 2026

This Privacy Policy describes how Omniposter (“Omniposter,” “we,” “us,” or “our”) collects, uses, stores, and discloses information when you use our website at https://omniposter.ai (the “Site”) and the related software services (collectively, the “Service”). By creating an account or otherwise using the Service, you agree to the practices described here.

If you do not agree with this Privacy Policy, do not use the Service.


1. Who we are

Omniposter is an AI-powered content engine for digital publishers. The Service helps publishers commission AI-generated editorial stories and marketing posts, schedule and publish them to third-party platforms (such as WordPress, X/Twitter, LinkedIn, Facebook, and Instagram), analyze the resulting performance, and, if they choose, collect reader sign-ups and comments on their own sites (see Section 2.4).

For privacy questions, contact us at dev@omniposter.ai.


2. Information we collect

2.1 Information you provide directly

  • Account information. When you register, we collect your email address and a password (stored only as a salted hash; we never see your password in plaintext).
  • Profile and project information. Project name, website URL, brand voice, hashtags, editorial preferences, researcher personas, publishing destinations, and other configuration you supply.
  • Third-party credentials and tokens. API keys for the AI providers you choose to use (Anthropic / Claude, OpenAI, and/or Google Gemini), WordPress Application Passwords, social-platform access tokens or app credentials, GA4 and Google Search Console authorization data, custom webhook URLs and secrets. All of these are encrypted at rest using authenticated encryption (Fernet / AES-128-CBC + HMAC-SHA256) before being written to our database.
  • Payment information. We do not store full credit-card numbers, bank account numbers, or other primary payment instruments. Payments are processed by Stripe, Inc., our payment processor. We store the Stripe customer ID, subscription ID, plan, status, billing period dates, and the last four digits / card brand that Stripe returns to us for receipts and account-management purposes. See Section 4.1.
  • Content you upload or generate. Stories, marketing posts, content seeds (e.g. ingested RSS items), researcher portraits, hero images, editorial briefs, revision notes, schedules, and any other content you create within the Service.
  • Support communications. If you email us, we keep a record of the correspondence.

2.2 Information collected automatically

  • Usage data. Server logs of API requests (timestamps, endpoints, response codes, IP addresses, user-agent strings) used to operate, secure, and debug the Service.
  • Authentication cookies. A single JWT-bearing HTTP-only cookie is set on login so we can identify your session. We do not use third-party advertising or cross-site tracking cookies.
  • Operational diagnostics. Anonymous error traces, performance metrics, and audit logs of actions taken on your account (e.g. “story #123 commissioned at 14:02 UTC”).

2.3 Information collected from third parties

  • Analytics integrations. If you connect Google Analytics 4 (GA4) and/or Google Search Console (GSC), we receive the metrics, dimensions, queries, page paths, and other report data that those services return for the properties you have authorized.
  • Social platform integrations. If you connect an X (Twitter), LinkedIn, Facebook, or Instagram account to publish on your behalf, we receive the access tokens, account identifiers (e.g. X user ID, Page ID, IG Business account ID), display name, profile image URL, and any post-level analytics returned by the platform (impressions, likes, replies, clicks, etc.).
  • Stripe. Payment status updates and webhook events delivered by Stripe for the purpose of provisioning and revoking access to paid features.
  • AI provider responses. When the Service calls the AI provider you chose (Anthropic, OpenAI, or Google), the response text and a record of which model was used is stored in association with the story or post that was generated.
  • Stock-photo provider (Pexels). Photographer attribution and image URLs returned by the Pexels API are stored on the stories that use those images.

2.4 Information about your audience (readers of your site)

Omniposter is a business-to-business Service. Two features handle personal data of the people who read a publisher’s site:

  • WordPress authors. When you sync researchers, we create WordPress users on your blog with email addresses we generate. They become users of your WordPress installation, not ours.
  • Audience (sign-up forms, registration wall, reader sign-in, and comments). This feature is off until a publisher turns it on and adds our embed script to their site. When a reader chooses to sign up, sign in, or comment through it, we collect and store, on the publisher’s behalf:
  • the email address and/or mobile phone number the reader enters, and when it was verified with a one-time code or sign-in link;
  • the display name the reader chooses, and the comments, likes, and reports they make;
  • evidence of consent: when the reader consented, the wording of the text-message disclosure they were shown, their IP address and browser user-agent at sign-up, and the page, form, and referring page the sign-up came from;
  • for each code or sign-in link we send: the address it went to, the IP address and user-agent of the request, and a keyed hash of the IP address that we use to limit abuse. We keep these records for up to 30 days (see Section 5). The codes and links themselves are stored only as hashes;
  • if the reader signs in with Google: the identifier of their Google account, linked to their record, and the email address Google confirms. The record of each Google sign-in (the account details Google sent us, which can include the reader’s name, plus the IP address and user-agent of the request) is deleted automatically within 2 days;
  • comments do not store the commenter’s IP address or any hash of it. When a reader reports a comment, we keep a keyed hash of their IP address only to limit how many reports one address can file in an hour, and delete it within about a day;
  • counts of how often each sign-up form was shown, dismissed, and completed. These counts do not identify anyone;
  • if the publisher sends newsletter issues and has switched on counting opens and clicks (it is off unless they do): whether, and when first, each reader opened an issue or clicked one of its links. To count them, the email carries a small image and links that pass through our server; we do not record the reader’s IP address or device for this. These records are deleted 30 days after the issue was sent; the issue’s totals stay and do not identify anyone.

To keep a reader signed in, the embed script saves a sign-in token, valid for one year, in the reader’s browser storage on the publisher’s site (see Section 8).

Who decides what happens to this data. For reader data, the publisher whose site the reader signed up on is the controller, and Omniposter is a processor (a “service provider”) acting on that publisher’s instructions. We use reader data only to run the Audience feature for that publisher and to protect it from abuse. We do not sell it, use it for advertising, or use it to market our own services. The publisher is responsible for telling its readers how their data is used and for having any consent its jurisdiction requires (for example, for text messages).

Deleting reader data. A signed-in reader can erase their own record from the widget (“Delete my data”). This deletes their email address, phone number, the link to their Google account, sessions, likes, reports, the records of codes and links sent to them and of their Google sign-ins, and blanks the text of their comments. Readers can also ask the publisher, who can erase a reader or remove a comment from Omniposter. If a reader contacts us directly, we will pass the request on to the publisher and help them respond.

Access to reader data. To answer a reader’s access request, the publisher can export everything we hold about that reader for its site: their record and consent evidence, linked sign-in accounts, sessions, comments, likes and reports, the stored record of each code or sign-in link sent to them (the shortened IP address, user-agent, page, return address and referring page), and any Google sign-in records we still hold (the account details Google sent, the shortened IP address and user-agent). We store IP addresses shortened, with their last part removed; the hashes used to limit abuse are not part of the export.

Banned readers. If a publisher bans a reader from commenting, we keep a one-way hash of each of that reader’s email addresses and phone numbers, and of the identifier of each Google account linked to their record, even after the reader’s record is erased, so the ban still applies if the same address or Google account signs up again. The hash cannot be turned back into the address or account. When the publisher lifts the ban, we delete every hash that ban created, including one for a Google account the reader has since unlinked and those carried over from an earlier record the reader erased before coming back. The hashes are also deleted when the publisher’s project is deleted.

Any audience data that flows through GA4, GSC, or the social platforms is governed by the privacy policies of those services, and your relationship with your audience is your responsibility.


3. How we use information

We use the information described above to:

  • Provide and operate the Service (create your account, generate content, schedule and deliver posts, run analytics);
  • Authenticate users and authorize access to projects;
  • Process payments and manage subscriptions;
  • Send transactional emails (account verification, password reset, billing notices, critical service alerts);
  • Diagnose, debug, and improve the Service;
  • Detect, prevent, and respond to fraud, abuse, security incidents, and violations of our Terms of Service;
  • Comply with legal obligations and enforce our agreements.

We do not:

  • Sell or rent your personal information to third parties;
  • Use your generated content or project configuration to train our own machine-learning models;
  • Disclose your AI API keys, social tokens, or other credentials to anyone other than the third-party service they authenticate to.

4. Sub-processors and disclosures to third parties

To operate the Service we share limited information with the following sub-processors. Each is bound by contractual privacy and security obligations. We may add or change sub-processors over time; material changes will be reflected here.

4.1 Payment processing

  • Stripe, Inc. (https://stripe.com/privacy). Receives your name, email, billing address (collected during checkout by Stripe directly), and payment instrument details. Stripe is a PCI-DSS Level 1 service provider.

4.2 Hosting and infrastructure

  • Vercel Inc. (https://vercel.com/legal/privacy-policy). Hosts the Service’s application.
  • Neon (https://neon.com/privacy-policy). Hosts the Service’s main database (managed PostgreSQL).
  • Cloudflare, Inc. (https://www.cloudflare.com/privacypolicy/). Serves our marketing website and stores uploaded files (Cloudflare R2). It also runs the Audience service on Cloudflare Workers, and the reader data described in Section 2.4 is stored in Cloudflare’s D1 database.

4.3 AI generation

When you supply an API key for an AI provider, your prompts and the content the Service generates on your behalf are sent directly to that provider using your key. We do not proxy through our own account or insert ourselves in the data flow. Your relationship with the AI provider is governed by their terms and privacy policy.

  • Anthropic, PBC. Claude models. https://www.anthropic.com/legal/privacy
  • OpenAI, L.L.C. GPT models. https://openai.com/policies/privacy-policy
  • Google LLC (Generative AI / Gemini). https://policies.google.com/privacy

In limited cases (specifically: onboarding-time site-detection, weekly trendline briefing analysis), the Service calls Anthropic using our own platform key. These calls do not include your editorial content; they include only the site URL or the analytics summary needed for that specific feature. We disclose this so you understand exactly when our key, versus your key, is in use.

  • Cloudflare Workers AI (Cloudflare, Inc.). If a publisher using Audience leaves automatic comment screening on, the text of each reader comment that would otherwise be published is checked by a safety model (Llama Guard) running on Cloudflare Workers AI. Only the comment text is sent, and the result decides whether the comment is held for the publisher to review. Comments are not sent to the AI providers listed above.

4.4 Image generation and stock photography

  • fal.ai, Inc. Provides the Flux image generation model used by the Service. Your image prompts are transmitted to fal.ai when you request AI-generated imagery. https://fal.ai/privacy
  • Pexels. Provides stock photography metadata when the editorial pipeline searches for hero images. Search queries (typically 2–4 keywords from your story) are transmitted to Pexels. https://www.pexels.com/privacy-policy/

4.5 Transactional email and text messages

  • SendGrid (Twilio Inc.). Sends transactional email (verification, password reset, billing). For publishers using Audience, it also sends readers their one-time codes and sign-in links, and the digests and newsletters the publisher sends them. Recipient address and the email body are processed by SendGrid for delivery. https://www.twilio.com/en-us/legal/privacy
  • Twilio Inc. (Programmable Messaging). For publishers using Audience with text messages turned on, sends readers who choose to sign up by text their one-time codes. Text messages do not carry sign-in links. The reader’s phone number and the message text are processed by Twilio for delivery. https://www.twilio.com/en-us/legal/privacy

4.6 Google user data (Google Analytics 4 and Search Console)

If you choose to connect your Google account, Omniposter requests read-only access to your own Google Analytics 4 and Google Search Console data through the following OAuth scopes:

  • openid and .../auth/userinfo.email — to identify the Google account you connected (your email address), so you can see which account is linked.
  • .../auth/analytics.readonly — to read the GA4 reporting data (sessions, users, top pages, traffic sources, conversions, and similar metrics and dimensions) for the GA4 properties you authorize.
  • .../auth/webmasters.readonly — to read Google Search Console reporting data (search queries, clicks, impressions, click-through rate, average position, and top pages) for the verified sites you authorize.

How we use it. This access is read-only. We retrieve the data on your behalf, cache the resulting report snapshots in our database to power your in-product analytics dashboards, and summarize it into your weekly content briefing that recommends what to write next. We never create, modify, or delete any data in your Google Analytics or Search Console accounts.

How we store, share, and protect it. The OAuth refresh token used to access your Google data is encrypted at rest (Fernet / AES-128-CBC + HMAC-SHA256). Your Google user data is shown only to you and the members of your own Omniposter project. We do not sell it, use it for advertising, or use it to train generalized AI/ML models. To generate your weekly content briefing, a summary derived from your Analytics data may be sent to the AI provider that powers that feature (see Section 4.3) — solely to produce that user-facing feature at your direction, and for no other purpose. Our personnel do not read your Google user data except where necessary for security, to comply with applicable law, or with your explicit consent (for example, to resolve a support request). When you disconnect the integration or delete your account, the token is deleted and the cached report snapshots are removed (subject to the backup window in Section 5).

Limited Use. Omniposter’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google’s own handling of your data is governed by the Google Privacy Policy.

4.7 Publishing destinations (only if you connect them)

  • WordPress sites you own. When you connect a WordPress site, the Service authenticates to its REST API using the Application Password you supply and publishes posts, manages users, and uploads media to that site. The Service does not read your WordPress site content beyond what is necessary to publish and manage authors.
  • X (Twitter, Inc.), LinkedIn (Microsoft / LinkedIn Corp.), Meta (Facebook, Inc.) — Pages and Instagram Business accounts. When you authorize a connection (either by supplying API credentials or by completing an OAuth flow), we transmit the post content, images, and any metadata to that platform on your behalf and read back post-level metrics the platform returns. The data you transmit and any data returned are also governed by that platform’s privacy policy and developer terms.

4.8 Other disclosures

We may also disclose your information when we believe in good faith that disclosure is necessary to:

  • Comply with applicable law, legal process, or a binding governmental request;
  • Enforce our Terms of Service or other agreements;
  • Protect the rights, property, or safety of Omniposter, our users, or the public;
  • Investigate or prevent fraud, abuse, security incidents, or violations of our policies;
  • Effect a business transfer (merger, acquisition, financing, reorganization, bankruptcy, sale of assets), in which case we will require the successor to honor this Privacy Policy with respect to your information.

5. Data retention

  • Account data is retained while your account is active and for up to 90 days after termination or cancellation, after which it is deleted or anonymized except as required for tax, accounting, fraud prevention, or other legal-compliance purposes (typically up to 7 years for financial records).
  • Generated content (stories, posts, researchers) is retained while your account is active. You may delete individual items at any time. On account termination, content not already exported by you is deleted within the 90-day window.
  • Audience (reader) data (Section 2.4) is kept until the reader erases it, the publisher deletes it, or the publisher’s project is deleted, whichever comes first. Turning the Audience feature off stops new sign-ups and comments but does not delete existing data. When a project is deleted, its reader data is deleted from Cloudflare D1 as well. The consent evidence on a reader’s record (when they consented, the text-message wording they were shown, and their IP address and user-agent at sign-up) is kept for as long as that record.
  • One-time codes and sign-in links expire 15 minutes after they are sent and can be used only once. The record of each code or link we sent (the address, the IP address and user-agent of the request, and the consent shown) is deleted automatically 30 days after it was sent, or sooner if the reader erases their data or the project is deleted.
  • Google sign-in records (Section 2.4) are deleted automatically within 2 days. The keyed hash of the IP address of a reader who reports a comment is deleted within about a day.
  • The records of which readers opened or clicked a newsletter issue (Section 2.4) are deleted automatically 30 days after the issue was sent.
  • The one-way hashes that keep a banned reader banned (Section 2.4), of their email addresses, phone numbers and linked Google accounts, are kept until the publisher lifts the ban, which deletes every hash that ban created, or the project is deleted.
  • Third-party tokens and credentials are encrypted at rest and are deleted immediately when you disconnect the integration, when the credential is rotated or revoked, or on account termination.
  • Backups may retain otherwise-deleted information for up to 35 days after deletion.
  • Server logs are retained for up to 90 days.
  • Audit logs of payment events are retained for up to 7 years as required for tax and accounting purposes.

6. Security

We take reasonable administrative, technical, and physical measures to protect your information, including:

  • Encryption in transit (HTTPS / TLS) for all client-server communication;
  • Authenticated encryption at rest (Fernet) for sensitive credentials and tokens;
  • Salted, hashed passwords (Argon2 / bcrypt) — we cannot recover your password and will never ask for it;
  • Strict tenant isolation — every database query in the Service is scoped to the requesting user;
  • Hosted by infrastructure providers with documented SOC 2 controls;
  • Principle-of-least-privilege access for our personnel.

No method of transmission or storage is 100% secure. We cannot guarantee absolute security, and you use the Service at your own risk. If we become aware of a security incident affecting your information, we will notify you in accordance with applicable law.


7. Your choices and rights

Depending on your jurisdiction, you may have some or all of the following rights with respect to your personal information:

  • Access. Request a copy of the personal information we hold about you.
  • Correction. Ask us to correct inaccurate or incomplete personal information.
  • Deletion. Request that we delete your personal information, subject to legal retention requirements.
  • Portability. Request a machine-readable export of your account data.
  • Restriction or objection. Ask us to restrict or object to certain processing.
  • Withdrawal of consent. Where processing is based on consent, withdraw your consent at any time.
  • Lodge a complaint with a supervisory authority (e.g., your local data-protection authority in the EU/UK, or your state attorney general in certain US states).

To exercise any of these rights, email dev@omniposter.ai from the address associated with your account. We will respond within the timeframes required by applicable law (typically 30 days).

You can also manage many of these rights yourself from the Service: delete individual stories, posts, researchers, and projects; disconnect integrations; rotate or remove AI keys; and cancel your subscription. Account deletion can be initiated by emailing us until in-app self-service deletion is available.


8. Cookies and similar technologies

We use a small number of strictly-necessary cookies and browser storage items, including:

  • An authentication cookie that holds a signed session token so you stay logged in;
  • Local storage to remember non-sensitive UI preferences (e.g., which tab you last viewed).

On publishers’ sites that use Audience, our embed script stores the following in the reader’s browser. Everything is first-party storage on the publisher’s own site:

  • a reader sign-in token, valid for one year, in local storage and in a first-party cookie (omni_r_…), so the reader stays signed in on that site;
  • the list of articles the reader has opened on that site, used to count free articles before a registration wall. This list stays in the browser and is not sent to us;
  • when the reader last dismissed a sign-up form, so it is not shown again too soon, plus a short-lived cache of the site’s form settings.

These items work only on the publisher’s site that set them. They are not used to track readers across sites.

We do not use advertising cookies, third-party analytics trackers on the Service itself, or cross-site tracking technologies. We do not respond to “Do Not Track” browser signals because there is no consensus standard, but our default behavior is consistent with the intent of that signal: we don’t track you across other sites.


9. International data transfers

The Service is operated from the United States. If you access the Service from outside the United States, your information will be transferred to, stored, and processed in the United States and in other countries where our sub-processors operate. By using the Service you consent to these transfers. We rely on standard contractual clauses or other lawful transfer mechanisms where required.


10. Children’s privacy

The Service is intended for use by businesses and is not directed to children under the age of 16. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with personal information, please contact us and we will delete it.


11. California, Virginia, Colorado, and other US state-specific notices

To the extent any US state privacy law (CCPA/CPRA, VCDPA, CPA, etc.) applies to you, you have the right to know, access, delete, correct, opt out of certain processing, and not face discrimination for exercising your rights. We do not “sell” your personal information as that term is defined in those statutes, and we do not engage in “targeted advertising” or “profiling” with significant effects. To exercise any state-specific right, email dev@omniposter.ai.


12. European Economic Area, United Kingdom, and Switzerland

If you are in the EEA, the UK, or Switzerland, our legal bases for processing your information are: (a) performance of a contract with you; (b) our legitimate interests in operating, securing, and improving the Service; (c) compliance with legal obligations; and (d) your consent where required. Omniposter is the controller of your personal information for the purposes of GDPR and equivalent laws.

Reader data from the Audience feature is different. For the personal data of readers who sign up or comment on a publisher’s site (Section 2.4), the publisher is the controller and Omniposter is a processor acting on the publisher’s documented instructions. Readers should send requests about that data to the publisher; if they contact us, we will pass the request on and help the publisher respond.

You may contact your local supervisory authority. We do not currently have an EU representative under Article 27; if and when that requirement applies to us we will update this Policy.


13. Changes to this Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date at the top of this Policy and, for material changes, give you reasonable advance notice by email and/or via a notice in the Service. Your continued use of the Service after the effective date constitutes acceptance of the updated Policy.


14. Contact

For questions, requests, or concerns about this Privacy Policy or our handling of your information, contact:

Omniposter Email: dev@omniposter.ai