Privacy policy
This policy explains how CyFlow handles personal data: what we receive, why, how long we keep it, who receives it, and your rights. It is published in Georgian and English; if they differ, the Georgian text prevails. Effective from [to be added].
1. Who we are
CyFlow (cyflow.ge, app.cyflow.ge) is operated by Individual Entrepreneur Levani Gabinashvili (registered in Georgia, with small business status; personal number 01019082789, legal address: Zghvisubani Settlement, Quarter 10a, Building 44, Apartment 48, Tbilisi 0178, Georgia) ("CyFlow", "we"). Questions about data: privacy@cyflow.ge. Phone: +995 574 11 29 08. Support: support@cyflow.ge.
We have not appointed a personal data protection officer. Please send any question about data to privacy@cyflow.ge.
2. What CyFlow does
CyFlow lets businesses receive and answer their clients' messages in one place. Channels: Telegram, WhatsApp, Instagram, Facebook Messenger, Viber, a chat on the business's website, email and SMS. Businesses use CyFlow in two ways: inside another software product (such as Visage) that connects to CyFlow through its API, or directly in the CyFlow Inbox (app.cyflow.ge). Not every channel may be available to every business yet; what this policy says about a channel applies once a business uses it.
3. Our role
- Conversations with a business's clients: the business is the controller of this data: it decides whom it writes to and what. In the CyFlow Inbox, CyFlow is a processor and processes the data only on the business's instructions, under the annex to our terms of use (data processing terms). Through the API, the product is the business's processor and CyFlow is the product's sub-processor, under our agreement with the product.
- CyFlow's own data: CyFlow is the controller of Inbox user accounts, the contact details and keys of product representatives, connection and security data (who connected a channel, access tokens, audit records, deletion request records, rate limits), and the technical data of our website.
- Channels: Telegram, Meta (WhatsApp, Instagram, Messenger) and Viber process messages under their own terms and privacy policies. For WhatsApp, Meta processes messages as the business's processor under Meta's terms for the WhatsApp Business Platform.
If you are a client of a business that uses CyFlow, see section 13.
4. What data we handle and where it comes from
We receive data from the channels (Telegram, Meta, Viber, and our email and SMS providers), from the business and its team, from you when you sign up, and, for Instagram and Messenger clients' names, from Meta's API. Details per channel are on the page Data use and deletion.
- Connection data: the channel's identifiers (Facebook Page, Instagram account, WhatsApp Business account and number, Telegram connection, Viber bot, SMS sender name, the business's CyFlow email address), the account's name, the identifier of the person who connected the channel (their Facebook, Instagram or Telegram user id), the permissions they gave, and the access token (encrypted).
- Client contact details as the channel sends them: id, name and username; a phone number on WhatsApp and SMS; an email address on the email channel; on the website chat, what the visitor types in. For Instagram and Messenger, after the first message the Inbox asks Meta for the client's name (and Instagram username) and stores it encrypted.
- Messages: text, captions, descriptions of files (type, size, name), and the delivery and read receipts, edits and deletions the channel reports. On email also the subject and thread identifiers.
- Files (photos, voice messages, documents): the Inbox keeps an encrypted copy, because channels expire their file links within days. Through the API, files are streamed from the channel and not stored, except email attachments, which are kept encrypted.
- WhatsApp Business app numbers: if the business allows it in Meta's dialog, we receive its WhatsApp contacts (names and numbers), about the last six months of its chat history, and the messages it later sends from the app on its phone.
- Comments (only if the business turns them on): the commenter's name or username and the comment on the business's own Instagram and Facebook posts, the business's public replies, and one private reply.
- SMS: the business's sender name and the description it writes, sent to uBill for approval.
- Inbox account: name, email, password (as a hash only; we cannot see the password), language, team membership and role, sign-in sessions (a device label such as "Chrome, Windows" and the last activity time), the two-step sign-in secret (encrypted) and recovery codes (as hashes), invitations (the invitee's email and who invited them); the mobile number, proved with a one-time SMS code, and the personal ID number (both encrypted); for the business, whether it is a company or an individual entrepreneur, a company's identification code (encrypted), and whether CyFlow has approved it.
- What a team creates in the Inbox: notes and details it adds about clients (name, phone, email, birthday, tags), saved replies (all encrypted), who handles which conversation, and who sent each reply.
- Notification settings, if a user turns them on: the id of their Telegram chat with the CyFlow bot and the address of their browser's push service (both encrypted). A Telegram notice holds only the workspace name, how many chats wait for an answer and a link; a browser notification is empty.
- A webhook, if the workspace owner sets one: its address and signing secret (encrypted), and the events waiting to be sent (encrypted).
- Product representatives: contact details, the API key (as a hash only), the webhook address and secret (encrypted).
- Technical data: the network address (IP) of a device, to limit sign-up, sign-in and password reset attempts (on the website chat only a shortened one-way hash); our hosting provider's request logs (IP, browser, address, time); message metadata (id, direction, type, time, the client's identifier in the channel); security audit records (who did what and when, including who opened which conversation, without message content or phone numbers); records of deletion requests from Meta (the person's id only as a one-way hash).
5. Why we use data, and on what ground
We process the data we control:
- To run Inbox accounts: sign-up, sign-in, two-step sign-in, sessions, invitations and system emails (confirmation, password reset). Ground: performing our contract with you.
- To check who opens an account and who stands behind a business before it can use the Inbox: we prove the mobile number with an SMS code, and before approving the business our staff check the personal ID number and, for a company, its identification code (for example in the Public Registry). Only the staff who review sign-ups see these numbers, and each view is logged. Ground: performing our contract with you, and our legitimate interest in preventing fraud, impersonation and misuse of the channels connected through CyFlow.
- To connect and run channels for a business, including the identifier of the person who connected them. Ground: performing our contract with the business; for that person, our legitimate interest in running the connection they set up and in being able to show who set it up.
- For security and to prevent abuse: rate limits using network addresses, duplicate checks, audit records. Ground: our legitimate interest in keeping the service and our users' data secure and in being able to establish what happened in an incident.
- To carry out deletion requests from Meta and other channels, and to keep a record that we did. Ground: obligations under the law and the channels' terms, and our legitimate interest in proving that we met them.
- To answer lawful requests from authorities and keep accounting records. Ground: a legal obligation.
- To send Telegram notices and browser notifications. Ground: a service you asked for; you turn them on and can turn them off at any time.
- To send service messages about CyFlow (security, changes to the terms). Ground: performing our contract.
These grounds are set out in Article 5 of the Law of Georgia on Personal Data Protection and, where it applies, Article 6 of the EU General Data Protection Regulation (GDPR). Where we rely on a legitimate interest, you can ask us to stop the processing (section 14).
We send Inbox users only service emails. We will send news or offers (direct marketing) only with your separate consent, which you can withdraw at any time.
To create an Inbox account you must give a name, an email, a password, a Georgian mobile number and your personal ID number; the person who registers a business also says whether it is a company (with its identification code) or an individual entrepreneur. Without them we cannot open the account or approve the business. Everything else is optional. A person at CyFlow approves every business; we make no decisions about you by automated means alone.
For conversations we process for a business, the business chooses the legal ground and informs its clients.
6. What we never do
We do not sell, rent, license or buy data received from Meta, Telegram or any other channel; we do not use it for advertising, to build or enrich profiles of people, for surveillance, or to decide whether anyone qualifies for housing, employment, insurance, education, credit, government benefits or immigration status; we do not combine data of different businesses; we do not pass it to data brokers; and we do not use messages, files or contact data to train or improve artificial intelligence models, ours or anyone else's. We share data only as section 8 describes.
CyFlow uses no artificial intelligence on conversations. If we add such a feature, it will be optional and described in this policy before it starts; we will never use WhatsApp data to train artificial intelligence models.
The Inbox lets a business keep notes and details about its own clients. That is the business's data, kept only in its workspace, and CyFlow uses it for nothing else.
7. How long we keep data
- Message text in the delivery queue (encrypted; through the API and in the Inbox): deleted 30 days after the message arrived or was sent, whether it was delivered, delivery finally failed (after about 2 days of tries), or the copy is still waiting because the product has no working webhook address.
- Message metadata (id, direction, type, time, the client's identifier in the channel): 90 days.
- Time of the client's last message (for the reply window): 30 days; on email, SMS and the website chat: 90 days.
- Email subject and thread identifiers, and the name, phone and email a website chat visitor types in (encrypted): 90 days after the last update.
- Email attachments (encrypted): 30 days.
- Website chat replies the visitor's browser has not picked up yet (encrypted): deleted when picked up, at most 30 days.
- Duplicate-check records: 30 days. Connect codes (hash only): 7 days after use or expiry.
- Rate-limit counters, including the network address (IP) of a device at sign-up and sign-in: 1 day.
- Inbox messages and files: for the period the workspace owner chooses: 90 days, 365 days (the default), or until the owner deletes the workspace. Older messages and files are deleted automatically every day.
- An Inbox conversation, its notes and client details: deleted when no message is left in it, or when the workspace is deleted.
- Inbox sign-in session: 30 days. Email links: confirmation 3 days, password reset 1 hour; the record is deleted 7 days after use or expiry. Invitations: valid 7 days, deleted 30 days after they expire.
- Inbox webhook events: the content is deleted once sent, or after about 2 days of failed tries; the record of the call (without content) after 7 days.
- Notification settings (Telegram chat id, browser notification address): until the user turns them off.
- Inbox user account (name, email, password hash, two-step sign-in data): until the user deletes it (Settings > Delete my account). The mobile number and personal ID number go with the account, a company's identification code with the workspace; a one-time SMS code is valid for 10 minutes and deleted as soon as it is used. An account that no longer belongs to any workspace and is not signed in anywhere is deleted 30 days after it was created. No separate time limit is set yet for sign-ups that were never confirmed.
- Connection record (channel id and name): 1 year after disconnection the name, the owner's id and other details are erased, and the record itself is deleted once nothing refers to it (Inbox conversations keep it until the workspace deletes them). Business record (name and the id the product gave it): kept after disconnection; no time limit is set yet. The channel's access token is deleted as soon as the channel is disconnected.
- Security audit records (who did what and when; no message content and no phone numbers): deleted 2 years after they were made. Records of deletion requests from Meta (code, date, the person's id only as a one-way hash): deleted after 2 years; until then the status page shows the result of the request.
- Hosting request logs: [to be added] days. Database backups: deleted data is gone from the backups within [to be added] days.
- Our email and SMS providers keep copies of mail and SMS under their own rules; we are confirming the periods and will state them here.
How to have data deleted sooner is described on the page Data use and deletion. Once paid plans exist, we will keep accounting records for the period Georgian law sets.
8. Who receives data
- The business and its team (Inbox): every member of a workspace sees all its conversations, including Instagram and Messenger messages.
- The product (API) the business uses.
- The business's webhook, if the workspace owner sets one (for example the business's CRM or an automation service): CyFlow sends client details and messages there on the business's instruction; the business is responsible for that address.
- The channel itself (Telegram; Meta for WhatsApp, Instagram and Messenger; Viber) when a message is sent, and for email and SMS our service provider (see below). CyFlow runs the website chat itself.
- Telegram, if a team member turns on Telegram notices (only the workspace name, how many chats wait, and a link), and browsers' push services (Google, Mozilla, Apple, Microsoft), if a user turns on browser notifications (only an empty signal).
- uBill, our SMS provider, receives your mobile number and the one-time code in order to text it to you.
- Professional advisers (lawyers, auditors) bound to confidentiality.
- Public authorities and courts: only where the law of Georgia requires it, for example on a court ruling. Unless the law forbids it, we tell the business concerned first.
- A new owner, if CyFlow is sold or merged: account data may pass to it; data received from Meta only with Meta's consent.
Processors (service providers) that process data on our behalf:
- Supabase, Inc.: Database and encrypted file storage; data location: Germany (Frankfurt, EU); company registered in: USA.
- Vercel Inc.: Hosting: servers, website delivery and request logs; data location: Germany (Frankfurt, EU); the public website pages are served from a worldwide network; company registered in: USA.
- [email service: to be confirmed]: System emails (sign-up, password reset, invitations) and replies sent through the email channel; data location: [to be confirmed]; company registered in: [to be confirmed].
- Postmark [legal entity to be confirmed]: Receiving mail sent to the business's CyFlow address; data location: [to be confirmed]; company registered in: USA [to be confirmed] (only for the email channel).
- uBill [legal entity to be confirmed]: Sending and receiving SMS, approving sender names, codes that verify Inbox users' mobile numbers; data location: Georgia [to be confirmed]; company registered in: Georgia (for SMS and sign-up codes).
9. Transfers outside Georgia
We store data in Germany (Frankfurt, EU). Germany and the other EU states are on the list of countries with adequate data protection set under Georgian law.
Supabase, Inc. and Vercel Inc. are registered in the United States, which is not on that list, and their staff may be able to access data from outside the EU, for example for technical support. Our email provider may process mail outside the EU. Such transfers are made only on a ground under Article 37 of the Law of Georgia on Personal Data Protection: [to be added]. Where the GDPR applies, we use the safeguards in each provider's data processing agreement (the European Commission's standard contractual clauses, or the EU-US Data Privacy Framework where the provider is certified). You can ask us for a copy of the safeguards at privacy@cyflow.ge.
CyFlow's staff work in Georgia. When a client writes through Telegram, WhatsApp, Instagram, Messenger or Viber, that channel processes the message under its own terms, in the countries where it operates.
10. Security
Messages, files, client details, notes, names received from Meta, notification addresses and channel access tokens are encrypted at rest (AES-256-GCM). Passwords are stored only as a strong hash (scrypt), and product keys, connect codes and recovery codes only as hashes. Each product and each Inbox workspace can reach only its own data. All connections are encrypted (HTTPS). Two-step sign-in is available for Inbox accounts. Access to our systems is limited to people who need it for their work and who are bound to confidentiality.
The encryption is not end-to-end: CyFlow holds the keys so that the service can show messages to the business's team and deliver them. Our staff do not open conversations, except when the business asks for help, to deal with a security incident, or when the law requires it.
Access to personal data is logged: when an Inbox team member opens a conversation, and when CyFlow staff open a connection's page in our administration area (it shows the ids of clients who wrote recently), we record who, when and which conversation or connection, without message content. Repeated views by the same person within an hour are recorded once. Every deletion we carry out on request is recorded too. These records are kept with the audit records. They do not cover direct technical access to the database, which only named staff have.
To report a security vulnerability, write to security@cyflow.ge.
11. Incidents
If a security incident affects personal data, we act to limit its effects. As a processor, we tell the affected businesses and products without undue delay. Where we are the controller, we report the incident to the State Audit Office of Georgia within 72 hours as the law requires, and if it puts your data at high risk we tell you without undue delay. We also inform Meta, Telegram and other channels as their terms require.
12. Cookies and similar technologies
CyFlow itself uses no analytics or advertising cookies. We use:
- cy_session (app.cyflow.ge): the sign-in session; we store only its hash; 30 days.
- cy_mfa (app.cyflow.ge): the step between the password and the two-step sign-in code; 5 minutes.
- cy_lang (app.cyflow.ge): the chosen language; 365 days.
- cy_fb_pending (cyflow.ge, the Messenger connect page): the Facebook access token (encrypted) while you choose a Page; 10 minutes.
- cy_admin (cyflow.ge/admin): CyFlow staff sign-in; 12 hours.
- Browser local storage ib-theme and ib-panel (app.cyflow.ge): colour theme and panel layout, until you clear them.
- A service worker and a notification subscription (app.cyflow.ge): only if you allow notifications in your browser.
On the page where a business connects WhatsApp (cyflow.ge/connect/whatsapp), Meta's JavaScript SDK loads from Meta's servers only when you press the "Connect WhatsApp" button, so that Meta's sign-up dialog can run. Nothing from Meta loads when the page opens. Once it has loaded, Meta receives technical data about your device and may set its own cookies. Automatic app event logging (autoLogAppEvents) is switched off. Meta processes this under its own privacy and cookie policies; CyFlow does not receive it.
The website chat keeps the conversation (the last 200 messages) and a visitor id in the visitor's browser (local storage) on the business's website. The business tells its visitors about this.
13. If you wrote to a business that uses CyFlow
If you wrote to a business through its website chat, Telegram, WhatsApp, Instagram, Messenger, Viber, email or SMS and the business uses CyFlow, that business is the controller of your data. CyFlow processes it for the business. To use your rights, please contact the business first.
If you write to us (privacy@cyflow.ge), we pass your request to the business within 2 working days and help it answer you within the legal deadline. We act on the business's instruction, and on our own only where the law requires it. A public comment stays public on Instagram and Facebook; CyFlow keeps only a copy for the business.
14. Your rights
Under Chapter III of the Law of Georgia on Personal Data Protection you can ask us for:
- information about how we process your data (Article 13);
- access to your data and a copy of it (Article 14);
- correction, updating and completion of your data (Article 15);
- the end of processing, erasure or destruction of your data (Article 16);
- blocking of your data (Article 17);
- your data in a structured, machine-readable form, or its transfer to another controller (Article 18);
- where processing is based on consent, withdrawal of consent at any time (Article 20).
We make no individual decisions about you by automated means alone (Article 19). Write to privacy@cyflow.ge. We check that the request comes from you. Requests are free of charge. We answer within 10 working days; in exceptional cases this may be extended by up to 10 more working days, and we tell you why straight away. The owner of an Inbox workspace can download its data in Settings (JSON and CSV).
If you believe your rights have been breached, you can apply to the State Audit Office of Georgia, which supervises personal data protection (sao.ge), or to a court.
CyFlow is established in Georgia. If the GDPR or the UK GDPR applies to our processing of your data, you also have the rights those laws give, including the right to object to processing based on legitimate interests; you get our answer within one month in any case, and you can complain to the data protection authority of the country where you live or work (in the United Kingdom, the ICO).
15. Age
The Inbox and the API are for businesses and their staff, who must be at least 18. We do not knowingly collect children's data for our own purposes. A business's clients may be under 18; the business is responsible for having a legal ground to process their data, including a parent's consent where the law requires it.
16. Deleting data and removing CyFlow
How to disconnect a channel, delete a workspace, an account or one client's conversation, and what each step deletes and what it does not, is described on the page Data use and deletion. You can also remove CyFlow in your Facebook or Instagram settings: Meta then sends us a deletion request and gives you a confirmation code to check its status on our status page.
17. The Telegram Business bot
When you add the CyFlow bot under Telegram Business, it receives the messages in the chats you give it access to, keeps them as this policy describes, and passes them only to your Inbox or to the product you connected. We tell you before any significant change to how the bot works, so that you can remove it if you wish.
18. Changes
We publish changes to this policy on this page with a new date. We tell Inbox workspace owners and products about a material change by email at least 30 days before it takes effect. Earlier versions are available on request at privacy@cyflow.ge.