PostNest - Privacy Policy

Last updated: October 15, 2026

This Privacy Policy explains how Elledyne Labs, Inc., a Delaware corporation doing business as PostNest ("Elledyne Labs," "we," "us"), collects, uses, and shares personal information when you use our application, websites, and services, including the hosted PostNest Cloud service (the "Service"). Elledyne Labs owns and operates PostNest. This Policy is incorporated into our Terms of Service.

For the purposes of the EU and UK General Data Protection Regulation ("GDPR"/"UK GDPR"), Elledyne Labs is the controller of the personal information about our users described here. For personal information about other people that we process on a customer's behalf - for example, people who comment on a customer's posts, or people named or shown in the drafts, brand material, and media a customer stores in PostNest - Elledyne Labs acts as a processor (a "service provider" under the CCPA) for that customer, under our Data Processing Agreement. Our contact details are in Section 12.

1. A Note on How PostNest Is Designed

PostNest is a web application at app.postnest.io, run on PostNest Cloud, a hosted service we operate on Google Cloud. Where we offer a PostNest desktop application, it is a window onto the same hosted service, and your PostNest data is stored in PostNest Cloud in the same way.

  • Your drafts, brands, and campaigns are stored in PostNest Cloud under your account. They are encrypted at rest, scoped to your account so that no other customer can see them, and kept until you delete them or close your account (see Section 7).
  • PostNest Cloud handles everything that touches a platform. When you connect an account, publish a post, or read your Inbox, PostNest Cloud does the work through each platform's official API.
  • We never see your platform passwords. You connect an account by signing in on the platform's own authorization screen. The platform then gives PostNest an access token.
  • Access tokens never leave PostNest Cloud. They are encrypted with a key held in Google Cloud Key Management Service and are never sent to your browser, the desktop application, or anywhere else.
  • Your browser is yours. When you connect an account, or open a post or comment to act on it yourself, PostNest opens the platform's page in your own browser. PostNest does not automate, read, or collect anything from the platform pages you open.
  • AI runs on infrastructure we control. Drafts are generated by an open-weights AI model that we run ourselves on rented GPU infrastructure (RunPod). Your content is not sent to a third-party AI company.
  • We do not use your content, or data from your connected platforms, to train or fine-tune AI models.

2. Information We Collect

a. Account information. When you register, we collect your name, email address, and authentication credentials, processed through Google Firebase Authentication. If you sign in with Google, we receive basic profile information from Google. If you sign in with a phone number, we collect that number. This account is shared across Elledyne Labs products, so the same profile is used wherever you sign in with it. We also store the fact and version of your acceptance of our Terms and this Policy.

b. Connected accounts. PostNest connects to Facebook Pages, Instagram professional accounts, Threads, X, LinkedIn and TikTok, each through the platform's own sign-in and official API. When you connect a platform account, we receive and store: the access and refresh tokens the platform issues (encrypted - see Section 10); the account's platform identifier, name or handle, and account type; the permissions you granted; and the connection's status and expiry. For Facebook and LinkedIn Pages, we also receive the list of Pages or organizations you manage, so you can choose where to post.

c. Posts, media, and publishing records. When you approve a post for publishing, we receive and store the exact post you approved (its text, media, destination, options, and scheduled time) until it is published or cancelled. Media is held in temporary storage so the platform can retrieve it. After publishing, we keep the platform's identifier and link (permalink) for the post, its status, and any error.

d. Your connected accounts' own past posts. With your permission, when you build a brand, PostNest reads recent posts published by your own connected accounts through the platform's API, to learn your brand's voice. We keep the voice profile derived from them, not an archive of the posts.

e. Comments on your posts. To show your Inbox, we retrieve comments on posts published from your connected accounts through the platforms' APIs. For each comment we store the commenter's username or display name, the comment text, when it was posted, and links to the comment and post. We do not collect other information about commenters, and we do not combine a commenter's comments across different posts, brands, or customers into a profile. See Section 3 for the lawful basis and Section 7 for how quickly this is deleted.

