Privacy policy
Dieses Dokument ist auf Türkisch und Englisch verfügbar.
Dieser Text ist auch unter https://spexop.com/synvaro/privacy/ veröffentlicht. Stand der Quelle: 17 November 2026.
Last updated: 17 November 2026. This policy explains how the Synvaro application and its social-platform integrations, including Synvaro Pages, process personal data under the Turkish Personal Data Protection Law No. 6698 (KVKK) and, where applicable, the EU General Data Protection Regulation (GDPR). Not every planned feature is live; this policy describes existing flows and marks optional ones.
1. Who we are and our roles
The operator and data controller for the service in Türkiye is ISIS TURİZM HİJYEN DANIŞMANLIK ÇEVRE SAĞLIĞI ve TİC. LTD.ŞTİ. Synvaro and Qos are its brands in Türkiye. Registered address: Bahçelievler Mah. Antalya Cad. No:75 / 7-8, 07600 Manavgat/Antalya, Türkiye. Privacy and product contact: muhasebe@isis-turkey.com. Company website: ISIS Türkiye. The KVKK aydınlatma metni gives the Turkish-law information in the required form.
Synvaro acts in different roles depending on the data:
| Role | Data |
|---|---|
| Synvaro as controller | Accounts, sessions, access and security events, billing, support and abuse prevention. |
| Synvaro as processor on the customer’s instructions | Brand profile and memory, drafts, media and derivatives (crops, renders), workflow, external review and AI requests made for the customer. |
| Third parties as independent controllers | Social platforms (Meta, LinkedIn, Google/YouTube, Bluesky, TikTok), Canva and payment institutions (iyzico, Stripe), under their own terms and purposes. |
If another organization independently hosts Synvaro, that organization controls its installation and must provide its own privacy notice. The Synvaro project does not automatically receive that installation’s data.
2. What we process, per flow
| Flow | Personal data |
|---|---|
| Account, sign-in and security | Email, display name, avatar, Argon2id password hash, session token hash, device description, last-seen time, encrypted TOTP secret, hashed recovery codes, passkey public keys, Google/GitHub/Apple sign-in identifiers and security audit events. The IP address is used in memory for rate limiting. |
| Organizations and teams | Memberships, roles (OWNER/EDITOR), content-approval permission and invitations (email, hashed token, 7-day expiry). |
| Social connections and publishing | Platform account ID, display name, scopes, encrypted access and refresh tokens; references to published posts and engagement counters of the customer’s own posts. Some platforms depend on provider approval. |
| Media library and Canva | Uploaded images, video and audio (originals may contain EXIF data such as location, and faces or names of people), file names, descriptions, crops and renders, Canva imports and their provenance. Canva import is optional and off by default. |
| AI features | Prompts, selected text and media sent to the chosen AI provider, generated outputs, and cost and usage records. AI is off by default for each user. |
| External approval of an exact revision | Link hash, creation, expiry, use and revocation times, the approve or reject decision and an optional reason. No name or email of the approver is recorded. The IP address is used in memory for rate limiting. |
| Notifications and email | Email address, notification type and delivery status. |
| Website analytics (GA4) | Aggregated daily metrics (sessions, key events by UTM) read from the customer’s own Google Analytics 4 property when the customer connects it. No visitor-level data is stored. |
| Competitive and social intelligence | Where enabled: publication time, format, topic tags and visible counts of public posts of accounts the customer watches, with source and fetch time; CSV and manual entries. No scraping. |
| Billing | Package, amount, currency, payment and subscription status, provider references; payer name, address and identity details (encrypted). No card number or CVV. Paid plans are not yet open. |
| Logs, backups and support | Request metadata, error records, support correspondence and database backups. |
3. Purposes and legal bases
KVKK bases refer to Article 5(2); GDPR bases to Article 6(1).
| Purpose | KVKK | GDPR |
|---|---|---|
| Providing the account and the service | (c) contract | (b) contract |
| Security, multi-factor authentication, abuse and fraud prevention | (f) legitimate interest; (ç) legal obligation | (f) legitimate interests; (c) legal obligation |
| Content preparation, approval and user-approved publication | (c) contract | (b) contract; processor for the customer |
| External approval audit trail | (f) legitimate interest | (f) legitimate interests |
| AI operations requested by the user | (c) contract | (b) contract |
| Billing, invoicing and tax records | (c) contract; (ç) legal obligation | (b) contract; (c) legal obligation |
| Service and security emails | (c) contract; (f) legitimate interest | (b) contract; (f) legitimate interests |
| Handling rights requests and legal claims | (ç) legal obligation; (e) establishing, exercising or protecting a right | (c) legal obligation; (f) legitimate interests |
We do not use personal data for advertising, do not sell it and do not send marketing email from the application. Any future marketing communication will rely on separate opt-in consent. A platform authorization does not authorize unrelated use of your data.
4. Social accounts and publishing
Connecting an account uses the provider’s authorization flow. Synvaro uses the granted permissions to discover eligible accounts and, when you authorize it, publish or manage content. LinkedIn Page access is limited to Pages for which the connected user has the required role. We do not request your social-platform password.
Nothing is published without a user’s explicit approval of the exact content revision. An approved schedule authorizes execution of that content at the selected time. Publishing discloses the content to the platform and its audience, which govern it under their own terms.
Synvaro uses YouTube API Services when you enable its YouTube integration. See the YouTube Terms of Service, Google Privacy Policy and LinkedIn Privacy Policy for those providers’ practices.
Google user data. Synvaro’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Data from YouTube and Google Analytics is used only to provide the features you enable: uploading videos you have approved, reading your own channel, video and comment data and metrics, and reading aggregated, read-only web analytics for the property you select. It is not sold, not used for advertising, and not used to train generalized AI models. People do not read it except with your consent, when needed for security or abuse investigations, or to comply with law.
5. External approvers, AI and people in media
External approvers. A person who receives an approval link needs no account. Synvaro stores no recipient name or email; the customer chooses how to deliver the link. Link use and the decision are kept as an audit record. External approvers can exercise their rights through the contact below.
People in media. Brand media can show names, faces, locations, children and sensitive material. Original uploads are stored as uploaded; crops produced by Synvaro are re-encoded without EXIF/XMP metadata. Customers must have a lawful basis for such content.
AI. AI runs only when a user starts an action, and the price is shown before paid actions. The provider and model depend on the user’s choice and configuration (OpenAI, Google Gemini, Anthropic, Mistral, Groq, fal.ai, ElevenLabs), using either Synvaro’s platform key or the user’s own key. The selected provider receives the prompt and the relevant brand context or source material needed for that task.
Provider retention and training practices depend on the provider, account and settings; we do not promise that third-party processing has zero retention, is excluded from model training or stays within a particular region. fal.ai output URLs may be accessible to anyone who possesses the URL until the provider expires it. The AI visual review (Guardian) gives warnings and does not certify legal compliance or grant permission to publish. Access to a platform never authorizes unrelated AI processing of third-party data. Avoid submitting information you are not authorized to share.
6. Cookies and analytics
The Synvaro application uses only strictly necessary authentication and security cookies and sets no analytics or advertising cookies. When a customer connects Google Analytics 4, Synvaro reads that customer’s own GA4 property on the server and places no analytics cookie in the application. See the cookie policy.
7. Recipients and international transfers
We share data only with the categories of recipients listed in the subprocessor list: hosting and database, media storage (Cloudflare R2), email (Resend), AI providers, the platforms the user connects, payment institutions, and authorities where the law requires.
Several recipients are outside Türkiye and the EEA. Data may be processed outside Türkiye depending on the selected service and its infrastructure, subject to applicable transfer requirements under KVKK Article 9 and, where applicable, GDPR Chapter V. Storing media in a particular region does not by itself make the whole service resident in that region: AI, email, support and backups may run elsewhere.
8. Retention
Data is retained for as long as needed for its purpose and as required by law, and then deleted, destroyed or anonymized. Examples built into the application: sessions expire after 8 hours, password-reset links after 30 minutes, invitations after 7 days, and external approval links after the selected 24 hours, 72 hours or 7 days.
Accounting retention, disconnecting an integration, deleting derivatives and posts already published on independent platforms lead to different outcomes. Disconnecting an integration removes its active credentials from Synvaro but does not automatically delete saved content, publication history, backups or posts already on the platform. Backups may delay deletion until they expire.
9. Your rights and requests
Under KVKK Article 11 and, where applicable, GDPR Articles 15–22 you may request access, rectification, erasure, restriction and data portability, object to processing (including processing based on legitimate interests) and withdraw consent where processing relies on it. You may complain to the Turkish Personal Data Protection Authority or, where applicable, to your EU supervisory authority.
Email muhasebe@isis-turkey.com with the subject “Synvaro privacy request” and identify the relevant account or workspace; no account is needed. Do not send passwords, API keys or authorization tokens. We verify identity and authority and never disclose another customer’s data. Where the customer is the controller, we coordinate with it. We respond within 30 days under KVKK and within the periods required by other applicable law.
You can disconnect social accounts and personal AI credentials in Synvaro. For Google and YouTube, you can also revoke access through your Google account permissions; for LinkedIn and other services, use their connected-app settings. Revoking access does not itself remove an already published post.
10. Security
Measures include Argon2id password hashing; session, reset, invitation and external-approval tokens stored only as SHA-256 hashes; AES-256-GCM encryption of OAuth tokens, TOTP secrets, personal AI keys and billing contact data; required multi-factor authentication in production; passkeys storing only public keys; private media storage; organization and brand membership checks; security audit records; and rate limiting. These measures reduce risk but cannot guarantee absolute security. We hold no security certification and make no such claim.
11. Children
Synvaro is a business service and is not directed at children. Customers must not upload children’s data without a lawful basis.
12. Changes and contact
We will update this page and its date when our practices change. Material changes requiring notice or consent will be communicated through the service or the account contact channel as appropriate. Contact: muhasebe@isis-turkey.com.
