Privacy Policy
Last updated 30 October 2026
This policy explains what personal data Postyard collects, why, who it is shared with, how long it is kept and what rights you have. It covers the website at postyard.app, the application at app.postyard.app, public booking pages and short links served by Postyard, and Postyard's integrations with Facebook, Instagram, LinkedIn and Google.
Who we are
Postyard is operated by Jagu s.r.o., ID No. (IČO) 28426126, registered office Tisem 22, 257 56 Tisem, Czech Republic ("we", "us"). For anything about your data, write to hello@postyard.app.
Two roles we play
We are the controller of the data about the people who use Postyard: your account, how you sign in, the channels you connect and how you use the service.
We are a processor for the content a workspace puts into Postyard about other people: contacts and companies in the CRM, people who book a meeting on a booking page, people who comment on the workspace's social media posts, stand-up notes, offers and the like. The organisation that owns the workspace decides what goes in and why, and is the controller of that data. If you are such a person and want to exercise your rights, contact that organisation; we will help them answer you.
What we collect
Your account
- Name, e-mail address and profile picture.
- A password, stored only as a one-way hash — or, if you sign in with Google or GitHub, the basic profile those services share with us (name, e-mail, picture).
- The workspaces and teams you belong to and your role in them.
What you create in Postyard
Posts, captions, images and other uploaded files, comments, schedules, stand-up updates and notes, CRM records, offers, contact-card and signature designs, short links and anything else you or your colleagues enter.
Connected social accounts (Facebook, Instagram, LinkedIn)
A workspace can connect Facebook Pages, Instagram professional accounts, LinkedIn company pages it administers and the LinkedIn profile of the person connecting. When it does, we receive and store:
- The access token the network issues, so Postyard can act for the account when a member of the workspace asks it to.
- The identifiers, names, handles and profile pictures of the connected accounts, and their follower and post counts.
- The accounts' posts — captions, images and videos, publish times and permalinks — including posts, reels and stories published outside Postyard. Images and videos are copied into our storage, because the links the networks provide expire.
- Statistics of those posts and accounts: likes, comments, shares, saves, views, reach, clicks and followers, as the network reports them, so Postyard can show how the posts performed.
The permissions we request are listed on the network's consent screen before you agree. Facebook: list your Pages, read their posts, comments, engagement and statistics, publish posts and reply to comments. Instagram: basic profile, publish content, read insights, and read and reply to comments. LinkedIn: your basic profile; publish posts as you or as the company pages you administer; read those pages' posts, comments, statistics and follower counts; and reply to comments.
People who comment on connected accounts' posts
For posts published from a connected account, Postyard reads the comments left under them so the workspace can see and answer them in one place. For each comment we store its text, time and number of likes, the commenter's name and handle where the network provides them (LinkedIn does not share a member's name with page tools, so a LinkedIn commenter is shown as "A LinkedIn member"), whether the account has already replied, and any reply a member of the workspace drafts. A reply is published only when a member of the workspace presses Send reply — never automatically. This data is processed on behalf of the workspace whose account it is.
Google Calendar (booking pages)
If you connect a Google account for bookings, we store its access and refresh tokens and the account's e-mail address. We read which times are busy in the calendars you choose and create, update and delete the events for meetings booked through Postyard. We do not read the content of your other events.
People who book a meeting
Name, e-mail address, the answers to the booking form, the chosen time and time zone, and the language of the page. This is processed on behalf of the workspace whose page it is.
Short-link clicks
When someone opens a Postyard short link we record the time, the referring site, browser, operating system, device type, language, the UTM tags in the address and the country. The country is looked up from the IP address on our own server; the IP address itself is never stored. To count unique visitors we keep a keyed hash that changes every day and cannot be linked back to a person or across days.
The AI assistant and AI connections
If you use the AI assistant, your messages and the workspace data needed to answer them are sent to our AI provider to generate the reply. If you connect an AI client (for example Claude) to Postyard, it can read what your workspace allows it to — including comments on your posts, so it can suggest replies — and we record which client it was and what it read or changed, so your workspace can review it. A suggested reply is only a draft until a person sends it.
Technical data
Server logs of requests to the application (time, address requested, response, browser), kept to run the service securely and to fix faults.
The website
postyard.app uses one necessary cookie to remember your cookie choice. With your consent it also uses Microsoft Clarity to understand how visitors use the site. You can change your choice at any time with "Manage cookies" at the bottom of every page.
Why we use it, and on what legal basis
- To provide Postyard — your account, your workspaces, publishing and reading your connected accounts, bookings, links, e-mails the service sends. Basis: performance of our contract with you (Art. 6(1)(b) GDPR).
- To keep the service secure and working — logs, abuse prevention, error investigation. Basis: our legitimate interest (Art. 6(1)(f) GDPR).
- Website analytics — only with your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.
- To meet legal obligations, such as accounting and tax records (Art. 6(1)(c) GDPR).
We do not sell personal data, we do not use it for advertising, and we do not use data received from Facebook, Instagram, LinkedIn or Google for any purpose other than providing the features you asked for.
Data from Meta, LinkedIn and Google
- It is shown only to the members of the workspace that connected the account, used only to provide Postyard's features, and never sold, rented or shared with data brokers.
- Disconnecting an account in Postyard (Accounts → the account's menu → Disconnect) deletes its access token immediately. Removing the account from the same menu also deletes the stored account record, its statistics and the comments read from it. Posts imported from it stay in the workspace until a member deletes them. You can also remove Postyard's access from the network's own settings at any time.
- Postyard's use of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Who we share it with
We use the following service providers, each bound to process data only on our instructions:
| Provider | What for | Where |
|---|---|---|
| DigitalOcean | Servers, database and file storage | EU (Frankfurt) |
| Resend | Sending the service's e-mails | USA |
| Anthropic | The AI assistant | USA |
| Microsoft (Clarity) | Website analytics, with consent | USA |
| Meta, LinkedIn, Google, GitHub | Only when you sign in with or connect them, to provide that feature | USA / EU |
Transfers outside the European Economic Area rely on the EU–US Data Privacy Framework where the provider is certified, or on the European Commission's standard contractual clauses. We may also disclose data where the law requires it.
How long we keep it
- Account and workspace content: for as long as the account or workspace exists.
- Social and calendar access tokens: until you disconnect the account.
- Comments on connected accounts' posts and the replies drafted to them: until the post or the account is removed from Postyard.
- Short-link clicks: for as long as the link exists.
- Server logs: for a limited period needed to run and secure the service.
- Invoices and accounting records: for the period required by Czech law.
When you ask us to delete your account, we delete or anonymise your personal data within 30 days, except where we are required by law to keep it. Deleted data may persist in backups for a short time until they are overwritten.
Your rights
You have the right to access your data, have it corrected or deleted, restrict or object to its processing, receive it in a portable format, and withdraw consent at any time. To exercise any of them write to hello@postyard.app. How to delete your data is described step by step on our data deletion page.
You also have the right to lodge a complaint with the Czech data protection authority, the Úřad pro ochranu osobních údajů (uoou.gov.cz), or the authority in the EU country where you live.
Security
Data is transmitted over HTTPS, passwords and API tokens issued by Postyard are stored only as hashes, and access to workspace data is limited to the workspace's members according to their role and team.
Children
Postyard is a business tool and is not intended for anyone under 16.
Changes to this policy
If we change this policy we will update the date at the top, and tell account holders by e-mail or in the application when the change is significant.