Adsy Privacy Policy
Version of 2026-11-18.
This policy explains what data the Adsy service (https://adsy.kz) processes, why, how it is stored, who receives it and how to delete it. It covers the website, the Adsy web application and the advertising account data that customers connect to Adsy.
1. Summary
- Adsy is a service for managing Google Ads, Meta (Facebook and Instagram), TikTok Ads and Yandex Direct advertising accounts. Accounts are connected through the platforms' official APIs using OAuth.
- Adsy reads campaign structure, statuses, budgets, bids and performance statistics from connected accounts to show them in a single interface.
- Adsy changes an account only on a user's command, after a "before → after" preview and confirmation, or under a rule that a user created. Every change is recorded in the activity log.
- OAuth tokens are stored only in encrypted form. Data is stored on a server in the Republic of Kazakhstan.
- We do not sell data, use it for advertising or use it to train artificial intelligence models.
- You can disconnect an account and have its data deleted at any time. See the Data Deletion page.
2. Data controller and contact details
The operator of the Adsy service and controller of the data described in this policy is:
- Individual Entrepreneur “Rosemary” (ИП «Rosemary»)
- Address: 116 Kazybek Bi St., Almaty, Republic of Kazakhstan
- Phone: +7 708 337 0679
- Email: support@adsy.kz
Send questions about personal data and deletion requests to support@adsy.kz.
3. Data we process
3.1. Adsy user accounts
- Email address, name, interface language and whether the email address is verified.
- Password, stored as an Argon2id hash. We do not store the password itself.
- Session data: sign-in and last activity time, IP address and browser information (user agent).
- Links for email verification, password reset and invitations, stored as hashes and valid for a limited time.
3.2. Organizations
Organization name and settings, members and their roles (owner, manager, viewer), and invitations (the invitee's email address and role).
3.3. Advertising account data received through platform APIs
- Account IDs and names, currency, time zone, account status and access path (for example, through a manager account or an agency).
- Advertising structure: campaigns, ad groups, ads and keywords, with their statuses, budgets, bids and bidding strategies.
- Daily statistics: impressions, clicks, spend, conversions and other metrics the platform provides.
- The ID and, where the platform provides it, the email address or login of the platform account used to connect the advertising account.
- Changes made to the account outside Adsy, where the platform reports them through its API.
3.4. OAuth tokens
Access and refresh tokens that the platform issues after a user authorizes Adsy. Adsy needs them to access the account on the user's behalf.
3.5. Logs
- Activity log: who connected or disconnected an account, confirmed a change, created or edited a rule or invited a member, and when; for changes, the "before" and "after" values, the mode (live or dry run), the platform's response and the IP address.
- Platform API call log: method, account, response code, duration, request and response bodies. Tokens and other secrets are removed before anything is written to the log.
- Server logs: request path without parameters, response code, duration, user and organization IDs.
3.6. Support requests
Emails you send to support and our replies.
Adsy does not currently collect payment data: the service is in free early access.
4. Access to advertising platforms
For each platform, Adsy requests only the permissions its features need. The platform shows you the list of permissions on its consent screen when you connect.
| Platform | Permissions requested | Purpose |
|---|---|---|
| Google Ads | Google Ads API (https://www.googleapis.com/auth/adwords); openid and email | Reading accounts, campaign structure and statistics; changing statuses, budgets and bids on a user's command. openid and email identify which Google account is connected. The Google Ads API offers no narrower permission. |
| Meta (Facebook, Instagram) | ads_read, ads_management, business_management, pages_show_list, pages_read_engagement | Reading ad accounts, campaign structure and statistics; changing statuses, budgets and bids on a user's command; listing the business's ad accounts and Pages that the user granted access to |
| TikTok Ads | Ad Account Management, Reporting, Ads Management | Listing accounts and reading account data; statistics; changing statuses, budgets and bids on a user's command |
| Yandex Direct | direct:api, passport:business | Reading campaigns and statistics; changing statuses, budgets and bids on a user's command; working with an agency's client accounts |
Campaign creation is under development. If it requires additional permissions (for example, Meta's pages_manage_ads), we will update this policy before we start requesting them.
4.1. What Adsy changes in an account
- Currently: statuses (enable and pause), budgets and bids of campaigns, ad groups, ads and keywords.
- A change is made only in two cases: (a) a user with the owner or manager role requested it, reviewed the "before → after" preview and confirmed it; (b) a rule created by a member of the organization was triggered, and the organization's owner explicitly enabled automatic changes for that rule. By default, rules only send notifications.
- Every newly connected account starts in dry-run mode: changes are validated but not sent to the account. Only the organization's owner can switch an account to live mode.
- Adsy does not change payment methods, user access in the platform account or the settings of the advertising account itself.
4.2. How often statistics are updated
Statistics for today and yesterday are updated about once an hour (every 2 hours for Yandex Direct). Data for earlier days is recalculated overnight because platforms revise it retroactively. Updates may be delayed if a platform is temporarily unavailable or limits the number of requests.
5. Purposes and legal bases
| Purpose | Data | Legal basis |
|---|---|---|
| Registration, sign-in, organizations and roles | 3.1, 3.2 | Performance of the Terms of Service; user consent |
| Showing statistics and campaign structure, making changes and running rules | 3.3, 3.4 | Performance of the Terms of Service; the customer's consent to processing of its advertising account data |
| Tracking and reviewing changes, protection against errors and abuse | 3.5 | Performance of the Terms of Service; legitimate interest in the security of the service |
| Service emails: email verification, password reset, invitations, connection problem alerts | 3.1, 3.2 | Performance of the Terms of Service |
| Answering support requests | 3.6 | The user's request |
| Compliance with legal obligations | to the extent the law requires | Laws of the Republic of Kazakhstan |
One organization's data is never combined with another organization's data or used for another organization's benefit.
6. What Adsy does not do
- Sell data or transfer it to advertising networks, data brokers or information resellers.
- Use data to serve ads, including retargeting and personalized or interest-based advertising, or to promote Adsy.
- Use data to determine creditworthiness or for lending purposes.
- Use data to develop, improve or train artificial intelligence or machine learning models.
- Pass data received from one platform to another platform.
- Allow humans to read advertising account data, unless: (a) the user explicitly asked us to look at specific data, for example in a support request; (b) it is necessary for security purposes, such as investigating a bug or abuse; (c) it is required by law; or (d) the data is anonymized and aggregated for internal operations of the service.
7. Google data: compliance with the Google API Services User Data Policy
Adsy'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.
This means that Google Ads data received through Google APIs:
- is used only to provide user-facing features that are prominent in the Adsy interface: showing accounts, campaigns and statistics, previewing and making changes, rules and notifications;
- is not transferred to third parties, except as necessary to provide those features with the user's consent, for security purposes or to comply with applicable law;
- is not used to serve ads, including retargeting and personalized or interest-based advertising, and is not transferred to advertising platforms, data brokers or information resellers;
- is not used to determine creditworthiness or for lending purposes;
- is not read by humans, except in the cases listed in section 6.
These rules also apply to data aggregated, anonymized or derived from Google data.
8. Storage and security
- Data is stored and processed on a server in the Republic of Kazakhstan (Almaty), rented by Adsy from the hosting provider hoster.kz.
- OAuth tokens are encrypted before they are written to the database (hybrid X25519 + AES-256-GCM scheme). The decryption key is available only to the background processes that call the platforms; the web-facing part of the service cannot decrypt tokens. Tokens are never written to logs.
- Passwords are stored only as Argon2id hashes.
- Connections to the website and the application are protected by HTTPS. The session is kept in a cookie with the HttpOnly and Secure flags.
- Organizations' data is isolated at the application and database levels.
- The activity log is tamper-resistant: entries cannot be altered after the fact.
- Daily database backups are encrypted and kept for 14 days. Encrypted backups are also stored in secure cloud storage and on the operator's device. Token keys are not included in backups.
8.1. Retention periods
| Data | Retention | What happens next |
|---|---|---|
| OAuth tokens | While the account is connected | Deleted immediately on disconnection; for Google and TikTok, access is also revoked on the platform side |
| Account campaign structure and statistics | While the account is connected | Deleted within 72 hours of disconnection (usually within minutes), or after 30 days if the user chose "keep history" |
| Name and ID of a disconnected account | While the organization exists | Kept for the activity log; deleted together with the organization |
| Activity log and change history | While the organization exists | Deleted together with the organization |
| API call log: read requests | Request and response bodies for 7 days, other details for 90 days | Deleted by daily cleanup |
| API call log: account changes | 1 year | Deleted by daily cleanup |
| Synchronization run records | 90 days | Deleted |
| All of an organization's data | While the organization exists | Deleted 30 days after a request to delete the organization; the request can be cancelled before then |
| User account | Until the user asks for it to be deleted | Anonymized: email, name and password are removed, sign-in becomes impossible and sessions are ended |
| Sessions | Up to 30 days (14 days without activity) | Records deleted 30 days after the session ends |
| Invitations, verification and password reset links | Until used or expired | Deleted after 30 days |
| Backups | 14 days | Deleted data disappears from backups within 14 days |
9. Data deletion
- Disconnecting an account. The organization's owner disconnects the account in Adsy. The token is deleted immediately and background tasks for the account stop. The account's data is deleted within 72 hours or after 30 days, as the user chooses.
- Deleting an organization. The owner requests deletion of the organization. Tokens are deleted immediately (for Google and TikTok, also revoked on the platform side); all of the organization's data, including logs, is deleted after 30 days.
- Deleting a user account. After leaving all organizations, a user can ask for the user account to be deleted; it is then anonymized.
- Request by email. Any of these steps can be requested by writing to support@adsy.kz. Once we have confirmed that the request comes from the owner of the data, deletion is completed within 72 hours.
Step-by-step instructions, including how to revoke Adsy's access in each platform's settings, are on the Data Deletion page.
10. Who receives data
- Hosting provider: hoster.kz (Republic of Kazakhstan), which provides the server Adsy runs on.
- Email service provider: sends service emails and handles support correspondence. It receives the recipient's email address and the message text.
- Advertising platforms: Google, Meta, TikTok and Yandex receive the requests Adsy sends on the user's behalf: reading account data and commands to make changes. The platforms process this data under their own terms.
- Public authorities: only where required by law.
A customer's advertising account data is not disclosed to anyone else without the customer's consent.
10.1. Cross-border transfers
The Adsy database is located in Kazakhstan. Requests to advertising platform APIs are sent to the platforms' servers, which may be located outside Kazakhstan. Only the data needed for each request is sent: the access token, account and object IDs, and report or change parameters. Service emails may be processed by the email service provider outside Kazakhstan.
11. Cookies
The Adsy application uses one strictly necessary cookie, __Host-adsy_session. It holds the session ID after sign-in, is not accessible to page scripts and is sent only over HTTPS. A session ends after 14 days of inactivity and no later than 30 days after sign-in.
The website and the application have no analytics, advertising trackers or third-party cookies.
12. Your rights
You can:
- find out what data Adsy processes about you and receive a copy of it;
- correct inaccurate data (name and language in your profile, anything else on request);
- withdraw your consent and ask for your data to be deleted;
- disconnect an account and revoke Adsy's access on the platform side;
- lodge a complaint with the competent public authority for personal data protection.
Send requests to support@adsy.kz from the email address registered in your Adsy account. If you write from another address, we will ask you to confirm that the data belongs to you. Withdrawing consent to the processing of advertising account data means disconnecting the account: the service cannot work without that data.
13. Children
Adsy is a service for organizations and their staff. It is not intended for anyone under 18, and we do not knowingly collect their data.
14. Changes to this policy
A new version is published on this page with a new date. We notify users of material changes in advance by email or in the application. If we want to use data received from platforms in a new way, we will ask users for consent first.
The rules for using the service are set out in the Terms of Service.
15. Contact
Individual Entrepreneur “Rosemary” (ИП «Rosemary»), 116 Kazybek Bi St., Almaty, Republic of Kazakhstan, phone +7 708 337 0679, email support@adsy.kz.