f. Brands, drafts, campaigns, and the material you give us. The material you supply to build a brand (website addresses, documents and images you upload, examples you paste, and answers to the brand brief), and the drafts the AI produces, are processed to provide the Service. Your drafts, your brands (name, voice profile, colours, fonts, and logos), your campaigns, the media you upload, your approvals, and your publishing history are stored in PostNest Cloud for your account, encrypted at rest, until you delete them or close your account (see Section 7). This content may include personal information about other people, such as people named or shown in your posts and media.

When you build a brand from a website, our crawler, PostnestBot, fetches only the public pages of that site, and never social media platforms. It runs on our servers in Google Cloud, so the site sees requests from PostNest's published IP address, not from yours - see our PostnestBot page. Besides plain HTTP requests, it may open the site in an isolated, throwaway headless browser (Chromium) on our servers, to read pages drawn by JavaScript and to show you a live view. That browser has nothing of yours in it: no sign-in, and no cookies kept. It follows robots.txt, only reads pages, and stops if the site shows a bot check. Live view: while a site is being read, you can watch screenshots of the page being read. Only the newest screenshot exists at any time; it is visible only to you; it is deleted when the reading ends (and automatically within minutes if a reading is interrupted); it is kept in a separate database that is never backed up; and it is never logged and never sent to any AI model. Logos we fetch are stored with your brand. Only extracted text, colours, and font names are used to draft your brand; the AI never sees the screenshots. To preview a brand's fonts, the app may load font samples from Google Fonts (fonts.googleapis.com and fonts.gstatic.com), which sends your IP address and the font name to Google.

g. Billing information. Payments are processed by our payment processor, Stripe, which collects your payment details directly. We store your plan, subscription status, billing period, and the Stripe customer and subscription identifiers - never your full payment-card number.

h. Usage information. We record how you use plan-limited features (for example, the number of posts published per platform and AI drafts generated) to apply plan limits and manage platform costs, and we keep security logs of sensitive operations (such as use of access tokens, publishing, and deletions).

i. Analytics (website only). Our website uses Google Firebase Analytics to understand general, aggregated usage, and only after you consent - see Section 9. The PostNest app sends no analytics.

j. Diagnostic logs (opt-in). The PostNest app can send us sanitized diagnostic logs from your browser to help us debug a problem. This is off by default and only happens if you turn it on in Settings. When enabled, it sends warning, error, and fatal log entries only - not your brand or post content. You can delete your uploaded logs at any time. Separately, our servers keep operational and security logs, which do not contain your brand or post content; we keep them as described for security and audit logs in Section 7.

k. Communications and support. If you contact us (e.g., via the contact form or email), we collect your name, email, and the contents of your message. Our website also records a one-time note when a new visitor first arrives - see Section 9(b).

Voice dictation runs entirely in your browser, on your device; audio never leaves the device.

We do not knowingly collect special-category data, and you should not submit it through the Service.

3. How We Use Information, and Our Legal Bases

We use personal information only to provide and protect the Service:

  • To provide the Service - authenticate your account (across Elledyne Labs products); store your brands, drafts, campaigns, and media; connect your accounts; generate drafts; publish the posts you approve, at the time you choose; show your Inbox; and apply your plan's limits. Legal basis: performance of our contract with you.
  • To learn your brand's voice from your own past posts - only when you ask us to. Legal basis: performance of our contract with you, and your consent where a platform or the law requires it. You can withdraw it by disconnecting the account or deleting the brand.
  • To read the public websites you name when you build a brand - only when you ask us to. Legal basis: performance of our contract with you. Where those pages contain personal information about other people (for example, names on a team page), we process it on your behalf, only to produce your brand analysis.
  • To show and help you respond to comments on your own posts - we process commenters' usernames and comment text on behalf of the account holder. Legal basis: the account holder's legitimate interest in reading and responding to comments on their own posts, which commenters can reasonably expect when they comment publicly. We limit this to the minimum fields, keep it only briefly (Section 7), and never use it for any other purpose.
  • To keep the Service secure and reliable - detect and prevent fraud, abuse, and security incidents; keep audit logs; debug problems from logs you chose to send us. Legal basis: our legitimate interests in securing and maintaining the Service.
  • To understand website usage - Legal basis: your consent (analytics), or our legitimate interest (the first-visit record).
  • To provide support and respond to inquiries; to process payments for your plan. Legal basis: performance of a contract.
  • To comply with law, respond to lawful requests, and enforce our Terms. Legal basis: legal obligation, or our legitimate interests.

