Privacy Policy
Effective October 1, 2026 · Updated October 22, 2026
Synex ("we") operates the Synex web and mobile apps (the "Service"), which bring a creator's Threads, Instagram and YouTube channels together in one place. This policy explains what we collect and why, how long we keep it, when we delete it, and how you can exercise your rights. October 22 update: disclosures for follow-gated resource delivery, confirmation replies and their retention have been supplemented.
1. Information we collect and why
We collect only what the Service needs. Platform data is received through official APIs and only for accounts you connect yourself. We never ask for your platform passwords.
| Category | Data | Purpose | Source |
|---|---|---|---|
| Account | Email, name (optional), password hash, social login identifier (Google, Kakao, Apple) | Sign-up and sign-in, identity verification, support | You |
| Threads channel | User ID, username, profile picture, access token (encrypted), your posts and metrics, replies to your posts and posts that mention you (author username, text, time, hidden status) | Dashboard, archive, scorecards, inbox, search | Meta (Threads API) |
| Instagram channel (professional account) | Account ID, username, profile picture, follower count, access token (encrypted), media (caption, media URL, timestamp, permalink) and insights, comments and mentions (author username, text, time) | Dashboard, archive, scorecards, inbox, search | Meta (Instagram API) |
| YouTube channel | Channel ID and name, access and refresh tokens (encrypted), video list with titles and descriptions, public comments, YouTube Analytics reports (views, watch time, subscribers gained and lost, etc.) | Dashboard, archive and inbox display | Google (YouTube API Services) |
| AI reply drafts | The comment you request a draft for, your original post, your brand voice, whether a sent reply used a draft and how much it was edited, the time you consented to AI use | Generating reply drafts, quality metrics | You and your connected channels |
| Instagram keyword campaigns | Campaign account, post and comment identifiers, keyword, material name, link and version, saved DM message text, reply tone instructions, generated public reply, dispatch result and timestamps. If the follow check is selected, we also store the recipient Instagram-scoped ID (IGSID), request confirmation code, SHA-256 hash of the latest incoming message ID and its received time, the first instruction dispatch start time, and follow-processing status and fixed reason. Message ID hashes and received times are kept only for confirmation replies matching the campaign and recipient. Incoming messages delivered by the platform are processed in server memory only to identify campaign confirmation requests; unrelated message bodies and identifiers are not stored. We do not store incoming DM bodies, general profiles or usernames for this confirmation processing. | Matching comments on designated posts, sending enabled public replies and resource DMs, selected follow checks and confirmation replies, duplicate prevention and result display | You and Meta (Instagram API) |
| Payments | Payment method identifier (TossPayments billing key), payment and refund records, Apple transaction data | Paid plans, refunds, statutory record keeping | You and payment providers |
| Push notifications | Device push token, device type, notification delivery records, notification settings, consent and withdrawal records for promotional messages (with time) | Sending notifications, managing consent | Your device and you |
| Usage data | Access logs, IP address, browser and device information, error and performance data | Security, abuse prevention, improving the Service | Collected automatically |
2. Connecting platforms and permissions
- Threads and Instagram are connected through Meta's official APIs. We read only the connected account's data and the comments and mentions on that account's content.
- Inbox replies, hiding and deletion run when you press the corresponding button. Synex does not automatically engage with unrelated accounts' posts.
- For a keyword campaign you enable, a matching comment on the designated post of your own connected Instagram professional account can automatically trigger each selected action: a public reply, a resource DM, or both. If the follow check is selected, the first instruction DM has no resource. A reply with the confirmation code triggers an actual follow lookup and a resource DM for followers. Non-followers are asked to follow and reply with the same code again. Processing stays within 24 hours of the reply. These confirmation replies are processed, but this is not a general conversational chatbot. AI public replies require the same recorded, unrevoked consent for the current AI provider used by inbox AI drafts; enabling a campaign is a separate action.
- YouTube uses read-only scopes (youtube.readonly, yt-analytics.readonly). Synex never writes to YouTube; you reply to YouTube comments in YouTube Studio through a link.
- We record the permissions each channel actually granted. You can review them or disconnect in Settings › Channels.
3. YouTube API Services
Synex uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service, and the Google Privacy Policy also applies.
- YouTube Terms of Servicehttps://www.youtube.com/t/terms
- Google Privacy Policyhttps://policies.google.com/privacy
- Google security settings (revoke access)https://security.google.com/settings/security/permissions
- What we collect: your connected channel's information, video list and metadata, public comments on your videos, and YouTube Analytics reports.
- How we use it: we show it to you in your dashboard, archive and inbox, labeled "Provided by YouTube". We never sum it with other platforms' metrics or turn it into scores, multiples or rankings.
- Sharing: we do not sell or share YouTube data with third parties and we never send it to AI services. Only you and team members you invite can see it.
- Storage and refresh: tokens are stored encrypted. Video titles, descriptions and comments are refreshed within 30 days and deleted comments are removed. Access to analytics data is re-verified every 30 days.
- Revoking access: disconnect YouTube in Settings › Channels, or remove Synex's access in your Google security settings. When you disconnect we revoke the token and delete the data within 24 hours; if you revoke access at Google we delete it within 7 days after detecting the revocation.
Synex's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Google API Services User Data Policyhttps://developers.google.com/terms/api-services-user-data-policy
4. AI processing
"Draft with AI" in the inbox runs only when you press it, and you review, edit and send the draft yourself. The first time you use it we tell you the AI provider and what is sent, and record your consent with a timestamp.
An enabled Instagram keyword campaign can generate and post an AI public reply automatically after a matching comment, subject to the account, post and campaign conditions above. It uses the same recorded consent for the current AI provider as inbox AI drafts; this consent must not have been revoked. Campaign activation is separate from AI consent. Only replies that pass safety checks are posted; if no reply passes, nothing is posted and no fixed fallback reply is substituted.
| Feature | AI provider | Data sent | Retention |
|---|---|---|---|
| Inbox reply drafts | Microsoft Azure OpenAI (hosted by Microsoft; contracting entity under review) | That comment, your original post, your brand voice | Azure: default abuse monitoring applies as described in section 4; exact applicable retention terms remain under review. / Synex: draft records and usage/edit measurements, 90 days |
| Instagram campaign AI public replies | Microsoft Azure OpenAI (hosted by Microsoft; contracting entity under review) | The triggering comment, the first 300 characters of the post caption and the first 500 characters of your reply tone instructions | Azure: the abuse-monitoring terms described below. Synex: generated reply and dispatch records are subject to cleanup after 30 days; campaign settings and material versions are separate records. |
| Existing creation tools (post drafts, AI polish, card news, brand voice analysis) | Microsoft Azure OpenAI (hosted by Microsoft; contracting entity under review) | What you enter and your posts | Azure: default abuse monitoring applies as described in section 4; exact applicable retention terms remain under review. / Synex: results are kept until you delete them |
- Microsoft hosts Azure OpenAI; this route does not use the direct OpenAI, Anthropic or Google AI APIs. Microsoft says prompts and responses are not used to train foundation models without permission or instruction.
- YouTube data is never sent to AI.
- AI never produces the numbers you see. Every figure is a platform-provided value or a calculation from it.
The current gpt-5-mini deployment is Global Standard. Its East US 2 resource location does not restrict inference to the United States. Prompts and responses may be processed in any geography where the model is deployed. Exact transfer countries, contracting entity and applicable retention terms remain under review.
Default Azure abuse monitoring applies: flagged prompts and responses can undergo automated review and, in some cases, storage and review by authorized Microsoft staff. We do not promise zero data retention or deletion of all AI-provider records within 30 days. See Microsoft's current terms below.
- Microsoft Azure OpenAI — data privacyhttps://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy
- Microsoft Azure OpenAI — abuse monitoringhttps://learn.microsoft.com/en-us/azure/foundry/openai/concepts/abuse-monitoring
5. Retention
| Data | Source | Retention |
|---|---|---|
| Your posts and media, metric snapshots | Threads, Instagram | While the channel is connected (regardless of plan) |
| Comment, reply and mention text, author usernames | Threads, Instagram | 90 days |
| Video titles, descriptions, etc. | YouTube | While connected, refreshed within 30 days |
| Statistics and analytics reports | YouTube | While connected (analytics access re-verified every 30 days) |
| Comment text | YouTube | Up to 90 days (refreshed every 30 days, deleted comments removed) |
| AI draft records | Synex | Only sent drafts and whether they were edited, 90 days |
| Instagram campaign dispatch and follow-check records (including generated public replies) | Synex / Instagram | Cleanup targets records older than 30 days from the initial request creation. Follow-check records are part of the same dispatch record and have no separate longer retention. Campaign settings and material versions have no separate fixed time-based cleanup and are removed with the associated channel or account. |
| Push tokens and notification records | Device | Tokens deleted when unregistered, records 90 days |
| Payment, supply, contract and withdrawal records | TossPayments, Apple | 5 years (Korean E-Commerce Act) |
| Consumer complaint and dispute records | You | 3 years (Korean E-Commerce Act) |
| Access logs | Collected automatically | 3 months (Korean Protection of Communications Secrets Act) |
6. Deletion
| Trigger | What happens | Deadline |
|---|---|---|
| You disconnect a channel in the app | Token revoked through the platform's revoke API and that channel's data deleted | 24 hours |
| You remove the app on the platform (Threads uninstall or deletion request, Instagram deauthorization or data deletion request) | Deletion job registered; a status URL and confirmation code are returned | 24 hours |
| You revoke access at Google (token refresh fails) | We notify you that the connection ended, then delete | 7 days |
| You delete your account (app or web) | All channel data and the account deleted (except payment records we must keep by law) | 24 hours |
| You request deletion (email or the data deletion page) | Same as above | 7 days |
| A channel locked by your plan limit stays locked for 90 days | We notify you 7 days before, then disconnect and delete | - |
The deletion deadlines above apply to primary service data. PostgreSQL backups use Azure Korea South GRS storage. Base blobs become lifecycle deletion targets more than 28 days after modification; previous versions become targets more than 28 days after creation. Blob/container soft-delete retention is configured to 7 days. Lifecycle processing is asynchronous, so this is not a guarantee of complete deletion within 35 days.
7. Push notifications and promotional messages
- We process your device push token and delivery records to send notifications. When you sign out, delete your account or turn notifications off, we immediately unregister and delete that device's token.
- Expo relays notifications to Apple APNs for iOS or Google FCM for Android for delivery to your device. Along this route, notification payloads can include connected-channel identifiers, commenter usernames, post/comment excerpts and notification action data, as well as device delivery identifiers and title/body. You can turn app notifications off in Settings.
- Promotional messages (new features, offers, trial-ending notices, etc.) are sent only if you separately turn on "Consent to promotional messages (push and email)". Allowing notifications on your device is not this consent.
- Promotional push messages between 9 p.m. and 8 a.m. are sent only with a separate night-time consent.
- Promotional messages start with (광고) [Ad] in the title and body and include how to opt out. We confirm every consent, refusal and withdrawal right away and remind you of your consent every two years.
- You can withdraw consent at any time in Settings › Notifications.
9. Processors (PIPA Article 26)Legal review required
The table describes the currently observed service routes. The complete processor list and contracting entities remain under legal review; it is not a finalized contractual list.
| Processor | Work entrusted |
|---|---|
| Microsoft (Azure; contracting entity to be confirmed) | Infrastructure, data storage and backups, error and performance monitoring; AI reply drafts, Instagram campaign AI public replies and existing AI creation features through Azure OpenAI |
| Toss Payments Co., Ltd. | Web payment processing |
| 650 Industries, Inc. (Expo) | Relaying notifications to Apple APNs or Google FCM for device delivery |
| Vercel Inc. | Web hosting and delivery, API proxying and image optimization where those web routes are used |
| Apple APNs (contracting entity under review) | iOS device push delivery after relay by Expo |
| Google FCM (contracting entity under review) | Android device push delivery after relay by Expo |
10. Transfers outside Korea (PIPA Article 28-8)Legal review required
The table describes observed infrastructure and AI data flows. Transfers use encrypted connections (TLS). The complete recipient list, contracting entities, transfer countries and retention terms remain under legal review.
| Recipient (contact) | Country | Data | When and how | Retention | How to refuse and effect |
|---|---|---|---|---|---|
| Microsoft Azure OpenAI (privacy: https://learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-privacy; contracting entity to be confirmed) | Global Standard: any geography where the model is deployed; exact countries under review (not United States only) | Reply-draft inputs; Instagram campaign comment, caption excerpt (300 characters) and tone instructions (500 characters); inputs and posts used by other AI creation features (excluding YouTube data) | Sent by API when you request an AI feature or an enabled AI public-reply campaign is triggered | Azure: default abuse monitoring applies as described in section 4; exact applicable retention terms remain under review. | Do not request AI features or disable AI public replies in campaigns to avoid this AI transfer; manual replies remain available |
| 650 Industries, Inc. (Expo, expo.dev/privacy) | United States (Expo Push Service hosted on Google Cloud) | Device push token, notification title/body, connected-channel and commenter identifiers, post/comment excerpts and notification action data | Sent by API when a notification is delivered; Expo relays to Apple APNs or Google FCM | As long as needed to deliver | Not transferred if you turn off app notifications |
| Microsoft (Azure; contracting entity to be confirmed) | Korea Central VM storage and Korea South GRS backups (South Korea); other infrastructure and remote-access destinations remain under review | Service data in general | Continuously while you use the Service | Primary service data follows this policy; backup lifecycle and soft-delete periods are described in section 6 | Required to use the Service |
| Vercel Inc. (vercel.com/legal/dpa) | Global delivery and processing regions; exact processing and remote-support countries remain under review (see the official links below) | Web request data (IP address, browser information and cookies); contents of API requests/responses routed through the web proxy, including login information, session cookies, inbox, content and payment-related API data; image URLs and image content when image optimization is used | When loading the web app or using its proxy/image routes, over HTTPS | Vercel processing and deletion terms apply; exact applicable retention remains under review | Web hosting is required to use the web app |
| Apple APNs (contracting entity under review) | Processing countries remain under review | Device delivery identifiers and notification payload relayed by Expo, including title/body, channel/commenter identifiers, post/comment excerpts and notification action data | When Expo relays notifications for iOS device delivery | Applicable retention terms remain under review | Turn off app notifications to stop this notification delivery |
| Google FCM (contracting entity under review) | Processing countries remain under review | Device delivery identifiers and notification payload relayed by Expo, including title/body, channel/commenter identifiers, post/comment excerpts and notification action data | When Expo relays notifications for Android device delivery | Applicable retention terms remain under review | Turn off app notifications to stop this notification delivery |
- Vercel — regionshttps://vercel.com/docs/regions
- Vercel — data processing addendumhttps://vercel.com/legal/dpa
- Expo — push service processinghttps://docs.expo.dev/push-notifications/sending-notifications/
11. Security
- Platform access tokens are encrypted at rest; data in transit is encrypted (TLS)
- Least-privilege access with access logging
- Regular security reviews and vulnerability fixes
12. Your rights
- You may request access to, correction or deletion of your personal information, ask us to stop processing it, and withdraw consent at any time.
- You can disconnect channels in Settings › Channels and delete your account in Settings yourself.
- You can also revoke access on each platform: the website permissions / apps and websites settings in Threads and Instagram, and your Google security settings.
- Send requests to info@quantus.kr and we will handle them without delay.
14. Contact and remedies
- Privacy inquiries: info@quantus.kr
- Korea Internet & Security Agency privacy report center: privacy.kisa.or.kr / 118 (in Korea)
- Personal Information Dispute Mediation Committee: www.kopico.go.kr / 1833-6972
15. Changes to this policy
We announce changes in the Service 7 days before they take effect (30 days for changes that are unfavorable to you).