Privacy Policy
This policy explains what personal data Artima Socials processes, why, for how long, and what your rights are.
1. Who we are
The controller for customer account data is Artima s.r.o., Company ID: 19658451, VAT ID: CZ19658451, with its registered office at nám. T. G. Masaryka 1281, 760 01 Zlín, Czech Republic, registered in the Commercial Register maintained by Krajský soud v Brně, Section C, Insert 135572 ("we", "us"). We protect personal data under Regulation (EU) 2016/679 (GDPR) and applicable Czech law.
Contact privacy@artima.ai for data-protection questions and requests, support@artima.ai for support, and security@artima.ai to report vulnerabilities.
We have not appointed a data protection officer, because the law does not require one for our processing. For any data-protection question, contact privacy@artima.ai.
2. What Artima Socials is
Artima Socials connects your social accounts to you and to the tools you choose. It connects Facebook Pages, Instagram professional accounts through a Facebook Page or Instagram Login, Threads profiles, and your LinkedIn personal profile and, optionally, the organisation Pages you administer. It carries out your instructions in the app, through the API or through MCP.
Artima Socials contains no artificial intelligence. It does not generate, rewrite, summarise, classify or analyse content or people, and it makes no automated decisions. We do not use any data to train AI or machine-learning models, and we do not send data to AI providers. If you connect your own tools, including AI assistants, through our API or MCP, they act on your behalf and under your responsibility.
It does not score people or content.
3. Our two roles
- Controller: we determine the processing of customer account data, sign-in information, Terms acceptance records, security logs and support correspondence.
- Processor: we process other people's data from your connected networks only on your instructions and for your benefit: commenters, message senders, participant profiles and people appearing in imported posts or insights. You are the controller and decide what happens to that data. Each customer's data is kept separate. Section 11 of the Terms of Service governs this processing.
- Independent controllers: each social network determines its own processing under its own privacy policy.
4. Data we process
4.1 Your account
We store your email, password as an argon2 hash, display name, language, the Terms version and acceptance time, email-verification time and last sign-in. We also store your workspace membership and role, workspace name and contact email, and profile title, description and time zone.
An email address is required to create an account; without it we cannot provide an account. Signup asks for your email and acceptance of the Terms. You set your password through an email-verification link valid for 48 hours. Registration does not ask for your company name, occupation, country, date of birth or age. The confirmation that you are at least 16 is a checkbox; we do not store an age or date of birth.
4.2 Content you create
We process post text, uploaded media, schedules, chosen networks and options, and publication results, including remote post IDs, links, errors and the network's raw response. This lets us publish your instructions and display your history. Unsent Compose drafts stay in your browser; see the Cookie Policy.
4.3 Data from the networks you connect
When you connect, the network asks you to approve permissions. We collect the connected account's platform ID, handle, display name and avatar URL, and access and refresh tokens where issued. Tokens are encrypted with AES-256-GCM. We do not store the Meta user token after connection.
- Facebook Pages: the connecting user's ID and name let us list the Pages they manage; selected Page IDs, names, pictures and Page tokens let us publish, schedule, edit and delete supported own posts, read own posts, comments and reactions, reply to, hide and delete comments, and show Page and post insights.
- Instagram professional accounts: the account ID, username, name, picture and access token let us publish and schedule photos, carousels, reels, videos and stories, read your media, read, reply to, hide and delete comments, and show account and media insights. You can connect through a Facebook Page or Instagram Login.
- Threads profiles: the profile ID, username, picture and access token let us publish and schedule posts, delete own posts, read posts, manage replies and show insights.
- LinkedIn: we store your authenticated member ID, name, profile picture and access tokens, and the IDs, names and logos of organisation Pages you select. We store your connected LinkedIn profile, rather than merely caching it. We collect it when you connect and fetch network data again when you use the relevant features. The data lets us publish, schedule, edit and delete supported posts on your behalf, read available own posts and show available profile, Page and post statistics. Comment and reaction features are currently unavailable; the restrictions in section 7 apply to other members' data.
Available actions depend on the network, account, content type and permissions. Direct messages are described separately below. Posts already on a network that were not published through Artima Socials may be imported into your history as snapshots containing text, permalinks, media URLs, reaction totals and comment counts.
4.4 Comments and insights
Comments and insights are not stored in our database. They are fetched from the network when you open them. Short technical caches last five minutes for taggable users and 120 seconds for mention searches. Reaction and comment counts within imported-post snapshots are the exception: they are stored with those snapshots.
4.5 Direct messages (only if you turn messaging on)
Messaging is off by default for each network and must be switched on. For Facebook Pages and Instagram accounts with messaging enabled, we store participants' IDs, names, usernames and profile-picture URLs, message text, attachments and timestamps to show conversations and let you reply. Participant profiles are refreshed every five minutes for conversations active within the last 30 days.
Automatic replies send only the text you wrote in your settings; we do not generate or supply reply text. Raw Meta webhook deliveries can contain other people's message text and are retained for 30 days.
4.6 Data collected automatically
Server and edge logs contain IP addresses, user agents, request paths with query information redacted, response status and correlation IDs. Rate-limit counters use an IP address or /48 network prefix and, where applicable, a user identifier or keyed email hash. Audit records record who did what, when and with what result; email addresses appear only as keyed hashes.
We use no analytics, tracking, advertising or session-replay tools in the app or on the public site. This is separate from displaying insights supplied by your connected networks.
4.7 API keys, webhooks and connect links
Account API keys and profile key pairs are stored only as SHA-256 hashes, alongside names or labels, prefixes and last-used times. Profile pairs also carry read, write and, if granted, dm permissions. We store webhook endpoint URLs, selected events and encrypted signing secrets, and your allowed redirect origins. Hosted connect links are single use and last at most 15 minutes. We retain delivery outcomes and technical receipts needed to handle callbacks and deletion requests.
4.8 What we do not collect
The service is free of charge for now and we currently collect no payment-card or billing data. Paid plans will be introduced later under Terms section 10; we will update this policy before introducing any related processing. We never request or store your Facebook, Instagram, Threads or LinkedIn password: you sign in at the network itself. Artima Socials is not for children under 16, and we do not knowingly collect their data (section 15).
5. Why we use it and on what legal basis
| Purpose | Legal basis under GDPR |
|---|---|
| Creating and running your account, sign-in and transactional account email | Article 6(1)(b), performance of the contract |
| Connecting accounts, publishing and other actions you instruct | Article 6(1)(b), performance of the contract |
| Security, abuse prevention, rate limiting, troubleshooting and the audit trail | Article 6(1)(f), our legitimate interest in a secure, reliable service and evidence of actions |
| Answering support requests | Article 6(1)(b), performance of the contract |
| Handling rights requests and legally required disclosures or retention | Article 6(1)(c), compliance with legal obligations |
We send only transactional email, such as verification, password resets and signup notices, and no marketing email. For audience data processed on your behalf, you determine the lawful basis as controller (section 3).
6. Who receives data
Service providers. We use the following providers to run Artima Socials; for customer audience data they are sub-processors under Terms section 11.
Each provider listed below processes personal data on our behalf under a data processing agreement, forming part of its standard terms accepted by us.
| Provider | Purpose | Data | Location of processing |
|---|---|---|---|
| Hetzner Online GmbH, Germany | Hosting of servers, database, cache, logs and backups | Data described in Privacy Policy section 4 | Falkenstein, Germany |
| Cloudflare, Inc., USA (R2) | Storage and public delivery of uploaded media | Media files; viewers' IP addresses and user agents | Cloudflare's network; storage location hint Eastern Europe (EEUR), with default jurisdiction, not restricted to the EU; access and transfers outside the EEA may occur |
| Resend | Transactional email: verification, password reset and signup notices | Recipient address, email content and links | Processing location has not been confirmed; processing outside the EEA cannot be excluded |
Social networks. Meta and LinkedIn receive the content and instructions you direct us to publish, reply to or delete. They are independent controllers.
Your tools. Data you request through the API, MCP or webhooks goes to the tools you expressly choose, under your contract with their providers and subject to section 7. You are responsible for their use of it.
Authorities. Disclosure occurs only where legally required, under our Public Authority Request Policy.
Platform compliance. Network providers and professionals acting at their direction may receive necessary information for compliance monitoring or audits under their platform terms.
We do not sell, license or buy platform data, rent LinkedIn content, or share data for advertising. Network credentials and secrets are protected and are not shared with your connected tools; service providers helping us run the service may process them only as needed for that service.
7. Rules for data from the networks
We request only the data needed for the features you use and use it only for their permitted purposes. We do not build or augment profiles of people, target advertisements, make eligibility decisions, discriminate, conduct surveillance or re-identify people. We do not build a database of people across customers or combine LinkedIn member data with other personal data. We do not disclose Page administrators or LinkedIn account managers to third parties.
Other LinkedIn members' names, pictures and comments may be displayed only inside the app, only to people associated with the relevant Page or profile. They must not be exported through the API, MCP, webhooks or data exports, sold, transferred, used for sales or recruitment, or used to infer sensitive information. Comment and reaction features remain unavailable. Other members' profile data is not stored; any technical cache is limited to 24 hours, and transient member social activity to 48 hours. Mention-search results are used only for mentioning. Imported own posts and connected organisation details follow the actual retention described in section 9, not these transient-cache limits.
LinkedIn data is kept separate for the customer it belongs to; LinkedIn insights are used only to report to that customer. LinkedIn content is not made available to third parties except its permitted display to the customer inside the app. Messaging data is used only to support the conversation. These rules do not override the applicable network terms.
8. API, MCP and webhooks
You create and can revoke the keys used to access the API and MCP. Account keys can manage profiles, create profile key pairs and register account-wide webhooks. A profile key pair has read and write permissions by default; dm permission for message API access must be granted explicitly.
The MCP server does not retain credentials or data; it forwards your own profile key pair to the API and can do only what that pair permits.
Webhook events are message.received, message.read, post.published, post.failed, social.linked and social.disconnected. Message events contain the participant's ID, name, username, message text and attachments, and are sent only for accounts with messaging enabled. Webhook subscriptions are account-wide: the profile key's separate dm permission does not control them. Deliveries are signed with HMAC-SHA256, retried on failure and sent only to public HTTPS addresses.
You are responsible for your tools and what they do with the data, as set out in Terms sections 5 and 7. The LinkedIn restrictions in section 7 apply to every access channel.
9. How long we keep data
| Data | Retention or deletion criteria |
|---|---|
| Accounts whose email is never verified | Deleted seven days after signup, with the workspace created by that signup |
| Your account and workspace data, profiles, posts, schedules, connection records, tokens, imported posts, keys and webhooks | Kept while the account exists; database data covered by account deletion is deleted immediately, subject to the separate records below and the workspace rules on the Data Deletion page |
| Media covered by account or profile deletion | Files normally deleted within minutes; in every case within 30 days |
| Audit records | 24 months from the action; may survive account deletion; email appears only as a keyed hash |
| Publish-attempt records | 24 months from the attempt; a record of a publication still in progress or whose outcome is unresolved is kept for as long as it remains unresolved; may survive deletion and include the handle, network post ID and link |
| Sign-in sessions | End after eight hours of inactivity, at most seven days, or earlier on sign-out, password reset or account deletion |
| Verification and password-reset links | Valid for 48 hours and one hour respectively |
| A social account you disconnect in the app | Tokens and direct messages are deleted immediately; the account's record and its post history, including imported posts, stay until you delete your account; we no longer use the connection |
| A connection whose token expired or was rejected by the network | Marked as disconnected and no longer used; its tokens, direct messages, record and post history stay until you disconnect it in the app or delete your account |
| Direct messages and participant profiles | Kept for the enabled conversation while the account remains connected; no time-based deletion of conversations; deleted immediately on in-app disconnect, Meta app removal received by us, or account deletion |
| Raw Meta webhook deliveries, which may include message text | 30 days from receipt; account or message deletion may remove them earlier |
| Outbound webhook delivery records, which may include message text | 30 days after the final delivery attempt, successful or failed; deleted earlier with the account or applicable message-data purge |
| Posts deleted in the app | Removed from visible history, but the stored record is erased when the account or profile is deleted |
| Imported posts, including LinkedIn own posts | Stored until account or profile deletion; no separate age-based deletion currently applies |
| Connected LinkedIn organisation details, including name and logo | Kept with the connection record until account or profile deletion |
| Incomplete uploads and orphaned upload files | Incomplete uploads expire after 24 hours; files in managed upload paths are removed after 24 hours only if no media record references them |
| Referenced media and older uploads outside those paths | Kept until account or profile deletion; there is no individual media-file deletion control |
| Comments and insights | Not stored in the database; short caches as in sections 4.4 and 7; counts in imported snapshots follow the snapshot retention |
| Server and edge logs | Server logs are kept in size-limited files that are overwritten continuously |
| Support and privacy correspondence | 24 months after the correspondence ends |
| Technical callback receipts and deletion-work records | Retained to recognise repeated requests and complete deletion work; no separate time-based expiry currently applies |
Backups. Every day at 03:30 UTC, an encrypted backup (restic, AES-256) of the database and server configuration file is sent to a separate Hetzner Storage Box in Falkenstein, Germany (EU). Backups are used only for disaster recovery, retain 7 daily and 4 weekly snapshots, are automatically deleted when they expire and remain for at most 28 days. Media files are not included. Account or profile deletion removes covered data from the live database immediately; copies made before deletion disappear when their backups expire, within 28 days.
Uploaded media is publicly reachable by anyone who has its link so the networks can fetch it. Removing a post on a network does not itself erase an uploaded file or the stored snapshot here; they follow the periods and criteria above.
We handle deletion requests from users, customers and networks promptly. Platform data is deleted automatically only in the cases described above. If you no longer need a connection's data, delete your account or profile, or email privacy@artima.ai and we will delete it. If the service ends or LinkedIn ends our access to its API, we delete all LinkedIn content we hold. Data subject to a legal retention duty is kept only for the required period, with evidence of the legal requirement.
10. Deleting your data
Everyone can request correction or deletion, whether or not they have an Artima Socials account. See Data Deletion for instructions and the differences between these routes:
- In the app, use Settings → Delete account, or Connections → Disconnect for one connection.
- Email privacy@artima.ai, preferably from your account address.
- Remove Artima Socials in the network's settings. A deletion request made through Meta removes tokens and direct messages; removing the app at Meta removes direct messages and ends our use of the connection; other stored data remains as described in section 9. LinkedIn does not notify us, so also disconnect here or email us.
If you commented on a customer's post or sent them a message, we forward your request to that customer and help them fulfil it.
11. Your rights
Subject to the conditions in GDPR, you have the right to:
- access your personal data;
- correct inaccurate or incomplete data;
- have data erased;
- restrict processing;
- receive portable data in a structured, machine-readable format;
- object to processing based on legitimate interests;
- withdraw consent where processing relies on it, without affecting earlier lawful processing; we do not rely on consent for the processing described in section 5;
- not be subject to a decision based solely on automated processing with legal or similarly significant effects; we make no such decisions.
Write to privacy@artima.ai. We respond without undue delay and at the latest within one month of receipt; we may extend this by two further months where GDPR allows and will tell you why. We may verify your identity. For audience data, we promptly forward the request to the relevant customer and help them respond; this includes requests forwarded to us by Meta.
You may complain to Úřad pro ochranu osobních údajů (ÚOOÚ), Pplk. Sochora 27, 170 00 Praha 7, www.uoou.cz, or to the supervisory authority in the EU country where you live or work.
12. Security
Connections to Artima Socials use TLS. Network access and refresh tokens and webhook secrets are encrypted with AES-256-GCM using a key kept outside the database. Passwords are stored as argon2 hashes and API credentials as SHA-256 hashes. Secrets and tokens, including Profile-Key, Profile-Secret, Authorization and Cookie headers, are redacted from logs.
Report vulnerabilities to security@artima.ai.
13. International transfers
Our application server is hosted by Hetzner in Falkenstein, Germany. Cloudflare, Inc. is a US company. Its R2 storage is configured with an Eastern Europe location hint and default jurisdiction; that does not limit processing to the EU. Cloudflare may access or transfer media and request data outside the EEA. Resend sends transactional emails; its processing region has not been confirmed and processing outside the EEA cannot be excluded.
The location hint is not a legal transfer safeguard. For transfers outside the EEA, Cloudflare and Resend provide standard contractual clauses included in the provider's data processing agreement where those clauses apply under that agreement. Any transfers outside the EEA by Hetzner are subject to appropriate safeguards under the provider's data processing agreement. Contact privacy@artima.ai for information about these safeguards and how to obtain a copy. We comply with the networks' transfer terms; personal data from the EEA that we receive from Meta Platforms Ireland is processed under the standard contractual clauses incorporated in Meta's terms.
When you instruct publication or another action, the selected social network receives the data under its own terms and may process it outside the EEA. Your own tools may also process data outside the EEA under the arrangements you choose.
14. Cookies
We use strictly necessary cookies and a language preference, with no analytics or marketing cookies and no consent banner. See the Cookie Policy for cookies, browser storage and media-preview requests.
15. Children
Artima Socials is not intended for persons under 16. We do not knowingly collect children's personal data. If you learn that a child under 16 has provided personal data, contact privacy@artima.ai and we will promptly delete it.
16. Changes
We publish each new version with a new version number and effective date. We notify you of material changes by email or in the app before they apply. Changes to the scope of processing are first submitted to the networks for review and approval where their terms require it; we notify LinkedIn of changes to how its data is handled. We inform affected members of material scope changes and obtain renewed authorisation where required.
17. Contact
Artima s.r.o., Company ID: 19658451, VAT ID: CZ19658451, with its registered office at nám. T. G. Masaryka 1281, 760 01 Zlín, Czech Republic, registered in the Commercial Register maintained by Krajský soud v Brně, Section C, Insert 135572.
- Privacy and rights requests: privacy@artima.ai
- Support: support@artima.ai
- Vulnerabilities: security@artima.ai
- Phone: +420 605 375 252
You can also contact ÚOOÚ at the address in section 11.