Privacy
In effect since 2026-11-16
The Ukrainian text is the one that governs. This is a translation of it.
This is the text in force. Read the text in force
Privacy Policy
This Policy describes what personal data is held on the Platform, about whom, on what grounds, where, for how long and to whom it goes, under the Law of Ukraine "On Personal Data Protection".
1. Terms and definitions
1.1. In this Policy the terms below have these meanings:
Operator: the person named in section 14, who runs the Platform.
Platform: the Operator's software service that lets a Shop be run.
Shop: a Seller's shop on the Platform.
Seller: a person who opened a Shop and sells through it.
Buyer: a person who browses a Shop, places an order in it or writes to it.
Visitor: a person who opened this page.
Controller: whoever decides why and how personal data is processed.
Processor: whoever processes personal data on a Controller's instruction.
2. Controller, processor and grounds for processing
2.1. For a Buyer's data the Controller is the Seller whose Shop the Buyer ordered from or wrote to: the Seller collects their Buyers' data for themselves. The Operator is the Processor: it holds this data for that Shop and for nothing else, except what clause 2.7 names.
2.2. For a Seller's and a Visitor's data, and for what clause 2.7 names, the Controller is the Operator.
2.3. About anything in this Policy, write to the Operator at support@instatg.com.
2.4. The Platform asks no separate consent for the processing described here. The grounds are named as in article 11 of the Law of Ukraine "On Personal Data Protection".
2.5. The Seller processes a Buyer's data to fulfil the order the Buyer placed and to answer what the Buyer wrote: the ground is entering into and performing a transaction, and the steps before it, at the Buyer's request. If the Seller processes this data for anything else, the Seller determines the ground for that. The Operator processes it under its contract with the Seller.
2.6. The Operator processes a Seller's data to enter into and perform the contract with them. What the Shop paid the Platform the Operator also keeps because recording income is its duty under the law.
2.7. The records that keep the Platform running, failure reports, the records of a Visitor's arrival, the Operator's own records about Sellers (clause 5.4) and letters to support@instatg.com are processed on the ground of legitimate interest: for the Platform to work and be protected, to know where people come from, to remember conversations and to answer letters.
2.8. Only on the Seller's instruction, which is section 7 of the contract with them, the Operator processes everything section 3 describes: orders, carts, conversations and records of Buyers. For its own purposes the Operator processes the Seller's data (section 5), what the Shop paid the Platform (clause 4.5), the Visitor's data (section 6) and what clause 2.7 names. A Buyer's name or phone quoted in a failure record on the Platform's server is likewise processed on the Seller's instruction only and deleted within the period clause 9.4 names.
2.9. To whom a Buyer's data goes is the Seller's decision: by accepting the contract the Seller agrees to the services listed in clause 8.1, and the Seller themselves connects those named in clauses 8.2 and 8.4 to 8.6. Buyers' requests are answered by the Seller, with the Operator's help (section 4); a demand to delete data a Buyer sends to the Shop.
2.10. Of the services in section 8, Hetzner, Cloudflare, Sentry, Grafana Labs, Zoho and Anthropic act on the Operator's instruction: each processes only what is named, on terms that bind it to look after the data as the Operator does. Independent controllers of what they receive are Meta for the WhatsApp number, Paddle, LiqPay and monobank for a plan's payment, and the Payment Service, Nova Poshta, the AI agent and the video services the Seller connected: their processing is described in their own policies.
3. A Buyer's data
3.1. When a Buyer places an order, the Shop records what they ordered, their name and phone, the delivery method and the address exactly as they wrote it, a comment, the chosen way of paying, and the Telegram account or WhatsApp number the order came from.
3.2. If a Buyer pays by card, whether the payment went through is recorded. The Platform does not see the card number.
3.3. If a Buyer writes to the Shop through its bot, that conversation is held too, along with what the Buyer declared about an order, such as withdrawing from it.
3.4. If a Buyer writes to the Shop's WhatsApp number, the Shop records who wrote, the number written from where WhatsApp shows it, and when the Shop answered, but never what the Buyer or the Seller wrote. The words stay in WhatsApp and in the Seller's app.
3.5. The Shop answers with a link that opens it in the Buyer's browser in the Buyer's name. The browser that opened it first keeps a key for 30 (thirty) days in the page's own storage (localStorage), not in a cookie, so the Buyer returns to the same cart and orders. The key opens only this Shop in this browser and goes to nobody.
3.6. The page of an order placed in the browser offers to tell the Buyer when the order's status changes, if the browser can take it. If the Buyer agrees, the browser gives the Shop an address to deliver notifications to and the keys that seal a notification for it; the Shop records them beside that browser or that order and nothing else. A notification is sent only when the order's status changes and holds the Shop's name, the order's number and its status. It is delivered by the service of the browser's maker (clause 8.7), which cannot read it. What was recorded is gone as soon as the Buyer turns notifications off on the same page, the service says the address is gone, or the Buyer or the order is deleted (section 4).
3.7. When a Buyer puts an item in the cart, the cart and the account they came from are recorded. If the Shop turned on cart reminders, the bot sends the Buyer a reminder of it. Nothing more is recorded about browsing the Shop. There are no cookies, no identifier that follows browsing, no list of pages viewed, and no profile built from their actions. Videos in a Shop are the subject of clause 8.6.
3.8. The Platform does not establish who is browsing a Shop. Apart from that, the server that serves the Shop's page and the service that receives failure reports see the device's internet address, as any server on the internet does. If a Shop's page breaks on a Buyer's device, it sends a failure report; the report is built to leave out the Buyer's name, address and phone.
3.9. The Seller the Buyer ordered from sees the order and the conversation with them. Someone selling in another shop does not. Besides the Seller, those who keep the Platform running can reach them and are bound to keep them confidential. The data rests on the server and in the backups named in sections 7 and 8.
3.10. If the Shop's plan includes bot answers, the message a Buyer writes to the Shop's bot may be passed by the bot to Anthropic, to compose an answer from what the Shop knows about it. The Shop sees both the answer and that the bot composed it. Each such answer is marked to the Buyer as automatic. The Buyer's name, phone, address and Telegram account from the Shop's records are not passed to Anthropic; whatever the Buyer writes in the message itself goes with it. The Platform does not strip a phone, an address, an email or anything else the Buyer wrote themselves from the message; so neither the Shop nor the Operator asks a Buyer to write to the bot data whose processing article 7 of the Law restricts (health, beliefs and the like). Bot answers work while the Shop's plan includes them; the Seller turns them off by changing the plan. How long Anthropic keeps what is sent is set by its terms, named in clause 8.1.
4. A Buyer's requests and deletion
4.1. To learn what is recorded about them, correct it, get a copy of it or delete it, a Buyer writes to the Shop in its bot or on its WhatsApp number. The Shop recognises the Buyer by the Telegram account or WhatsApp number the order was placed or the message written from: a request from another account the Shop first checks with the Buyer. The decision on the request is the Seller's, as the controller. If a Buyer writes to support@instatg.com, the Operator passes the letter to the Shop within 10 (ten) working days and does what the Shop decides; the request is carried out no later than 30 (thirty) calendar days from its receipt, as article 16 of the Law requires. If the Shop does not answer, the Buyer writes to support@instatg.com.
4.2. At a Buyer's request the Seller deletes them from any order: their name, phone, address, account, comments, reasons for withdrawing, cart and conversation, what the Shop recorded about their messages to the WhatsApp number, and the answers the bot composed for them, are gone.
4.3. What remains after that is what the law obliges the Seller to keep as the record of a sale that happened: the order's items, amounts, dates and states, and the payment's numbers at the Payment Service, by which the Seller finds the payment in a dispute with a bank. The waybill number also remains, which names a parcel and not a person. One Buyer's orders stay linked to each other by an internal number that, after the deletion, points to nobody. A Nova Poshta waybill, once created, keeps the recipient's phone as long as the Shop exists, since by it Nova Poshta reports the parcel's state; this is a technical need of the Shop, not a requirement of the law.
4.4. The Seller deletes the whole Shop in its settings: the catalog, orders, records of Buyers, conversations, the bot token and, if the Shop connected a WhatsApp number, the number itself and everything recorded about people who wrote to it. Before that the Seller may get a copy of the Shop in the same settings: the catalog, orders, conversations, remembered answers, settings and photographs, as files in the chat with the Shop's bot and nowhere else.
4.5. What the Shop paid the Platform is not deleted: it stays the Operator's own record of income and is kept as clause 9.6 says.
4.6. A Seller who disconnects a WhatsApp number keeps the Shop; the number's key is forgotten at once.
4.7. What is deleted leaves the backups within 7 (seven) days at the latest: no backup is kept longer.
4.8. Meta's request to delete data obtained through a WhatsApp number leads to this section.
5. A Seller's data
5.1. A Shop is opened with a bot token from Telegram. The token is held encrypted, decrypted only to call Telegram, in the Shop's name or to check that the bot works, and shown on no screen.
5.2. Beside the token the Platform keeps the Telegram account that opened the Shop, the date and time of opening, which is the date the contract with the Operator was accepted, the Shop's settings, its catalog and orders.
5.3. A Seller who connects a WhatsApp number gives the Shop the key Meta issues for that number. The key is held encrypted, as the bot token is, decrypted only to call Meta about this number, and shown on no screen. Beside it the Platform keeps the number, the name Buyers see, and what Meta says about its state.
5.4. The Operator keeps its own record about a person it talks to about a Shop: what to call them, what and how much they sell, how they found the Platform, how the conversation ended, and their Telegram nickname and profile photo. Such a record can appear before a Shop is opened and stays after it is deleted, but no longer than 3 (three) years after the last conversation, the limitation period of article 257 of the Civil Code of Ukraine. To have it deleted earlier, write to support@instatg.com.
5.5. If a Seller pays for a plan by transfer to the Operator's account, the Operator receives what its bank shows in the statement, including the payer's name, their account and the purpose of the payment. This stays in the Operator's own income records, as clause 4.5 says.
6. A Visitor's data
6.1. What is held is that someone came, when, and by which link. Not who. There is no identifier, nothing is written to the Visitor's device, and two visits by one person cannot be told from visits by two. The server that serves this page sees the device's internet address, as clause 8.1 names.
7. Where it is held
7.1. Shops, orders and conversations are held on a server in Nuremberg, Germany. Backups and the Shops' images rest in Cloudflare's storage in the region Cloudflare calls "Eastern Europe", naming no country; there is no other backup location. A backup is made every 6 (six) hours and kept no longer than 7 (seven) days (clause 4.7).
8. To whom data goes
8.1. Each service receives only what this section names:
Hetzner, Germany (Nuremberg): the server the Shops run on: everything described above.
Cloudflare, Eastern Europe (a region; Cloudflare names no country): backups of the same, and the Shops' images.
Sentry, Germany: failure reports: from a device when a Shop's page breaks, with the device's internet address, and from the Platform's server. Reports are built to leave out a name, an address or a phone number.
Grafana Labs, United Kingdom: records that keep the Platform working, without the fields that could quote what something broke on.
Zoho, European Union: the mail at support@instatg.com: what people write to the Operator.
GitLab, United States: serves this page and, like any server, sees the device's internet address.
Meta Platforms Ireland, European Union: only for a Shop that connected a WhatsApp number: Meta tells the Platform who wrote to the number and when, and delivers to whoever wrote the Shop's single answer, its name and a link.
Anthropic, United States: only for a Shop whose plan includes bot answers: a Buyer's message to the Shop's bot and what the Shop knows about it: a product's description and prices; an order's number, items, amount, delivery and payment methods, dispatch date and tracking number; the Shop's delivery and payment methods; and answers the Seller asked to remember. A Buyer's name, phone, address and Telegram account from the Shop's records, and nothing about other Buyers, are not passed; whatever the Buyer writes in the message itself goes with it. Anthropic's terms forbid it to train its models on what is sent to it; how long it keeps what is sent is set by the same terms.
LiqPay and monobank, Ukraine: only for a Seller paying for a plan: the amount, period and number of the payment, and to LiqPay also the name of the plan and the Shop. The Seller enters card details on that service's page, and the Platform does not receive them. The service keeps the card for later charges if the Seller allowed it.
Paddle, United Kingdom: only for a Seller whose Shop works outside Ukraine and who pays for a plan through Paddle: the name of the plan, the period, the amount and the number of the payment; Paddle is not told the Shop's name. Paddle sells the plan as the merchant of record: the Seller enters their email address, country and card details on Paddle's page, and the Platform does not keep them. Paddle keeps the means of payment for later charges and finds by that email address a payment asked back.
8.2. If a Buyer pays by card, the bank the Shop connected receives, into the Shop's account, the order number, its items and the amount. It is the Shop's bank and not a service the Platform runs on.
8.3. Telegram carries messages and orders between a Buyer and the Shop's bot. It is the channel the Buyer chose and not a service the Platform hands anything to.
8.4. If the Shop connected Nova Poshta under its own key, then when the Seller creates a waybill Nova Poshta receives the recipient's name and phone, the branch, the items' names, the declared value and the cash-on-delivery amount, and afterwards the waybill number and the phone, to report its state. It is the Shop's carrier and not a service the Platform runs on.
8.5. If the Seller connected their own AI agent, that agent, with the Seller's permission, reads the Shop's orders, including the recipient's name and phone, the address and the comment. It is the Seller's tool and not a service the Platform runs on.
8.6. If the Seller added a video from YouTube, TikTok, Vimeo or Instagram to a product, then when a Buyer presses play that service receives the device's internet address and may write its own cookies to it. Before the press it receives nothing. It is a service the Seller chose and not a service the Platform runs on.
8.7. If the Buyer agreed to notifications (clause 3.6), the notification service of whoever made their browser, Google, Mozilla, Apple or Microsoft, receives the sealed notification and the address the browser gave. It cannot read the notification. It is the service of the browser the Buyer chose, not a service the Platform runs on.
9. How long it is kept
9.1. Orders, carts, conversations and the Shop are kept as long as the Shop exists. A Seller who deletes the Shop deletes everything in it except what the Shop paid the Platform. A Shop the Operator deleted for long inactivity under its contract with the Seller goes the same way, and a Shop the Operator stopped serving no earlier than 30 (thirty) days after that, as the contract says. A Buyer asks the Shop about their own orders.
9.2. A record that the Shop answered someone on WhatsApp is kept while the Shop exists. A link nobody opened stops opening after a day, and an opened one after 30 (thirty) days. The key in the Buyer's browser (clause 3.5) lives 30 (thirty) days. A browser's address for notifications (clause 3.6) is kept until the Buyer turns them off, the service says the address is gone, or the Buyer or the order is deleted.
9.3. Answers the bot composed and what they rested on are kept while the Shop exists; an answer the Seller asked to remember, until the Seller removes it. Records of a Buyer whose data was deleted go with the rest, and with them any remembered answer to their question. What was sent to Anthropic it keeps on its own terms (clause 8.1).
9.4. Records that keep the Platform working (that a step happened, that a request was refused) are kept on the Platform's server no longer than 14 (fourteen) days, and the Shop's internal journal of events for 30 (thirty) days. When something breaks, a record on the server may quote what it broke on, including order data; that part of the record stays on the server no longer than 14 (fourteen) days and does not reach Grafana. What Grafana Labs and Sentry received they keep on the terms of their services, within the limits the Operator set there.
9.5. The Operator's own record about a Seller (clause 5.4): no longer than 3 (three) years after the last conversation. Letters to support@instatg.com: while the correspondence lasts and 3 (three) years after it, for the same reason.
9.6. What the Shop paid the Platform, and what the Operator's bank showed about the payer (clause 5.5): at least 1095 (one thousand and ninety-five) days after the reporting period in which it was received, as article 44 of the Tax Code of Ukraine requires.
9.7. Backups: no longer than 7 (seven) days (clause 4.7).
10. Protection of data
10.1. Data travels only over protected connections: between a Buyer's or Seller's device and the Platform, and between the Platform and each service in section 8.
10.2. The bot token, the WhatsApp number's key and the keys of connected services are held encrypted and decrypted only to call the service concerned; no screen shows them.
10.3. Each Shop sees only its own orders, Buyers and conversations: the storage itself ensures this, not only the screen. Those who keep the Platform running can reach the data only as far as its upkeep requires, and are bound to keep it confidential.
10.4. Tokens, keys and passwords do not reach the records that keep the Platform working or the failure reports, and the fields that could quote what something broke on do not reach Grafana.
10.5. Backups are made continuously, only the Operator can reach them, and restoring from a backup is tested.
10.6. Of a breach of the security of Buyers' data the Operator tells the Seller without undue delay, naming which data it concerns and what has been done; a Seller or a Visitor whose data it concerns learns of it from the Operator in the same way.
11. What the Platform does not do
11.1. None of this data is sold, rented or passed to advertisers.
11.2. There is no tracking on other sites, no advertising network, and no analytics service watching how this page is read.
12. Changes to this Policy
12.1. A change to the list in section 8 is a change to this Policy: it has its own date, and the previous text stays available.
13. Rights over personal data
13.1. Everyone whose data this Policy describes has the rights set by article 8 of the Law of Ukraine "On Personal Data Protection", among them:
— to know who processes their data, why, where it is held and to whom it goes;
— to have access to their data;
— to object to the processing;
— to demand that data be changed or destroyed if it is processed unlawfully or is inaccurate;
— to know how automatic processing works and to be protected from an automated decision with legal consequences for them;
— to withdraw consent, where the processing rests on it.
13.2. A Buyer turns to the Shop about these rights, as section 4 describes. A Seller or a Visitor turns to the Operator at support@instatg.com.
13.3. A complaint about the processing of personal data can be brought to the Ukrainian Parliament Commissioner for Human Rights or to a court.
14. The Operator
ФОП Латковська Вікторія Валеріївна. Email: support@instatg.com. The Operator's other details are in section 15 of the Public contract for services of access to the platform.