Third-Party Services

Postelio relies on third-party services to provide infrastructure, artificial intelligence functionality, email delivery, backups, website analytics, and integrations with external platforms.

The services that apply to you may depend on the Postelio features, AI providers, and connected platforms you choose to use.

This page provides information about the principal third-party services currently used by Postelio. It may be updated as our infrastructure and integrations change.

1. Hosting and Infrastructure

Zomro

Purpose: Hosting of Postelio's primary application infrastructure.

Processing: Postelio's application servers and supporting infrastructure are hosted on infrastructure provided by Zomro.

Location: The primary Postelio server is currently hosted in the Netherlands.

The categories of data processed through this infrastructure may include account information, workspace data, content, publishing data, integration configuration, technical information, and other information necessary to provide the Service.

2. Cloud Storage and Backups

Amazon Web Services (AWS)

Service: Amazon Simple Storage Service (Amazon S3)

Purpose: Storage of production backups.

Current region: Europe (London) — eu-west-2, United Kingdom.

Production backups may contain information stored in Postelio's production systems at the time a backup is created.

Because the backup region is located in the United Kingdom, backup processing may involve a transfer of personal data outside the European Economic Area.

Where required, such processing is subject to applicable data-protection safeguards.

3. Email Services

Google Workspace

Purpose: Business email and customer communications.

Postelio uses Google Workspace for email sent to and received from the public Postelio contact address and for operational or support communications.

If you contact Postelio by email or through the website contact form, your name, email address, message, and related correspondence may be processed through Google Workspace.

4. Artificial Intelligence Providers

The AI provider used for a particular operation depends on your Postelio configuration.

Postelio may provide managed AI functionality, and users may also connect supported AI providers using their own credentials.

OpenAI

Purpose: AI content generation and, where supported and configured, AI image generation.

Information sent to OpenAI may include prompts, topics, instructions, existing content, generation settings, images or other context necessary to perform the generation requested by the user.

OpenAI may be used through Postelio-managed AI configuration or through a user's own supported provider connection, depending on the available configuration.

Google Gemini

Provider: Google

Purpose: AI content generation.

Information sent to Google Gemini may include prompts, topics, instructions, existing content, generation settings, and other context necessary to perform the generation requested by the user.

Some optional generation functionality may use additional provider features such as Google Search grounding. Where such functionality is enabled, additional processing by Google may occur.

Google Gemini may be used through Postelio-managed AI configuration or through a user's own supported provider connection, depending on the available configuration.

Bring Your Own AI

If you connect your own AI provider credentials, Postelio sends generation requests to the provider you selected.

Your use of that provider is also subject to your own agreement with the provider, including its terms, privacy practices, pricing, quotas, and data-processing arrangements.

5. Connected Social and Communication Platforms

Postelio processes information through a connected platform only when you configure or use the relevant integration.

Connected platforms operate under their own terms and privacy practices.

Telegram

Purpose: Publishing content to Telegram channels or chats configured by the user.

Depending on the integration, Postelio may transmit generated or user-provided text, images, media, and publishing instructions to Telegram.

Postelio may process the bot credentials and destination identifiers required to perform publishing operations.

X (Twitter)

Purpose: Publishing content to X accounts connected by the user.

Postelio may process authorization tokens, account identifiers, authorization information, text, media, and publishing-related information necessary to perform requested publishing operations.

Threads

Provider: Meta Platforms

Purpose: Publishing content to Threads accounts connected by the user.

Postelio may process authorization tokens, account identifiers, text, media references, and publishing-related information necessary to perform requested publishing operations.

Threads lifecycle deletion processing is currently under verification and mutation is disabled. Postelio does not remove Threads credentials or stored Threads account identity while that verification is incomplete.

Once activated after verification and product/legal sign-off, if Meta requests deletion of a connected Threads account, Postelio removes the active Threads OAuth credentials and the stored Threads account identity for that connection. Channel rows, the customer-authored channel name, publication history (including provider message identifiers and provider responses), and campaign-target records may be retained as Postelio customer business records. This is not a claim that all Meta or Threads user data is deleted.

6. Website Analytics

Google Analytics 4

Provider: Google LLC

Purpose: Measurement of visits to the Postelio website and application. The Google Analytics tag loads on measured pages regardless of your choice, in a mode where storage is denied until you accept optional analytics cookies.

While storage is denied, Google Analytics does not read or write first-party Analytics cookies, and the resulting measurement events are not associated with a persistent Google Analytics user identifier. One or more cookieless measurement requests may still be sent to Google as you use the page, and may transmit technical and event data: a random value generated for the page load, the IP address inherent to the connection, the browser user-agent, screen and device information, the page path in a normalized form that excludes account identifiers and query parameters, a sanitized referrer or no referrer, and a page title derived from that same normalized path.

After you accept, Analytics cookies such as _ga are set and measurement continues with a persistent identifier. Postelio does not send email addresses, usernames, or other account identifiers to Google Analytics. Advertising storage, advertising user data, and advertising personalization remain denied at all times.

You can change or withdraw that choice through Cookie settings.

Further information is available in our Privacy Policy.

7. Your Choice of External Services

Not every third-party service listed on this page necessarily processes data relating to every Postelio user.

For example:

• an AI provider processes generation data only when that provider is used for a generation operation;
• a connected social platform processes publishing data only when you connect and use that platform;
• Bring Your Own AI providers depend on the provider you choose.

Some infrastructure and operational providers may process information as part of the general operation of Postelio regardless of which optional integrations you use.

8. Third-Party Terms and Privacy Practices

Third-party services operate under their own terms, privacy policies, and data-processing arrangements.

Where a third-party service acts as a processor on behalf of Postelio, we use applicable contractual or other safeguards where required by data-protection law.

Where you independently connect or use a third-party service, your own agreement with that provider may also apply.

Postelio does not control changes made by third-party providers to their services, terms, APIs, processing locations, or privacy practices.

9. Changes to This List

We may update this page when:

• a new material service provider is introduced;
• an existing provider is replaced or removed;
• the purpose of a provider materially changes;
• relevant processing locations change; or
• our integrations or infrastructure change.

Updates to this list do not necessarily require changes to the Privacy Policy where the underlying purposes and principles of processing remain unchanged.

Material changes to our processing practices will be reflected in the Privacy Policy where appropriate.