Privacy Policy

1. Our roles

We act as controller for account administration, our billing, support and service security. For personal data contained in customer-managed content, audience data or other material processed solely on a customer's instructions, the customer determines the purposes and we act as processor under a separate data processing agreement. A customer may itself act as processor for its client. Contact the relevant customer about that data; we assist in handling requests under our agreement. Social platforms and payment providers may act as independent controllers for their own purposes.

2. Data and sources

We receive data directly from you, from the person inviting you to a workspace, from connected platforms within authorised permissions, and from your device when you use Tagv. Depending on enabled features, this includes name, email, password hash, authentication settings, workspace roles, invitations, support correspondence, billing details and transaction identifiers; social profile identifiers, names, avatars and encrypted access tokens; posts, images, video, comments, interactions and statistics; and IP addresses, browser information, request times and security logs. Optional AI functions receive the prompts and materials you submit to them. Payment card information is entered with the payment provider; Tagv does not store full card credentials.

If another person supplies your contact details, we use them for the invitation, cooperation or support concerned and provide the legally required information. Providing data is generally voluntary, but account, security and billing information marked as required is necessary for the relevant service or a legal obligation; without it we may be unable to provide that service. Do not submit special-category data or criminal-offence data unless a lawful basis and appropriate contractual safeguards have first been established.

3. Purposes and legal bases

• Account creation, requested functions, billing administration and contractual support: Article 6(1)(b) GDPR where you are the contracting individual; for representatives and invited users, Article 6(1)(f), our legitimate interest in providing the organisation's service and maintaining business contact.
• Tax, accounting and other binding legal duties: Article 6(1)(c) GDPR.
• Security, fraud prevention, necessary diagnostics, handling non-contractual enquiries and establishing or defending claims: Article 6(1)(f), our legitimate interests in protecting users, operating a reliable service and protecting legal rights; we balance these against your rights.
• Optional marketing communications and non-essential tracking, if introduced: consent under Article 6(1)(a) GDPR and applicable electronic communications rules where required. Consent is separate from accepting the terms and can be withdrawn without affecting earlier lawful processing.
• Customer-controlled content: the customer determines the legal basis; we process it on documented instructions under Article 28 GDPR, not on the basis of blanket user consent to this policy.

4. Integrations, publication and AI

Connecting a social account authorises the operations shown during the connection flow, such as publishing or reading profile information and statistics. An integration permission is distinct from GDPR consent. You can disconnect in Tagv or revoke access at the platform. This stops future authorised access but does not automatically remove already published posts, platform-held data or copies received by others.

Content is shared with the accounts, workspace members and audiences you select. Public links, calendars and publications may expose personal data to anyone who can access them; check settings before sharing.

AI functions use OpenRouter, Inc., which forwards the prompts and materials needed to perform the task to the selected model provider. Depending on the function, these may include text, post context and images submitted for analysis. The model can be configured for the workspace. Retention and use of data for training depend on the model provider and the privacy settings of the OpenRouter account; we do not declare a uniform retention period or exclusion from training for all models. Provider information: https://openrouter.ai/privacy/ and https://openrouter.ai/docs/guides/privacy/provider-logging.

5. Recipients and international transfers

Recipients may include infrastructure, storage, email, security and support providers; Stripe for payments; connected social platforms; enabled AI providers; professional advisers; and legally authorised authorities. We limit access to what the relevant role requires. We enter into appropriate agreements with processors. Uploaded files are stored in Cloudflare R2 in Europe. The Tagv application runs in containers in Microsoft Azure in the Poland Central region in Poland. The application database is located in the same region.

Hosting the application and database in Azure Poland Central and storing files in Cloudflare R2 in Europe do not determine where AI providers process data. Using OpenRouter and model providers may involve processing data outside the EEA. EU-only AI processing requires active OpenRouter regional routing and use of the European API endpoint. The processing location depends on the service configuration and model provider.

6. Retention and deletion

Account data is retained while needed to provide the account. Customer content is retained according to the customer’s instructions, workspace settings and the data processing agreement. Deleting a personal account does not necessarily delete another customer’s workspace records or posts on external platforms. We delete account data and its content 3 months after account closure, except for data we must retain for legal obligations or establishing and defending claims. We restrict the use of retained data to those purposes.

Accounting and tax records are retained for statutory periods, generally five years calculated under the relevant Polish tax or accounting rules; a legal suspension or extension may change that period. Consent records are kept as necessary to demonstrate compliance. Marketing processing stops when consent is withdrawn or an applicable objection is made, with a minimal suppression record where needed to honour that choice.

Logs are deleted after 3 months. Deleted accounts’ data is removed from backups 3 months after account closure. We do not delete accounts or their data solely because of user inactivity.

7. Your rights

Subject to the conditions in GDPR, you may request access and a copy, rectification, erasure, restriction and portability of data processed automatically on consent or contract. You may object to processing based on legitimate interests on grounds relating to your situation and may object to direct marketing at any time. You may withdraw consent as easily as you gave it; withdrawal does not affect prior lawful processing.

Contact support@tagv.io. We normally respond within one month; where legally justified, we may extend by up to two further months and explain this within the first month. We may request proportionate identity verification. You may complain to the President of the Polish Personal Data Protection Office (https://uodo.gov.pl/) or another competent supervisory authority, including in the country of your habitual residence, workplace or the alleged infringement.

8. Cookies and browser storage

Tagv sets its own cookies to maintain sessions, secure the connection of social accounts and remember the language. Session and integration cookies are necessary for these functions; the language cookie stores the user’s preference. We currently do not use analytics or analytics or advertising cookies.

Cookies can be deleted or blocked in browser settings. Blocking session or integration cookies may prevent login or the connection of a social account. Below we list the names, purposes and lifetimes of cookies set by Tagv. The lifetime is counted from when a cookie is set or reset.

The application also uses localStorage: splot_access_token stores the access token; locale, splot-theme and splot_active_workspace_id remember the language, theme and workspace; splot_onboarding_done_* remembers dismissal of the introduction, and splot_upload:* enables resuming a file upload. LocalStorage has no automatic expiry: entries remain until removed by the application or until the browser’s site data is cleared. The token’s server-side validity is independent of its storage in the browser.

• splot_rt — maintains and refreshes the login session; 7 days from setting or refreshing, deleted on logout. HttpOnly cookie, SameSite=Strict, path /api/auth.
• splot_oauth_nonce — protects the social account connection process against request substitution; up to 15 minutes, deleted when handling the return from authorisation. HttpOnly cookie, SameSite=Lax, path /.
• splot_oauth_pkce — secures the authorisation code exchange for integrations using PKCE; up to 15 minutes, deleted when handling the return from authorisation. HttpOnly cookie, SameSite=Lax, path /.
• splot_oauth_dpop — secures authorisation for the Bluesky integration; up to 15 minutes, deleted when handling the return from authorisation. HttpOnly cookie, SameSite=Lax, path /.
• locale — remembers the selected application language; 365 days from setting. Functional cookie, SameSite=Lax, path /.

9. Security, automated decisions and children

Measures include encrypted transport, hashed passwords, encrypted integration tokens and role-based access controls. We adapt safeguards to risk and handle breaches under applicable law. Keep credentials secure and use available two-factor authentication.

Tagv is intended for adults. If you believe a child has submitted personal data, contact us. We do not make decisions about users based solely on automated processing that produce legal effects or similarly significantly affect them.

10. Policy updates

We update this policy when processing changes and identify the applicable version and date. Material changes are communicated appropriately before they apply. A policy update does not itself obtain consent or create a new legal basis. If new processing requires consent, we request it separately.