We do not sell personal information, do not use it for advertising, and do not use your content, or data from your connected platforms, to train or fine-tune AI models.

4. AI Processing

PostNest uses AI to draft brand definitions, posts, and replies to comments.

  • The model. Drafts are generated by an open-weights AI model that we run ourselves, on dedicated GPU infrastructure provided by RunPod. Your content is not sent to a third-party AI company's service, and the model is called only from PostNest Cloud.
  • What the model sees. Only what is needed for the draft you asked for: for example, your brand definition, the material you supplied, your draft, your connected accounts' past posts (when building a brand), or the comment you want to reply to. The model is used only to draft posts and replies for you.
  • No training. We do not use your content, or data from your connected platforms, to train or fine-tune AI models.
  • No retention of prompts or outputs. We do not store the prompts sent to the model, or keep a record of what it returns, after the draft has been returned to you. A draft it produces is saved only as a draft in your account, which you can edit or delete like any other draft. We log only technical measurements (such as size, timing, and which model was used). Our GPU provider keeps a request's result for at most a few minutes so it can be delivered, under a data-processing agreement that limits its use to providing the service to us.
  • Development and testing. Our separate development and testing environment, including any AI service used there, works only with synthetic test data; it never receives your content or data from your connected platforms.
  • AI and LinkedIn. We do not use AI to draft replies to LinkedIn comments. AI may be used only to sort or tag LinkedIn comments (for example, by priority or topic).
  • You decide what is published. AI drafts are labelled, editable, and never published or posted without your action. We do not make decisions about you based solely on automated processing that produce legal or similarly significant effects (GDPR Art. 22).

5. How We Share Information

We do not sell your personal information, and we do not "share" it for cross-context behavioral advertising as that term is defined under the CCPA/CPRA. We share personal information only as follows:

  • Service providers (sub-processors) who act on our behalf, under contract, and only to provide the Service: Google (Firebase Authentication, Cloud Firestore, Cloud Functions, Cloud Run, Cloud Storage, Cloud Tasks, Cloud Key Management Service, Artifact Registry, Cloud Logging, Error Reporting, Firebase Hosting, and Firebase Analytics for the website); RunPod (GPU infrastructure for our AI model); Resend (transactional email); and Stripe (payments). The current list is on our Sub-processors page.
  • Platforms you connect - when you approve a post, we send it to the platform you chose, and we request data from that platform on your behalf. Each platform is an independent controller of the data it receives, under its privacy policy.
  • Other Elledyne Labs products - because your account is shared, your profile information is available to the other Elledyne Labs products you sign in to. Your PostNest content and connected-account data are not.
  • Legal and safety - to comply with law, respond to lawful requests, or protect the rights, safety, and property of Elledyne Labs, our users, or others.
  • Requests from public authorities - we disclose personal information to a government, regulator, or law-enforcement authority only when legally required. We review every request for legality and refuse requests that aren't legally binding; we challenge requests we consider unlawful, overbroad, or in conflict with other laws that protect the data; we disclose only the minimum necessary; we notify the affected customer or user before disclosure unless the law forbids it; and we document every request and our response. We never give any authority direct or bulk access to our systems.
  • Business transfers - in connection with a merger, acquisition, financing, or sale of assets, subject to this Policy.

6. International Data Transfers

We are based in the United States, and PostNest Cloud processes and stores data in the United States. AI drafts are also generated in data centres in the United States. If you access the Service from the EU, UK, or elsewhere, your information will be transferred to and processed in the United States and other countries that may have different data-protection laws. Where required, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum and Swiss equivalents), including those incorporated into our sub-processors' data-processing terms.

7. Data Retention

