Last updated: November 2, 2026
Privacy Policy
This policy explains what Postalrios collects, why it is used, which providers help process it, and how account and generation data are handled.
Service provider
AGAPIE ARISTOTEL-IOAN PERSOANĂ FIZICĂ AUTORIZATĂ
Romanian tax identification number (CUI): 52393158. Trade register number: F2025031262003.
B-dul Bucureștii Noi, 136, parter, ap. 5, Sector 1, București, 012366, Romania.
Contact: office@postalrios.com.
AGAPIE ARISTOTEL-IOAN PERSOANĂ FIZICĂ AUTORIZATĂ is the controller of the personal data described in this policy.
1. Overview
This Privacy Policy explains how Postalrios collects, uses, stores, and shares information when you use the website, application, billing flow, AI generation workflows, and LinkedIn-related features.
The service provider named above is the controller of your personal data processed through Postalrios. Contact office@postalrios.com about this policy or your personal information.
2. Information we collect
We collect account information such as your email address, authentication identifiers, role, plan, account status, and settings.
When you sign up, we check whether your new account repeats an earlier free trial. We compare keyed hashes (HMAC-SHA256 with a secret key) of the IP address you signed up from (for IPv6, its /64 network) and of your email address in a normalized form (lowercase, without a +tag, and for Gmail without dots) with those of earlier free trials. We store these hashes, never the addresses themselves, only if your account receives the free trial, and we store whether it did.
If you submit a withdrawal declaration, we store your name, confirmation email, contract details, submission time, acknowledgement delivery state, and resolution so we can handle the request and demonstrate receipt.
We collect content you provide or generate, including areas, topics, prompts, custom instructions, post drafts, carousel text, generated image prompts, generated images, scheduling information, and publishing history.
When Creator Insights is enabled, we store your feed settings, public trend-source titles, short excerpts and links, recommendations, confidence information, and automation history. We do not scrape LinkedIn or store full third-party articles.
We collect usage and operational information such as generation counts, image counts, token usage, provider/model metadata, job status, errors, logs, device/browser metadata, IP-derived security signals, and timestamps.
When you arrive at our public site, postalrios.com, our server reads the campaign tags of the link you followed (utm_source, utm_medium, and utm_campaign) and the domain name of the site that sent you, as your browser reports it (such as linkedin.com, never the page's address). We count visits per day by the kind of site that sent them (such as LinkedIn, a search engine, or an AI assistant) and by campaign tag; these counts hold nothing about you. If you go on to sign up, the links on our pages carry where you came from to sign-up and back to the app, in the address Clerk, our sign-in provider, returns you to, and we store it once with your new account. We also store when you first use Postalrios again 7 days or more after signing up.
Only if you allow it, your browser measures how fast Postalrios is for you: how quickly pages load and respond, how long each kind of app request takes and whether it succeeded, and the size, cache use, and connection protocol of the app's own files and requests. A page's own loading is measured only if, when our server received the request for that page, you had allowed measurement 10 minutes or more earlier by our server's clock, and your choice has not changed since. These numbers are labelled only with the kind of page and request, never with page addresses, request contents, or identifiers of you, your account, or your device, and we keep them only as aggregate statistics. We store your choice and when you made it with your account. You can change it at any time in Settings.
If you set up AI integrations, we store for each API key its name, permissions, and when it was created, last used, and expires, with a fingerprint of the key (a SHA-256 hash) instead of the key itself; for each AI app you connect, its client identifier at Clerk, its permissions, and when it was connected and last used. We keep a record of each change it makes and of each of its actions that we refuse or that fails, including attempts at actions its permissions do not include: the action, the post when known, and the outcome, without the post's text. A request that names none of our actions changes nothing and is recorded only in our server logs. When a revoked or expired key or app is used, we keep a record that it was used, at most once an hour per key or app. Its successful reads, and the other uses of revoked or expired keys, are recorded only in our server logs (section 7, logs and security records).
If you connect your LinkedIn company pages, we store the pages LinkedIn lists you as an administrator of (each page's LinkedIn ID, name, and public page name, your role, and when we last checked it), which of them you turn on for posting, and which of your posts each page publishes. For your pages' posts, we store the organic statistics LinkedIn reports for them: impressions, clicks, reactions, comments, and reshares. While a page has a campaign, we also store its daily follower gains, organic and paid, as LinkedIn reports them.
If you use campaigns, we store each campaign's brief (its name, goal, audience, key messages, call to action, voice notes, and the facts about your team you add), its storyline, and the AI reports you ask for. Facts about your team can name people: add only what they have agreed to share. When you add a post your page made on LinkedIn to a campaign, we copy the post's text, format, publication time, and link from LinkedIn.
When you submit feedback, we store your report and delivery status. If you include diagnostic details, we attach browser family and major version, viewport size, timezone offset, connection status, and up to ten recent failed app request names and bounded error codes. You can inspect or omit these details before submission. The report and included diagnostics are shared with our team through GitHub. This diagnostic collection does not capture request contents, raw error messages, credentials, or browsing history.
We receive payment and subscription status from Clerk Billing and Stripe, such as plan, checkout status, subscription status, billing events, and payment outcome. We do not store full payment card numbers.
When you subscribe, we record the statements you confirm before checkout, when you confirmed them, the plan, price, VAT status, seller details and terms versions shown to you, and the email address we send your contract confirmation to, with its delivery status.
Where this information comes from
Most of this information comes from you, or is created when you use Postalrios. The rest comes from these sources: Clerk, when you sign up or sign in (your email address and sign-in identifiers, and, if you sign in with LinkedIn, the LinkedIn access token we use to publish at your request); LinkedIn, when you publish or connect LinkedIn analytics (your member ID and the metrics of your own Postalrios-published posts) or your company pages (the pages you administer and your role, their posts' statistics and daily follower gains, and the page posts you add to a campaign); Clerk Billing and Stripe (payment and subscription status); and public sources for Creator Insights and research: Hacker News, the feeds you add, and, when enabled, GDELT news data and web search results. Those public items can include the names of their authors or of people they mention. We keep only titles, short excerpts, and links, for the periods in section 7.
What you must provide
You need to give us an email address to create an account. To buy a plan, you need to give the billing details Romanian tax law requires on an invoice. Without them we cannot open your account or sell you a plan. Everything else, such as your content, instructions, feeds, feedback diagnostics, performance measurement, and LinkedIn connections, is up to you; if you leave something out, only the feature that needs it will not work.
3. Connected services
If you connect LinkedIn or another third-party account, we may receive access tokens, account identifiers, posting status, publishing metadata, and error messages needed to provide the connected workflow.
If LinkedIn creator analytics is enabled and you grant the required permission, we encrypt the Community API access token and temporarily store aggregate numeric metrics only for your own Postalrios-published posts. Disconnecting analytics deletes the stored Community API token. We do not retrieve comments, reactions, other member profiles, or LinkedIn posts other than your company pages' own (below).
If you connect your company pages, the same connection also gets LinkedIn's permissions to publish as, and read the statistics of, the pages you administer. We use them only for those pages: to list them and check your role, to publish the posts you schedule for a page, to read the statistics of the page's posts and its daily follower gains, and, when you look for earlier posts to add to a campaign, to read the page's own posts.
Your use of connected services is also subject to those third parties' privacy policies and terms.
4. How we use information and why
This table lists each purpose, the information we use for it, and the legal basis under the GDPR. Section 7 says how long we keep each kind of information.
| Purpose | Information | Legal basis |
|---|---|---|
| Providing Postalrios: your account, generating and storing drafts and images, scheduling and publishing to LinkedIn at your request, Creator Insights when you enable it, and support | Account information, your content, connected-service data, usage information | Performing our contract with you (Art. 6(1)(b)) |
| AI integrations, if you set them up: letting the AI assistant you connect read your posts and create, schedule, or publish them with the permissions you give it, and showing you what it did | Your content, API key fingerprints and connection identifiers, permissions, and records of changes and refused actions | Performing our contract with you (Art. 6(1)(b)) |
| Company pages and campaigns, if you use them: publishing as your LinkedIn pages, planning campaigns, measuring their posts, and writing the reports you ask for | Your pages and role, campaign briefs and team facts, your pages' posts, their statistics, and follower gains | Performing our contract with you (Art. 6(1)(b)) |
| Plans, credits, and payments: checkout, subscriptions, and plan limits | Account, subscription, and payment status | Performing our contract with you (Art. 6(1)(b)) |
| Checkout confirmations: recording the statements you confirm before checkout, emailing your contract confirmation, and keeping them after account deletion | Confirmed statements, time, plan and price shown, billing email, and delivery status | Complying with consumer protection law (Art. 6(1)(c)), and our legitimate interest in establishing, exercising, or defending legal claims (Art. 6(1)(f)) |
| Invoicing and tax: issuing invoices, reporting them to ANAF through RO e-Factura, and keeping accounting records, including after you delete your account | Billing details, invoices, and payments | Complying with Romanian tax and accounting law (Art. 6(1)(c)) |
| Withdrawal declarations: handling a declaration, proving we received it, and keeping it after account deletion | Name, confirmation email, contract details, and dates | Complying with consumer protection law (Art. 6(1)(c)), and our legitimate interest in establishing, exercising, or defending legal claims (Art. 6(1)(f)) |
| Account emails: receipts, service messages, and notifications about your drafts and publishing, which you can switch off in Settings | Email address and account events | Performing our contract with you (Art. 6(1)(b)) |
| Security and abuse prevention: protecting sign-in, rate limits, security logs, and investigating incidents | IP addresses, account identifiers, and request details | Our legitimate interest in keeping the service and its users secure (Art. 6(1)(f)) |
| Preventing repeat free trials: checking at sign-up whether a new account repeats an earlier free trial, and keeping the records of each trial for that check | Keyed hashes of your sign-up IP address and normalized email address, and whether your account received the free trial | Our legitimate interest in offering one free trial per person and keeping its cost under control (Art. 6(1)(f)) |
| Reliability and cost: statistics about usage, errors, capacity, and provider cost | Usage and operational information | Our legitimate interest in running a reliable and affordable service (Art. 6(1)(f)) |
| Understanding how people find and start using Postalrios: counting visits to our public site by where they came from, and measuring which channels and campaigns bring sign-ups and whether new accounts go on to draft, publish to LinkedIn, buy a plan, and come back | Daily visit counts by channel and campaign tag; where you came from when you signed up, when you first came back, and the dates of your first drafts, LinkedIn posts, checkouts, and payments | Our legitimate interest in knowing which ways of reaching people work and in helping new users get started (Art. 6(1)(f)) |
| Performance measurement, if you allow it: finding what makes pages and requests slow | Page and request speed, sizes, and cache and protocol use, kept as aggregate statistics; your choice and when you made it | Your consent (Art. 6(1)(a)), which you can change at any time in Settings |
| Feedback you send us, with the diagnostics you choose to include | Your report and diagnostics | Our legitimate interest in answering you and fixing problems (Art. 6(1)(f)) |
Where we rely on our legitimate interests, you can ask us for our assessment of why those interests are not overridden by yours, and you can object (section 9).
Postalrios uses AI models to draft posts, carousels, images, and suggestions from what you give it. You review the results and decide what to publish; automatic drafting and scheduling run only when you turn them on. Plan limits and rate limits are applied automatically and can pause or refuse a request. The repeat free-trial check at sign-up is automatic too: an account it matches gets no free credits but can still subscribe. If you think it matched you wrongly, contact office@postalrios.com and we will review it. We do not make decisions about you based solely on automated processing that have legal effects on you or similarly significantly affect you.
5. Who receives information
Postalrios sends prompts, instructions, content context, and related metadata to AI providers when needed to generate text, images, embeddings, or prompt transformations. For a campaign, that includes its brief and team facts when its storyline and posts are written, and, for a campaign report you ask for, its posts' text and LinkedIn statistics.
For every request the Postalrios service sends through OpenRouter with your content, we require routing only to model providers that OpenRouter's published policy data lists as not storing inputs for training. If no such provider is available, the request fails rather than going to one that does. This relies on OpenRouter's provider records, not our own review of each provider, and it is not zero data retention: a provider can still keep request data for a limited period, for example for abuse monitoring or legal compliance, under its own terms. It does not cover the search service OpenRouter uses for web research, or TypeSafe.
Service providers that process information for us
These providers process information on our instructions: Clerk (sign-in, account management, and legacy subscriptions); Stripe Payments Europe, Limited (checkout, subscription billing, tax calculation, and payment processing); Solo (fiscal invoicing and accounting); OpenRouter (routing AI requests to the model providers that generate text and images, and research searches to Parallel Web Systems); TypeSafe (writing review, when that feature is enabled); and Amazon Web Services (encrypted backups, stored in Frankfurt, Germany). We run the application, database, file storage, and email server ourselves, in Romania.
Recipients that decide for themselves
Stripe also acts as a separate controller of the payment data it uses to prevent fraud and to meet its own legal obligations, such as anti-money-laundering checks, under its own privacy policy.
ANAF, the Romanian tax authority, receives the invoices we issue through the RO e-Factura system, as Romanian law requires.
GitHub receives the feedback you submit, with the diagnostics you choose to include, in a private repository we use to track reports. GitHub handles it as a separate controller under its own privacy statement.
LinkedIn is not one of our processors. When you ask Postalrios to publish, we send the post, including its image or PDF, to your own LinkedIn account through LinkedIn's API. LinkedIn Ireland Unlimited Company, our counterparty under LinkedIn's API terms, receives it in the EU and processes it as a separate controller under LinkedIn's own terms and privacy policy. The same applies to the post metrics we request when you connect LinkedIn analytics, and to what we publish as your company pages and the page data we request for them.
The AI assistants you connect through AI integrations, such as Claude, ChatGPT, or Cursor, are not our processors. When yours makes a request, we send it what the request asks for and its permissions allow: your posts, content areas, credit balance, publishing window, and whether LinkedIn is connected, and, if you use company pages and campaigns, your pages' names and your campaigns with their briefs, team facts, and storylines. It does not receive what we read from LinkedIn for your pages: their posts' statistics, follower gains, the posts you added to a campaign from LinkedIn (it sees that they are there, not their text), or campaign reports. Its provider handles that information as a separate controller under its own terms and privacy policy. You can revoke its access in Settings at any time.
We also disclose information when the law requires it, for example to a court or public authority, or when we need it to establish, exercise, or defend a legal claim.
7. Retention
We keep personal information only as long as we need it for the purposes described in this policy. The periods below describe how long we keep each kind of information.
Where you came from: we keep where you came from when you signed up, and when you first came back, with your account while it is open, and delete them with it. Daily visit counts to our public site hold no personal information; we keep them as statistics.
Account and content: we keep your account, settings, areas, topics, drafts, images, uploaded files, schedules, publishing history, feedback, and in-app notifications while your account is open. You can delete drafts and carousels in the app at any time. Deleting one also deletes its images, and removes the copies of its text in our internal job and publishing queues; our monthly retention review removes any copy left over. If our storage cannot remove an image file at that moment, the file stays in your account's storage folder, no longer linked to anything, until you delete your account.
Account deletion: when you ask us to delete your account, we delete your content, schedules, files, preferences, feedback and support emails, notifications, job, usage, and event records, and connected LinkedIn access, and ask our providers to delete the data they hold for us where applicable.
Some information remains after account deletion: billing, tax, and legal records; encrypted backups, until they expire; server logs, until they are overwritten or deleted as described under logs below; operational and security records not linked to the account, such as rate-limit records keyed by IP address; free-trial records (keyed hashes of the sign-up email and IP address), until they expire; and copies held by providers under their own terms. Each is described below. We restrict what remains and remove your sign-in, so it cannot be used to operate the account.
Billing, tax, and legal records: records we need for accounting, tax, and possible legal claims, such as your billing profile, subscription and payment history, invoices and other fiscal documents, credit ledger, checkout confirmations, and withdrawal declarations, are kept for five years after the contract ends or any withdrawal request is resolved, whichever is later. We delete them at our first monthly retention review after that. We keep them longer only where Romanian accounting or tax law requires it, or while we need them for a dispute, legal claim, or audit. Our monthly accounting exports, which list all customers' invoices and billing details for one month, are the business's bookkeeping records: we keep each one until five years from 1 July of the year following the month it covers, longer only under a legal hold, and then delete it.
Free-trial records: when your account receives the free trial, we keep the keyed hash of your sign-up IP address for 30 days and the record with the keyed hash of your email address for 12 months after you signed up, even if you delete your account sooner, so that deleting and re-creating an account does not start a new trial. An automatic job deletes them hourly as each period ends. Whether your account received the free trial is kept with your account.
AI integrations: we keep an API key's record until it expires or you revoke it, and then for 90 days; a connected AI app's record while your account is open, so that an app you revoked stays refused; the records of their changes, refused or failed actions, and hourly records of revoked or expired key uses for 90 days; and, for each post or campaign your AI created, the request key it sent and the post's or campaign's ID for 90 days, so that a repeated request does not create or charge for it again.
Company pages and campaigns: we keep the list of your pages and your campaigns with their storylines while your account is open, until you delete a campaign. Deleting a campaign also deletes its reports and the posts you added to it from LinkedIn, and taking such a post out of a campaign deletes our copy of it; the posts written in Postalrios stay. What we read from LinkedIn for your pages is kept at most 180 days from when we read it: your pages' post statistics, their daily follower gains, and the posts you added to a campaign from LinkedIn. A campaign report is deleted when the first of the LinkedIn data it was written from is, or when any post it read is deleted. An automatic job deletes them hourly as each period ends.
Creator analytics for your Postalrios-published posts remain active for up to 90 days. After that, the metrics are archived for up to one year and then deleted. You can manually unarchive a post's insights during the archive period; doing so resets that data point's 90-day active period. Trend metric snapshots expire after seven days. Recommendations expire after 30 days unless they became a topic or draft in your account; those stay until you delete that topic or draft. Normalized trend items are kept for up to 30 days, or longer while such a recommendation cites them as evidence. An automatic job removes this data hourly as each period ends, whether or not Creator Insights is enabled.
Logs and security records: server logs and internal job, error, and security records can include IP addresses, account identifiers, and request details. We use them to secure the service, prevent abuse, and investigate problems. Our application and gateway servers keep their logs in rotating files limited to 50 MB per server component, so older entries are overwritten as new ones arrive, and each new release of the service deletes the previous release's logs on those servers. Copies of these logs, and of our proxy's access logs, are also sent to our own monitoring server, which deletes them 14 days after receiving them. If a new release fails its health checks, the last lines of these logs are copied into our build server's record of that release, so we can find the cause, and deleted with it after 30 days. When you delete your account, we delete the job, usage, event, and rate-limit records linked to it. Database, proxy, and mail server logs, emails from people without an account, and records we cannot link to your account have no fixed deletion period yet.
Backups: encrypted backups are stored in the EU and deleted automatically. Daily copies are removed within about 60 days, weekly copies within about 24 weeks, and monthly copies within about two years. Deleted information remains in older backups until they expire. If we restore a backup, we first re-apply the account deletions made since it was taken.
Provider copies: Clerk, Stripe, OpenRouter and the AI model providers it uses, GitHub, and our other providers keep the information they process under their own terms and retention settings.
8. Security
We use reasonable technical and organizational measures to protect information. No online service can guarantee perfect security.
You are responsible for protecting your account credentials and for promptly telling us about suspected unauthorized access.
9. Your rights
Right to object
You can object at any time, on grounds relating to your particular situation, to our use of your information based on our legitimate interests: security and abuse prevention, preventing repeat free trials, reliability and cost statistics, handling feedback, and keeping records for legal claims. We will then stop, unless we have compelling legitimate grounds that override your interests, rights, and freedoms, or we need the information to establish, exercise, or defend legal claims.
Your other rights
Wherever you live, you can ask us for access to your personal data, to correct it, to delete it, to restrict how we use it, and for a copy of the data you gave us in a structured, machine-readable format. You can update some account settings in the application yourself. Send requests to office@postalrios.com.
Where we rely on your consent, for performance measurement, you can withdraw it at any time in Settings (or, while your account is disabled, on the page shown in its place), as easily as you gave it. Withdrawing stops measurement at once in the open tabs of the browser you use, and once our server has your withdrawal, nothing measured after that is sent from your other browsers or devices. It does not affect measurement made before.
Some rights are limited by law. For example, we must keep invoices for the period Romanian law requires even if you ask us to delete them, and we keep the records we need for a dispute or legal claim.
We answer within one month. If a request is complex, or we receive many, we can extend this by up to two further months; we will tell you within the first month and explain why.
Complaints
You can complain to a data protection authority. Our lead authority is the National Supervisory Authority for Personal Data Processing (ANSPDCP), 28-30 G-ral Gheorghe Magheru Blvd., District 1, 010336 Bucharest, Romania; anspdcp@dataprotection.ro; +40 318 059 211; www.dataprotection.ro. You can also complain to the authority in the country where you live, where you work, or where you think the infringement took place.
10. International processing
Postalrios runs its application servers, database, file storage, and email server in Romania. Encrypted backups are stored in Frankfurt, Germany. Some providers process information outside the European Economic Area (EEA), mainly in the United States.
Clerk (sign-in and account management) and GitHub (feedback reports) are certified under the EU-U.S. Data Privacy Framework. The European Commission has found that this framework provides adequate protection for personal data sent to certified U.S. companies (GDPR Art. 45). You can check a company's certification at dataprivacyframework.gov.
Stripe Payments Europe, Limited transfers payment data to Stripe, LLC in the United States, which receives it under the EU-U.S. Data Privacy Framework.
OpenRouter, which routes our AI requests, processes them in the United States. Transfers to OpenRouter rely on the European Commission's standard contractual clauses (controller to processor, GDPR Art. 46(2)(c)) in OpenRouter's data processing agreement, which its terms of service incorporate.
OpenRouter passes each AI request on to a model provider, and research searches to Parallel Web Systems. These process them in the United States or other countries outside the EEA. We have not yet confirmed that OpenRouter's data processing agreement covers them, and we have not identified another safeguard for them. TypeSafe (writing review, when that feature is enabled) processes its requests in the United States, and we have not confirmed a safeguard with TypeSafe either. Ask office@postalrios.com for the current status.
When you publish to LinkedIn or connect LinkedIn analytics or your company pages, we send the post and those requests to LinkedIn Ireland Unlimited Company in the EU, which handles them as a separate controller (section 5). LinkedIn's own transfers outside the EU are covered by its privacy policy.
An AI assistant you connect through AI integrations receives what it requests wherever its provider processes it, often outside the EEA, under that provider's own terms (section 5).
You can ask office@postalrios.com for more information about these transfers, or for a copy of OpenRouter's standard contractual clauses. Using Postalrios does not waive your data protection rights or constitute consent to an otherwise unlawful transfer.
11. Minimum age
You must be at least 18 years old to create an account or use Postalrios.
We do not knowingly collect personal information from anyone under 18. If you believe someone under 18 has given us personal information, contact office@postalrios.com so we can take appropriate action, including deleting it.
12. Changes
We update this Privacy Policy when our processing changes. Before a material change takes effect, such as a new purpose, a new kind of recipient, or a new transfer outside the European Economic Area, we will email every account holder about it, in a message about that change only, no later than 30 days before it takes effect. Smaller corrections take effect when we publish them. The date at the top of this page shows the last update.
13. Contact
Privacy questions or requests can be sent to office@postalrios.com.