We keep personal information only as long as we need it for the purposes above:

  • Account information - while your account is active. Your sign-in and profile (name, email address, photo, and billing address) are shared across Elledyne Labs products, so deleting your PostNest account keeps them and you can go on using our other products. Email service@postnest.io to have them deleted too; we do so within 30 days, subject to legal retention requirements.
  • Access tokens and connection details - until you disconnect the account, the platform revokes or expires our access, or your account is closed. Disconnecting deletes the token immediately.
  • Comments in your Inbox - deleted automatically: LinkedIn comments after 24 hours (and in any case within 48 hours), X posts and replies after 7 days, and all other platforms' comments after 30 days. Before you draft a reply to an X post, we check it again and remove it if it has been deleted or made private.
  • Brands, drafts, campaigns, uploaded media, approvals, and publishing history stored in PostNest Cloud - until you delete them or close your account (see "Everything we hold for a closed account" below).
  • Brand Forge live-view screenshots - only the newest one exists at a time, and it is deleted when the reading ends, or automatically within minutes if a reading is interrupted. Screenshots are never backed up.
  • Posts awaiting publication - until they are published or cancelled.
  • Media staged for publishing - deleted 7 days after the post is published (or cancelled).
  • Publishing records (the platform's identifier and link for a published post) - while your account is active, unless the account is disconnected or you or the platform ask us to delete them.
  • Voice profiles derived from your connected accounts' posts - until you disconnect that account or delete the brand.
  • AI prompts and model outputs - not retained by us after the draft is returned (see Section 4). Drafts you save are kept in PostNest Cloud with your other brand data (above).
  • Security and audit logs - for as long as needed for security and compliance.
  • Billing records (plan, subscription status, billing period, Stripe identifiers) - while your subscription is active, and afterwards for as long as tax and accounting law requires. Stripe keeps its own payment records under its privacy policy.
  • Everything we hold for a closed account - deleted within 30 days of account closure. Data we process on your behalf under our Data Processing Agreement, such as Inbox comments and posts awaiting publication, is deleted within 10 days.
  • Backups - we keep daily, encrypted backups of the brand, draft, campaign, media, approval, and publishing data in PostNest Cloud for 14 days, and can restore that data to any point in the previous 7 days. Data you delete, or that we delete on the schedules above, can therefore remain in our backups for up to 14 days after it is deleted. We use backups only to restore the Service after a failure or loss of data. Inbox comments, access tokens, posts awaiting publication and staged media are kept in a separate database and storage that are not backed up, so the deletion times above apply to them exactly.
  • Diagnostic logs, if you have opted in - as long as needed to investigate the issue. You can delete them yourself at any time.
  • Firebase Analytics data (website) - according to the retention period configured in our Firebase settings.
  • Support communications - as needed to handle your request and for our records.

8. Deleting Your Data, and Your Privacy Rights

Deleting your data. You can delete data in several ways (see our Data Deletion page for details):

  • Disconnect an account in PostNest. We revoke and delete its access token and delete the data we obtained from it (comments, publishing records, and its voice profile), and cancel its scheduled posts.
  • Remove PostNest's access in the platform's own settings (for example, Facebook, Instagram, Threads, or TikTok). When the platform notifies us, we delete that account's data the same way. Where Meta sends us a data-deletion request, we confirm it and give you a link to check its status.
  • Delete your PostNest account on the Account page at postnest.io, or request deletion by email to service@postnest.io. We delete everything we hold for your PostNest account within 30 days. Copies in our backups expire as described in Section 7.

a. EU/UK (GDPR / UK GDPR). Subject to conditions and exceptions, you have the right to access, rectify, erase, restrict, and port your personal data; to object to processing based on legitimate interests; to withdraw consent; and to lodge a complaint with your local supervisory authority (in the UK, the ICO).

b. California (CCPA/CPRA). California residents have the right to know/access, delete, and correct personal information, and to opt out of the "sale" or "sharing" of personal information. We do not sell or share personal information as those terms are defined under the CCPA/CPRA. We will not discriminate against you for exercising your rights.

c. Other U.S. states. Residents of certain other states may have similar rights; we honor applicable state privacy laws.

d. If you commented on a PostNest customer's post. We process your username and comment on behalf of the account holder whose post you commented on, and we delete it automatically within the periods in Section 7. You can also email service@postnest.io with a link to your comment, and we will delete our copy. You may also contact the account holder, or contact us and we will help direct your request.

To exercise any right, contact us at service@postnest.io. We will verify your request as required by law and respond within the timeframes the law requires - generally within one month under the GDPR/UK GDPR (extendable by two further months for complex requests) and within 45 days under the CCPA/CPRA (extendable by a further 45 days). You may use an authorized agent where the law permits.

9. Cookies, Tracking, and Your Analytics Choices

Our website uses browser storage for two purposes:

a. Essential authentication. Signing in stores your session in your browser (via Firebase Authentication). This is strictly necessary to provide the Service, does not require consent, and is unaffected by your analytics choice below.

b. First-visit record (no consent required; legitimate interest). The first time a browser loads our site, our server records a one-time note that a new visitor arrived — your IP address and the approximate location derived from it (city/region), your landing page, referrer, browser, language, and timezone. This is a single server-side record (similar to an ordinary server log), used only so we know when new visitors find the site; it is not used for advertising and contains no persistent tracking identifier unless you have approved analytics. A small flag is stored in your browser so we do not record the same browser twice.

c. Analytics — only with your consent. When you first visit, we ask before enabling analytics, and no analytics runs or is stored until you approve. If you approve, we enable Google Firebase Analytics (which sets analytics cookies such as _ga) and store a random analytics identifier in your browser. If you decline, none of this happens, and anything stored under a previous approval is deleted from your browser.

Withdrawing consent is as easy as granting it: use the "Manage analytics consent" control at the bottom of this page at any time. Turning analytics off stops collection immediately and deletes the analytics identifier and cookies from your browser. You can also control cookies through your browser settings.

10. Security

We use administrative, technical, and organizational measures designed to protect personal information, including:

  • Encrypted access tokens. Platform access tokens are encrypted with keys held in Google Cloud Key Management Service, are readable only by PostNest Cloud's own server code, and are never sent to the desktop application or to your browser. Each use of a token is logged.
  • Access controls. Data in PostNest Cloud is scoped to the account it belongs to; you can read your own brands, drafts, campaigns, media, connection status, publishing status, and Inbox, and no one else's. Administrative access is limited and protected with multi-factor authentication.
  • Encryption in transit and at rest for data held in PostNest Cloud, including its backups.
  • AI infrastructure limited to vetted, certified data centres, with request logging turned off, and no customer data stored on its disks.
  • Least data. We collect only the fields we need from platforms, and delete them on the schedules in Section 7.

Anyone who can sign in to your PostNest account can see your brands, drafts, and campaigns, so keep your sign-in secure and the devices you sign in from protected. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. You are responsible for safeguarding your account credentials. If we learn of a security incident affecting your personal information, we will notify you and the relevant authorities and platforms as the law and our agreements require. (We do not claim any formal security certification, such as SOC 2, that has not been completed.)

11. Children's Privacy

The Service is not directed to anyone under 18, and you must be at least 18 to use it (see Terms of Service §1). We do not knowingly collect personal information from anyone under 18, and in no event from children under 13 (or the minimum age of digital consent in your jurisdiction). If you believe someone under 18 has provided us personal information, contact us and we will delete it.

12. Contact Us, and EU/UK Representative

Elledyne Labs, Inc.
17595 Harvard Avenue, Suite C #4001
Irvine, CA 92614
Privacy requests: service@postnest.io

EU/UK Representative and Data Protection Officer. We have not appointed an EU or UK Representative under GDPR/UK GDPR Art. 27, or a Data Protection Officer. If we begin to actively offer the Service to individuals in the EU or UK such that either is required, we will appoint one and update this Section.

13. Changes to This Policy

We may update this Policy from time to time. We will post the updated version with a new "Last updated" date and, for material changes, provide additional notice where required. Your continued use of the Service after changes take effect constitutes acceptance.