Kairo Studio Privacy Policy
Effective date: 2026-11-10
This policy explains how Fittcoaching LLC handles personal data in Kairo Studio: the Studio app at https://app.kamalov.systems/studio/ and at an agency's own address, the Instagram and Facebook connection, inbox and data deletion pages on app.kamalov.systems, and the AI agent that answers Instagram messages and comments, Facebook Messenger messages and the chat on a business's own website for businesses, with the tools to import a business's facts from its website or its files, to write, approve and publish a business's Instagram and Facebook Page posts, to show its numbers, to moderate the comments on its Facebook Page, to collect the answers to its Facebook lead ads, and for agencies to run Studio for their clients (together, "the Service"). It does not cover the kamalov.systems website, or the website of a business that uses the chat.
The short version.
- Two groups of people are covered. For business users of Studio, including agencies and the people they invite, we decide how their data is used. For people who message or comment on a business's Instagram account or Facebook Page, write in the chat on its website, or answer its Facebook lead ads, that business decides, and we process their data only for it.
- An AI model from OpenAI, in the United States, writes and checks the replies. Instagram and Messenger messages and comments go to OpenAI alone: when it does not answer, the message waits and is answered later, and a message that can no longer be answered within 24 hours gets no reply. For the rest, such as the website chat, test chats and drafting, Mistral AI, in France, takes over when OpenAI does not answer. The AI models receive the text of messages, never Instagram or Facebook names, and no Instagram, Facebook or website visitor ID (section 5).
- Instagram and Messenger messages, Instagram comments and website chat messages are kept for 30 days, then deleted.
- The chat on a business's website stores a random ID in each visitor's browser, to keep their conversation together. It sets no cookie (section 3.6d).
- An agency can run Studio for other businesses, its clients. Its logins then see and change those businesses' data in Studio (section 3.1a).
- We send password reset links and agencies' invitations by email, through Resend.
- For each person who writes or comments, a business's Studio keeps a lead record: where the conversation stands, counts and times, never the text. For a person who answers a Facebook lead ad, the record holds the answers they gave in the form, such as their name, email address and phone number. A lead record is kept 12 months after the last activity on it.
- A business can publish posts to its Instagram account or Facebook Page from Studio. Nothing is published until the business approves it. The pictures and videos are stored on our server only until the post is published (or, for a draft, seven days after its last change), and Instagram's or Facebook's servers download them from our server to publish them.
- The numbers Studio shows for an Instagram account or a Facebook Page (such as reach, views, likes and reactions), and the recent comments on a Facebook Page, are read from Meta when you open those pages. Our server stores the last answer so that a reload does not ask Meta again. The daily clean-up deletes it once it is more than 24 hours old, and it also goes when the agent or the account is deleted.
- On a Facebook Page, the agent answers Messenger messages, never comments. A comment is hidden, shown, answered or deleted only when the business presses that button in Studio.
- We do not sell personal data, and we do not share it for advertising.
- Questions and requests go to [email protected].
1. Who we are
Fittcoaching LLC, a Washington limited liability company, 7654 19th St W, Tacoma, WA 98466-3615, United States. Email: [email protected] ("we", "us"). Studio pages carry the Kamalov Systems name. The Service is ours.
Kairo Studio is not offered to businesses established in the European Economic Area, the United Kingdom or Switzerland, so we have not appointed a representative under Article 27 of the GDPR or the UK GDPR. Write to us at [email protected] about any privacy question.
2. Whose data this covers, and our role
Business users. People who sign up for Studio or work in it for a business or an agency: owners, staff and agency staff, including the people an agency invites by email. For their data we are the controller.
People who message a business. People who send a direct message to, or comment on a post of, an Instagram account that a business has connected to the Service; people who send a Messenger message to, or comment on a post of, a Facebook Page that a business has connected; people who answer a lead ad of such a Page; and people who write in the chat on a business's own website. Here the business is the controller: it chooses to use the Service and decides what its agent says. We process their data only for that business, as its processor and service provider, under our Data Processing Addendum. When an agency runs a business's Studio, the agency acts for that business, and we process the data for the business, through the agency.
If you wrote to a business on Instagram, on Facebook or in the chat on its website, or answered its lead ad, please contact that business first about your data. You can also write to us at [email protected]. We will pass your request to the business, help it answer, and act on it ourselves where the law requires.
Instagram and Facebook are run by Meta, which handles your Instagram and Facebook accounts under its own privacy policy. A business's website is its own, under its own privacy notice.
3. What we collect
3.1 Your Studio account
- your name or your business's name, and your email address;
- if you sign up with your email, your password, stored only as a scrypt hash with its own random salt, so we cannot read it;
- if you sign in with Google, what Google sends us when you choose to: your email address, that Google has verified it, and the name on your Google account, which only fills in the name field for you to change. We receive no Google password and keep no Google token, and Studio asks Google for nothing else.
- account and client identifiers, creation times and, if your business is one of an agency's clients, which agency (section 3.1a);
- the version of the Terms you accepted and when.
If you ask for a new password, or a password for an account you made with Google, we email you a link through Resend (section 4). It works once, for one hour. We do not store the link.
3.1a Agencies and their clients
An agency account lets an agency run Studio for other businesses, its clients.
- What we keep for an agency: its name and referral code; if it sets them, a brand name and a logo (a PNG, JPEG or WebP picture of up to 300 KB, stored on our server under a random name); its list of clients; and the monthly price it records for each client, with its currency. Studio only stores these prices. It does not bill them or collect them.
- How a business becomes a client. An agency can add a business by its name alone and run it itself. A business also becomes its client when it signs up through the agency's referral link or on the agency's own address (section 3.1b). The agency sees how many businesses signed up through its link.
- Invitations. An agency can give a login to a client's owner or to a teammate by typing their email address. We then make a login with that email address and no password, and send one invitation email through Resend, with the agency's name, the business's name and a link that works once, for 7 days. We record which agency login invited the person, when the email was tried and sent, and whether Resend accepted it. The agency can send it again. The person joins by setting a password and accepting our Terms. If nobody does this within 8 days, we delete the login and its invitation record.
- What the agency sees and does. The agency's own logins, and a teammate invited to all its clients, can open every client and see and change what that client's own logins can in Studio: its agents, briefs, facts, test chats, leads with any lead ad answers, website chats, imported facts, posts, numbers and Page comments. They can also act there, for example switch an agent on or publish a post. A teammate invited to one client sees only that business. The agency's logins also see, for each client, whether its agent is live, how many new leads and messages it had in the last 7 days, the email addresses of its logins and whether they have joined. They can remove a client's login, except the last one that has joined, and they can copy an agent's brief and facts from one client to another.
- What a client sees. A client's own logins see only their own business, never the agency's other clients or its prices. If the agency set a brand, they see its name and logo at the top of Studio's pages in place of the Kamalov Systems mark. The logo is shown only to the agency's logins and its clients' logins.
3.1b An agency's own address
An agency can serve Studio at an address of its own, such as studio.youragency.com.
- The agency types the address in Studio and adds a DNS record (a CNAME) that points it to domains.kamalov.systems. We store the address, its state, the times of our checks and their errors, and, when another agency held that name before, a proof code that the agency must publish in its DNS.
- Our server checks the DNS, gets a certificate for the address from Let's Encrypt (section 4) and then serves Studio there. Every certificate is recorded in public Certificate Transparency logs, so the address becomes public.
- At that address, the sign-in and sign-up pages show the agency's brand name, Sign in with Google is not offered, a business that signs up there becomes the agency's client, and only the agency's logins and its clients' logins can sign in. The sign-in cookie (section 3.7) is set for that address.
- Requests to that address come straight to our server, without Cloudflare, and our web server logs them as section 3.7 says. This includes the website chat when its code was copied from Studio at that address.
- When the agency removes the address, or its account is deleted, our server stops serving it and deletes its certificate (the certificate is not revoked). We keep a record of the address, the agency that claimed it and when, also after that, so that no one else can take the address over without proving that they control it.
3.2 Your agents and test chats
- each agent's name, business type, brief, facts, comment keywords and private-reply text;
- the gaps found in tests, whether the agent is live, which Instagram account or Facebook Page it uses and when it was connected;
- the website chat's settings: whether it is on, the site you allow and the key in its code;
- your test chats: what you type in Studio's test chat and the agent's answers, with times.
3.3 Website text and imported files
If you give Studio a website address, our server fetches that page once, keeps up to 6,000 characters of its text in memory, and sends that text, with your own sample text, to OpenAI (or Mistral AI when OpenAI does not answer) to draft your brief and facts. We do not store the page. Our server identifies itself to the website as KairoStudio/1, with a link to https://kamalov.systems.
Importing facts. On an agent's Knowledge page you can give Studio a page of your website or a file: .txt, .md or .csv, and .pdf when our server can read PDFs, of up to 2 MB. Our server reads the page in the same way (up to 6,000 characters of its text), or the file's text in memory (up to 12,000 characters, and at most the first 30 pages of a PDF), and sends that text to OpenAI (or Mistral AI when OpenAI does not answer). The AI lists the facts it finds, such as prices, opening hours, address, phone numbers and links. Studio keeps only the facts whose figures, links and phone numbers appear in the text, as proposals. A proposal reaches the agent's facts only when you press Add. We do not store the file or its text. For each source we store whether it was a page or a file, the page address or the file name, a fingerprint of its text (so that Check again can tell whether a page changed), and when it was first read and last checked. For each proposal we store the fact, the line of your facts it would replace, whether you added it or skipped it, and when. They stay until you delete the agent or the account.
3.4 Your Instagram connection
When you connect an Instagram professional account, you log in and approve access on www.instagram.com. We never see your Instagram password. Instagram then gives our server, through api.instagram.com and graph.instagram.com, the account's Instagram user ID, username and account type, its profile picture, and an access token. We keep a copy of the profile picture to show in Studio, and delete it with the connection. We store these with the token's expiry date, the permissions you granted, when you connected, and your settings. The access token is encrypted at rest.
The permissions we ask for are instagram_business_basic, instagram_business_manage_messages, instagram_business_manage_comments (when the agent answers comments), instagram_business_content_publish (to publish the posts you approve) and instagram_business_manage_insights (to show your account's numbers). You can use Studio without publishing or insights; an account connected before these two permissions existed is asked to reconnect only when you open Posts or Insights.
3.4a Your Facebook Page connection
When you connect a Facebook Page, you log in and approve access on www.facebook.com, through Facebook Login for Business. We never see your Facebook password. Facebook then gives our server, through graph.facebook.com, a user access token. With it, our server reads your app-scoped Facebook user ID, the permissions you granted, and the Pages you manage and chose to share, each with its ID, name and Page access token. We use the user access token only during this step, and we do not store it.
While you choose a Page, our server holds the list of your Pages, with their Page access tokens encrypted. The list is deleted when you choose. If you do not choose within ten minutes, the choice expires, and our server deletes the list within a minute after that.
For the Page you choose, we store its ID and name, its Page access token, the app-scoped ID of the Facebook user who connected it (so that we can act on Meta's removal and deletion requests), the permissions you granted, when you connected, whether Facebook accepted our request to send us the Page's events, and your settings. The Page access token is encrypted at rest. We do not store the Page's picture.
The Service uses these permissions, each only for what is listed:
- pages_show_list: to list the Pages you manage, so that you can choose one;
- pages_messaging: to send the agent's Messenger replies, the follow-ups you set, and the replies you type yourself in Studio (with Meta's human agent tag when more than 24 hours have passed);
- pages_manage_metadata: to receive the Page's Messenger messages and lead ad notices;
- pages_read_engagement and pages_read_user_content: to read the Page's posts and the comments on them;
- pages_manage_posts, and publish_video for a video: to publish the posts you approve;
- pages_manage_engagement: to hide, show, answer or delete a comment when you press that button;
- read_insights: to show the Page's numbers;
- Business Asset User Profile Access: to read the name of a person who messages the Page, as described in section 3.6;
- leads_retrieval, pages_manage_ads and ads_management: to read the answers people give in the Page's lead ads, and which form and ad each answer came from.
Facebook also includes public_profile, from which we read only your app-scoped user ID. If Facebook's screen also lists ads_read or business_management, the Service does not use them to read or change your ads, ad accounts or business settings. You can use Studio for Messenger without the other features. If you did not grant a permission that a feature needs, Studio asks you to reconnect the Page when you open that feature.
3.5 The inbox
The inbox at app.kamalov.systems/inbox lets you read and answer your Instagram messages and comments by hand. To show them, it fetches your conversations, posts and comments, and the names and usernames of the people in them, live from Instagram. We do not store what it shows. We do store each message you send through the inbox (the time, the recipient's Instagram ID and the text), and it joins the agent's conversation history, so the agent knows what was said. Profile pictures and post images load in your browser directly from Instagram's servers. The inbox shows Instagram accounts only, not Facebook Pages.
3.6 Messages and comments on a connected account
When people message or comment on a connected Instagram account, or send a Messenger message to a connected Facebook Page, Meta sends us each event. We store:
- for an Instagram direct message: the sender's Instagram-scoped ID, the message ID, its text and the time;
- for a Messenger message: the sender's Page-scoped ID, the message ID, its text and the time. On the first message from a new person, our server also asks Facebook once for that person's name (never their picture), using the Page's access token, and stores it on the business's lead record so the business sees who wrote. If Facebook gives no name, Studio shows "Messenger user" and the last digits of the ID, and asks again at most once a day;
- for an Instagram comment: the commenter's ID, the comment ID, the ID of the comment it answers, its text and the time.
We keep text only, never photos, videos, voice notes or other attachments. Comments on a Facebook Page do not come to us as events, and the agent never answers them (section 3.6c).
A business can also answer an Instagram or Messenger conversation itself, from the person's card in Studio. We store that reply (the text, who it is for, when it was asked for and sent, and whether Meta accepted it), send it through Meta, and add it to the conversation history so the agent knows what was said. After such a reply, the agent and the follow-ups stay quiet with that person for 24 hours, or until the business hands the conversation back. A reply is sent only within 7 days of the person's last message.
To answer, and to keep the agent consistent, we also keep:
- each person's conversation with the agent: the last 20 messages, the IDs of the messages already answered, and the times of the last hour's replies;
- every reply the agent sends, with the message it answers, the time, the account, the person's ID, whether it was a message or a comment, whether the message asked for a person or raised a complaint, and Meta's response;
- drafts: an Instagram account or Facebook Page connected outside Studio, for example through the inbox, may get a reply written and stored as a draft that is never sent. A Studio agent that is switched off or not ready writes nothing, and its messages go to no AI model;
- for the conversations that got one, the time a reply sent until 2026-11-10 told the person that the replies are automated. Replies no longer carry this notice, and these times are deleted 30 days after they were written;
- for Instagram keyword comments: the comment ID, whether the private reply was sent, and Instagram's response;
- a list of the last 5,000 message and comment IDs, so that one message is never answered twice.
In the inbox, a business also sees the person's name and username, which we fetch live from Instagram and do not store.
3.6a Leads, follow-ups, the booking link and script tests
For each person who messages or comments on a connected Instagram account, sends a Messenger message to a connected Facebook Page, answers a lead ad of that Page, or writes in the chat on the business's website, Studio keeps a lead record for the business:
- the person's Instagram-scoped or Page-scoped ID, and their username when Instagram gives it; for a lead ad, the lead's ID instead, and as the record's name the name the person gave in the form, or their email address or phone number when the form has no name; for the website chat, the random visitor ID (section 3.6d);
- where the conversation stands (a stage such as Replied or Booked, which the business can move);
- whether it started with a message, a comment, a lead ad or the website chat, and the comment word that started it;
- which of the business's two scripts answers them, when the business runs a script test (each new person is given one at random and keeps it);
- the times of their first and last message and of the agent's last message, how long the first reply took, and how many messages each side sent;
- when they reached Booked;
- a history of these events: stage changes, the booking link opened, each follow-up sent or failed with Meta's error, for a lead ad the IDs of the form and the ad it came from, and for the website chat whether the visitor asked for a person.
A lead record holds no message text.
Lead ads. When someone submits a lead ad of a connected Facebook Page, Meta tells our server the lead's ID and the IDs of the Page, the form and the ad, with no answers. We keep these IDs in a queue. Our server then reads the person's answers from Facebook with the Page access token, up to 30 questions and up to 300 characters per answer, for example their name, email address and phone number. Studio stores the answers with the lead record and shows them to the business on its Leads board. The answers are never sent to an AI model, and the agent sends the person no message. The queue entry holds no answers. It is deleted 30 days after the lead record is made or after the last try to read the answers fails, and at once when the Page's data is deleted. While no agent of the business holds the Page, the entry waits in the queue, for 30 days at most after Meta told us about the lead, and is then deleted.
Follow-ups. When a business switches them on, the agent sends the follow-ups that business set (up to five: a message, a GIF, a voice note or a heart on the person's last message) to a person who has not answered, on Instagram or Messenger. They go only within 24 hours of that person's last message, never to someone in Booked or Closed, and none after the person writes again. A person who only answered a lead ad, or wrote only in the website chat, gets none. For each one we record the step, its status, the number of tries and Meta's response.
The booking link. When a business adds a booking link, the agent gives each person a link of their own on app.kamalov.systems. The link carries the person's Instagram-scoped or Page-scoped ID, or for the website chat their random visitor ID, with a signature. The AI models never see it: they see a placeholder, and our server puts the person's own link into the reply after the model has written it. The conversation history we keep for the agent holds the placeholder, not the link. When it is opened we record the time and move the lead to Booking, then send the browser on to the business's booking page without a referrer. That link sets no cookie and records nothing more than our normal server logs (section 3.7). The booking page belongs to the business or its booking provider, under their own privacy terms.
Numbers and exports. Studio counts these records to show the business its results: how many people reached each stage, reply rate, response time, and results per comment word and per script. A business can download its leads as a CSV file. For a lead ad, the file holds the name, email address or phone number shown as the record's name, not the other answers. That copy is then the business's own responsibility.
3.6b Posts and Insights
Posts. When you write a post in Studio for an Instagram account or a Facebook Page, we store, for the business: the post's type (picture, carousel or reel; on a Facebook Page a reel is posted as a video, and a post can also be text alone), its caption, the picture description if you give one, its pictures or video, its status (draft, approved, published or failed), the time you approved it and the time it is to go out, and, once Instagram or Facebook has published it, its ID for the post and its public link. The files are stored on our server under a long random name and are reachable by anyone who has that name, which is how Instagram's or Facebook's servers download them to publish the post. We delete the files when the post is published, when you delete the draft, and seven days after the last change to a draft, a cancelled post or a failed post. A post waiting because the account has not allowed posting keeps its files for 30 days. A post goes to Instagram or Facebook only after you press Approve, and only at the time you chose. Pictures and captions can show people, who then are part of the content you publish; you must have their permission (Terms section 8).
Drafting a caption. If you use "Draft a caption", the topic you type (up to 300 characters) and the agent's brief and facts (up to 1,500 and 2,500 characters) go to OpenAI (or Mistral AI when OpenAI does not answer), which returns a caption for you to read, change and approve. It receives no picture, no Instagram or Facebook ID, username, email address or IP address (section 5).
Insights. When you open Insights, our server asks Meta for the totals of the period you picked and the numbers of your twelve most recent posts. For an Instagram account: accounts reached, views, likes, comments, saves and shares. For a Facebook Page: views of its content, people reached, post engagements, views of the Page, clicks on its contact and action buttons, and followers, and for each post its views, reach, clicks, reactions and comments. The answer also holds the first 90 characters of each post's caption and its link. Studio stores the answer in its database, so that a reload within ten minutes does not ask Meta again. The daily clean-up deletes it once it is more than 24 hours old, and it goes at once when the agent or the account is deleted, or when the Instagram account's or Page's data is deleted (section 15). The reply service keeps no copy of it in its memory.
3.6c Comments on a Facebook Page
When you open Comments for a connected Facebook Page, our server reads from Facebook the comments on the Page's eight most recent posts, up to 25 per post: each comment's ID, its text (up to 500 characters), the commenter's name when Facebook gives it, the time, whether it is hidden, and the first 60 characters of the post's text. Facebook also sends the commenter's Facebook ID. We use it only to tell the Page's own replies apart, and we do not store it. Studio stores this list as it stores the Insights answer (section 3.6b): a reload within ten minutes does not ask Facebook again, the daily clean-up deletes it once it is more than 24 hours old, and it goes at once when the agent or the account is deleted.
The agent never answers, hides or deletes a comment by itself. When you press Hide, Show, Reply or Delete on a comment, Studio records one request: the comment's ID, the action, your reply text if you wrote one, which Studio user pressed it, when, Facebook's answer, and the ID of the reply Facebook made. Our server carries out each request once, with the Page access token. A deleted comment cannot be brought back. These records are deleted 30 days after the request was carried out or failed, and at once when the agent or the account is deleted.
3.6d The chat on a business's website
A business can put Studio's chat on its own website with one line of code that loads the chat from our server. While the business has the chat on and its agent is live, a chat bubble shows on its pages, and the agent answers from the same brief and facts as on Instagram. When the chat is off or the agent is not live, the chat answers nothing, and within minutes the code stops showing the bubble and storing anything.
- A random visitor ID. When a page with the code loads, the chat makes a random ID of 32 characters and stores it in the visitor's browser, in the local storage of the business's website, under the name kairo_v. It does this as soon as the page loads, even if the visitor never opens the chat. It has no expiry: it stays until the visitor clears that website's data. It holds nothing but the random ID. Studio uses it to keep one visitor's conversation together, to limit how many messages one visitor can send, and as the ID of the visitor's lead record and booking link. The chat sets no cookie. The business decides when its pages load the chat, and where its law requires consent for this, the business asks for it (Terms section 7).
- What we store. For each message: the visitor ID, the text (up to 500 characters), the agent's reply, whether it was answered, and the times. The chat has no field for a name, email address or phone number, but a visitor can write them in a message. When a visitor asks for a person, the agent asks for an email address or a phone number so the business can reach them, and promises no answer in the chat; what the visitor writes is stored like any other message.
- Coming back. When the visitor opens the chat again in the same browser, it shows their last 20 messages with that business and the replies. Anyone who uses that browser can see them there, so on a shared device a visitor should clear the website's data.
- The business sees each conversation in Studio, under the last four characters of the visitor ID, with its messages, replies and times, and whether the visitor asked for a person. Studio has no way for the business to answer a visitor in the chat by hand.
- The lead record. A visitor's first message makes a lead record for the business (section 3.6a), with the website chat as its source. A website visitor gets no follow-ups.
- The AI. Each message goes to the AI as section 5 says. The open chat shows the line "Automated reply by AI" at the top, in the visitor's browser language when we have that language.
- Technical data. Each page that loads the code, and each message, is a request from the visitor's browser to our server, through Cloudflare (or straight to our server on an agency's own address, section 3.1b). Our web server and Cloudflare log these requests like any other (section 3.7). We use the IP address to limit how many messages one address can send, in memory only (section 3.7).
- How long. Messages and replies are deleted 30 days after they were written, and at once when the business deletes the agent or its account (section 9).
3.7 Technical data and cookies
- IP address. We use IP addresses for rate limits, for example at most 10 sign-in tries in 10 minutes, and to limit how many messages one address can send to a website chat. For this we hold the IP address, and an email address typed into the sign-in or password reset form or into an agency's invitation, in memory only, never on disk. An entry counts toward a limit for at most one hour. Studio's sign-in pages forget it within a minute after that. The website chat and the agency pages forget it at their next request after that, or when the service restarts, so without another request it can stay in memory longer.
- Logs. Our web server and Cloudflare log requests: IP address, time, page and browser details. This includes the requests that a website's visitors make to its chat. Requests to an agency's own address reach our web server without Cloudflare (section 3.1b). Our reply service writes a short line per message to the server's system log: the business's Instagram username or Facebook Page name, the first 40 characters of the message and the first 60 characters of the reply. Its lines about follow-ups name the person only by a short code that our server makes from their ID with a secret key and that does not show the ID, and its lines about lead ads name the lead's ID. The website chat writes no message text to the logs.
- Cookies. We use the cookies below. All of them are needed to make the Service work. None is used for analytics or advertising.
- ks_studio keeps you signed in to Studio, on app.kamalov.systems or on an agency's own address, for 14 days.
- kgoauth is a one-time code that protects the Sign in with Google step, for 10 minutes.
- kgnew holds the email address and name Google sent until you finish signing up, for 15 minutes at most.
- kfresh shows that you have just confirmed with Google that the account is yours, so that you can delete it, for 10 minutes.
- ks_oauth is a one-time code that protects the Instagram connection step, for 10 minutes.
- ks_fb is a one-time code that protects the Facebook connection step, for 10 minutes.
- ks_fbp links your browser to the list of Pages you choose from, for 10 minutes.
- igop keeps you signed in to the inbox, for 12 hours.
Studio's preview of the website chat also stores a random kairo_v ID in your browser's local storage. The preview never sends it to us, and it stays until you clear the site's data.
3.8 When you write to us
If you email us, we keep your message and our reply.
4. Who receives data
We share personal data only with the people and companies below, and only as the Service needs.
- Contabo GmbH, Munich, Germany, hosts our server. The server is in France. The data in section 3 that we store is stored there.
- OpenAI (OpenAI OpCo, LLC), San Francisco, United States, provides the main AI models, through api.openai.com. Section 5 says exactly what it receives.
- Mistral AI, Paris, France, provides the fallback AI models, through api.mistral.ai, used only when OpenAI does not answer, and never for Instagram or Facebook messages, comments or other data from Meta. Section 5 says exactly what it receives.
- Cloudflare, Inc., United States, carries the traffic to app.kamalov.systems, including the website chat and the Instagram and Facebook events Meta sends us, and protects it from attacks. It processes IP addresses and request data to do this. Traffic to an agency's own address does not pass through Cloudflare (section 3.1b).
- Resend sends Studio's emails through api.resend.com, from [email protected]: the password reset links (section 3.1) and agencies' invitations (section 3.1a). It receives the recipient's email address and the email's text, which can name the business and the agency.
- Let's Encrypt, run by the Internet Security Research Group, issues the certificate for an agency's own address. It receives that address and publishes it in public Certificate Transparency logs (section 3.1b).
- Meta Platforms (Instagram and Facebook). As a business's settings direct, we send replies, private replies, comments and the posts it approves to Instagram through graph.instagram.com, and Messenger replies, follow-ups, the posts it approves and the comment actions it presses to Facebook through graph.facebook.com. We read the numbers of its account or Page, the comments on its Page and the answers to its lead ads, and we receive its events. To publish a post, Instagram's or Facebook's servers download its pictures or video from a public address on our server (section 3.6b). Login takes place on www.instagram.com and api.instagram.com, or on www.facebook.com. Meta handles this data as its own controller, under its own policy.
- Google (Sign in with Google). If you choose Continue with Google, you sign in on accounts.google.com and Google sends our server your email address and name, as section 3.1 says. Google handles your Google account under its own policy.
- Google (Google Fonts). Studio serves its typefaces from our own server. The inbox, the Instagram and Facebook connection pages and the data deletion pages load theirs from fonts.googleapis.com and fonts.gstatic.com, so Google receives the IP address and browser details of the people who open those pages. People who only message a business on Instagram or Facebook, or answer its lead ad, never load them.
- Your agency. If your business is one of an agency's clients, the agency's logins can see and change your business's data in Studio and act on it, including the messages, leads and website chats of the people who wrote to you, as section 3.1a says.
- Our developer, Albert Kamalov, in the United Arab Emirates, builds and runs the Service for us under a written contract, and can access the server to keep it running, secure and fixed.
- The websites you name receive a request from our server (section 3.3).
- Our email provider holds the emails you send to [email protected].
- Authorities and courts, when the law requires it (section 12).
- A successor, if the Service is sold or merged, under this policy.
We do not sell personal data. We do not share it for cross-context behavioral or targeted advertising, and there is no advertising in the Service.
5. How the AI uses data
The Service uses AI models from OpenAI. gpt-6-luna writes briefs, facts and replies, checks whether the facts answer a message, and checks each reply against the facts. When OpenAI does not answer, Mistral AI's models (mistral-small-latest, mistral-large-latest) do the same work, except for Instagram and Messenger messages and comments, which go to OpenAI alone. When OpenAI does not answer one of those, our server keeps the message and asks OpenAI again later, waiting longer each time (from one minute up to ten). A reply that could no longer be sent within 24 hours of the person's message is not written at all.
What OpenAI, and Mistral AI when it takes over, receive:
- when Studio drafts an agent: the business type, the owner's sample text (up to 3,000 characters) and the website text (up to 6,000 characters);
- when you import facts: the text of the page (up to 6,000 characters) or of the file (up to 12,000 characters);
- when you ask for a caption draft: the topic you typed (up to 300 characters) and the agent's brief and facts (up to 1,500 and 2,500 characters);
- for each reply, draft or test answer: the agent's brief and facts (with a placeholder where a person's own booking link would go, never the link itself), its tone setting, up to the last 10 messages of the conversation (up to 500 characters each) and the new message;
- for the two checks: the facts and the brief, the new message with up to the last 4 messages before it (up to 300 characters each), and the draft reply.
It never receives usernames, email addresses or IP addresses. It receives no Instagram, Facebook or website visitor ID either: where the agent gives a person their own booking link, the model sees only a placeholder, in the facts, in the conversation history and in a message that quotes the link, and our server puts the person's link into the reply after the model has written it. It never receives lead ad answers, the comments on a Facebook Page, or account and Page numbers. Messages, and the pages and files a business imports, can still contain personal data that people wrote in them, such as a name or a phone number.
OpenAI keeps what we send for up to 30 days to monitor abuse, unless the law requires longer, and then deletes it. It processes it in the United States, under OpenAI's Data Processing Addendum, which uses the EU Standard Contractual Clauses (and the UK Addendum) for transfers. Mistral AI's policy lets it keep what we send for up to 30 days to monitor abuse, and then delete it.
Model training. OpenAI does not use what we send through its API to train its models. For the fallback we use Mistral AI's free plan. On that plan Mistral AI may use the text we send and the replies it returns to improve its models (Mistral AI help article 347617). For that reason Mistral AI never receives Instagram or Facebook messages, comments or other data from Meta. What it can receive is a message in the website chat or a test chat with the business's brief and facts and earlier messages of the same conversation, a caption request, or the text a business gives to draft its agent or imports as facts, without usernames, email addresses or IP addresses, and without Instagram, Facebook or website visitor IDs. If we move to a plan or setting that excludes training, we will update this section.
No decisions about people. The agent answers questions. It does not make decisions that have legal or similarly significant effects on anyone. The business reviews its agent in test chats and decides when it goes live. The agent never claims to be a person. When someone asks whether they are talking to a bot, it says that it is automated. The website chat also shows the line "Automated reply by AI" at the top of the open chat.
6. How we use data
- to run the Service: accounts, agencies and their clients, invitation and password emails, an agency's own address, agents, test chats, imported facts, the Instagram and Facebook connections, the website chat, receiving messages, writing and sending replies, the inbox, lead records and lead ad answers, the follow-ups and booking link a business sets, posts, numbers, the comment actions a business presses, and its results;
- to keep it safe and working: rate limits, logs, preventing abuse and fixing errors;
- to write to business users about the Service, its security and changes to our terms;
- to meet legal duties and to enforce our Terms.
We use the messages, comments, website chat messages and lead ad answers of people who write to a business only to provide the Service to that business. We do not use them for our own purposes, to build profiles or for advertising.
7. Legal bases (EEA, UK and Switzerland)
For the data we control:
- Contract (Article 6(1)(b) GDPR): to give you the Service you signed up for, including your account, agents, test chats and Instagram and Facebook connections, an agency's tools, and the invitation and password emails.
- Legitimate interests (Article 6(1)(f) GDPR): security, rate limits and logs, preventing abuse, writing to business users about the Service, improving Studio, and defending legal claims. You can object (section 14).
- Legal obligation (Article 6(1)(c) GDPR): the records and disclosures the law requires.
We do not rely on consent. Our cookies are strictly necessary, so they need none.
For messages, comments, website chat messages and lead ad answers sent to a business, the business is the controller and chooses the legal basis. We process them on its instructions, as Article 28 GDPR requires. On its own website, the business also decides whether the chat's visitor ID needs its visitors' consent, and asks for it where it does (section 3.6d).
8. International transfers
Our server is in France. Some recipients, and the people who run the Service, are elsewhere: Fittcoaching LLC is in the United States, OpenAI processes the AI requests in the United States, Cloudflare is in the United States and runs a global network, our developer is in the United Arab Emirates, and Resend, which sends our emails, and Let's Encrypt, which issues the certificates for agencies' own addresses, can process what they receive outside the EEA. When personal data from the EEA, the UK or Switzerland goes to a country without an adequacy decision, we use the European Commission's standard contractual clauses, with the UK Addendum and the changes Switzerland requires, or another safeguard the law allows. For the businesses we serve, these clauses are part of our Data Processing Addendum. You can ask us for a copy.
9. How long we keep data (retention)
| Data | How long we keep it |
|---|---|
| Studio account | While the account exists. If you delete it on the Account page, at once. If you ask us to close it, 30 days so you can ask for an export, then deleted. |
| Agents, briefs, facts, keywords, private-reply text, test chats, website chat settings | Until you delete the agent or close the account, then as above. |
| Sources and proposals of imported facts (page address or file name, a fingerprint of the text, times, the facts found and your choice) | Until you delete the agent or close the account, then as above. We never store the imported file or its text. |
| Website chat messages and replies | 30 days from when they were written. Deleted at once with the agent or the account. |
| The website chat's visitor ID in a visitor's browser | No expiry. It stays until the visitor clears the website's data. |
| An agency's name, referral code, brand name, logo and currency | Until the agency's account is deleted. |
| The monthly price an agency records for a client | Until that client's record is deleted. |
| An invitation that nobody answered | The login and its invitation record are deleted 8 days after the invitation was made. The record of an answered invitation stays with the login. |
| An agency's own address | Until the agency removes it or its account is deleted. Then our server stops serving it and deletes its certificate. The record of the address, the agency that claimed it and when stays after that, to stop someone else from taking the address over. |
| Emails sent through Resend | As Resend's terms provide. |
| Instagram connection and access token | While the account stays connected. Deleted when you remove our app in Instagram's settings, when you ask us, or when your Studio account is deleted. |
| Facebook Page connection and Page access token | While the Page stays connected. Deleted when you remove our app in Facebook's settings, when you ask us, or when your Studio account is deleted. |
| The list of your Pages while you choose one | Deleted when you choose. If you do not, it expires after 10 minutes and is deleted within a minute after that. |
| Instagram and Messenger messages, Instagram comments, conversation history, sent replies, drafts, messages sent from the inbox, times of past automated-reply notices | 30 days from when they were received, sent or written. |
| Keyword comment records | 30 days. |
| Pictures and videos of posts | Deleted when the post is published or the draft is deleted; seven days after the last change to a draft, a cancelled post or a failed post; 30 days for a post waiting for the account to allow posting. |
| Post records (type, caption, status, times, Instagram's or Facebook's post ID and link) | Until you delete the agent or close the account, then as above. Also deleted when the account's or Page's data is deleted (section 15). |
| Insights numbers and a Page's comment list | The last answer, until the daily clean-up after it is 24 hours old. Deleted at once with the agent or the account, or when the Instagram account's or Page's data is deleted (section 15). |
| Replies you type yourself in Studio (Reply yourself), with their status | 30 days after they were written. Deleted at once with the person's data, the agent or the account. |
| Comment actions on a Facebook Page, with your reply text | 30 days after the action was carried out or failed. Deleted at once with the agent or the account, or when the Page's data is deleted (section 15). |
| Lead records, their history, lead ad answers and follow-up records | 12 months after the person's last message or the last change to the record, then deleted. Sooner when the business deletes the agent or its account, or when the person asks. |
| Lead ad queue entries (IDs only) | 30 days after the lead record is made or the last try to read the answers fails. Deleted at once when the Page's data is deleted. An entry for a Page that no agent holds waits until one does, for 30 days at most. |
| Follow-up settings, booking link, comment words and their messages, script B | Until you change them or delete the agent, then as for agents. |
| List of answered message IDs | Only the last 5,000 IDs. Older ones roll off. |
| Our web server and system logs | 30 days. |
| Logs at Cloudflare | As Cloudflare's data processing terms provide. |
| Rate-limit counters, with IP addresses and typed email addresses | In memory only, while they count toward a limit (at most 1 hour). The website chat and the agency pages forget them at their next request after that, or when the service restarts (section 3.7). |
| Backups | Full copies of the server, made to recover from a failure, are kept offline for up to 12 months and then deleted. Data deleted from the live systems leaves the backups when they are deleted. We never restore a deleted account from a backup. |
| Data sent to OpenAI | Up to 30 days, under OpenAI's terms. |
| Data sent to Mistral AI | Up to 30 days, under Mistral AI's terms. |
| Emails with us | Up to 3 years after the conversation ends, or sooner if you ask and we no longer need them. |
We keep data longer only where the law requires it or for an active legal claim, and then only the data needed.
10. Security
- Every connection uses HTTPS.
- Passwords are stored only as salted scrypt hashes.
- Instagram access tokens and Facebook Page access tokens are encrypted at rest, with a key that only the server can read. We do not store the Facebook user access token.
- Sign-in cookies are signed, HttpOnly and Secure, and forms are protected against cross-site requests and double submission.
- Instagram and Facebook events, and Meta's removal and deletion requests, are accepted only with Meta's valid signature.
- Sign-in, sign-up and AI use are rate limited, and the website fetch refuses private network addresses.
- The website chat answers only while the business has it on and its agent is live. When the business sets its own site, browsers on other websites are refused. Messages over 500 characters are refused, and the number of messages per address, per visitor and per agent is limited.
- Password reset and invitation links are signed, work once, and expire after one hour and 7 days.
- An agency's logins reach only its own clients, a client's logins reach only their own business, an agency's logo is shown only to its logins and its clients' logins, and an agency's own address lets in only those logins.
- Only the people who run the Service can access the server, and they are bound to keep the data confidential.
No system is perfectly secure. If you find a security problem, email [email protected].
11. Data breaches
If a breach of security puts personal data at risk, we act at once to contain it. We tell the businesses whose data is affected without undue delay, and within 72 hours of learning of it, so they can meet their own duties. For the data we control, we notify the data protection authority within 72 hours where the GDPR or the UK GDPR requires it, and we tell the people affected without undue delay where the law requires it, for example within 30 days under Washington law.
12. Law enforcement requests
We disclose personal data to an authority only when the law requires it, for example under a valid court order or subpoena. We check each request, disclose only what is strictly required, and challenge requests that go too far. Where the data comes from a business's conversations, we tell that business first, unless the law forbids it, and refer the authority to the business where we can.
13. Children
The Service is for businesses, and Studio accounts are for adults 18 and over. Instagram and Facebook require their users to be at least 13. The agent is not meant for children, and we do not knowingly collect children's data for our own purposes. If a child messages a business, the message is handled like any other and deleted after 30 days. If you think we hold a child's data that we should not, email [email protected] and we will delete it.
14. Your rights
Depending on where you live, you can ask us to:
- tell you what data we hold about you, and give you a copy;
- correct it;
- delete it;
- limit or object to how we use it;
- send it to you or to another service in a machine-readable format.
To ask, email [email protected].
- Business users: write from your account email, so we can confirm it is you. You can also download your data yourself on Studio's Account page, with Download my data: one file with your login (without the password), your business, its agents with their test chats, leads, posts, website chats and imported facts, and the data of its Instagram accounts. An agency's file holds the agency's record and its list of clients. The data of each client is in that client's own file, and we send it on request.
- People who messaged a business: tell us the business's Instagram username or Facebook Page name and roughly when you wrote, or the email address or phone number you gave in its lead ad, so we can find your data. If you wrote in the chat on a business's website, tell us the website and roughly when you wrote and what, or the kairo_v visitor ID stored in your browser for that website. The business decides as the controller, and we help it answer.
We answer within one month, or within 45 days where a US state law gives that time. If we need longer, we tell you why, as the law allows.
If we decline your request, you can appeal by replying with the subject "Appeal". We answer an appeal within 45 days.
You can also complain to a data protection authority: in the EEA, the authority where you live or work; in the UK, the Information Commissioner's Office; in Switzerland, the Federal Data Protection and Information Commissioner. In the United States you can contact your state attorney general.
15. How to delete your data
- Business users: for a business, Delete the account on Studio's Account page deletes the account at once: its agents with their facts, tests, leads, posts, website chats and imported facts, its logins, and its Instagram and Facebook Page connections with the messages kept for them. When your business or agency has other logins, the page offers Delete my login instead, which deletes only your login. The page says which one it does before you confirm. You can also email [email protected] from your account email and ask us to close your account. We then delete it as section 9 says.
- Agencies: when an agency deletes its account, its logins, its brand and logo are deleted, and its own address stops. Each client that has its own login keeps its account and its data, and continues with us directly.
- Disconnecting Instagram: in Studio, Disconnect stops the agent at once. To end the connection completely, remove our app from your Instagram account in Instagram's settings. Meta then tells us, and we delete the access token and the messages, comments and replies of that account within 30 days. You can also ask us by email. Our page at https://app.kamalov.systems/data-deletion says the same.
- Disconnecting a Facebook Page: in Studio, Disconnect stops the agent at once. To end the connection completely, remove our app from your Facebook account in Facebook's settings. Meta then tells us, and for every Page you connected we delete its Page access token, its Messenger messages, replies and drafts, its posts and their files, and its lead ad queue. This happens at once, and a deletion that fails is tried again every day. Its Insights answer, its comment list and its comment-action records go at the same time. Lead records, with any lead ad answers, stay until the agent or the account is deleted, the person asks, or 12 months pass (section 9). If you also ask Facebook to delete your data, we do the same, and Facebook shows you a confirmation code and a link to a page on app.kamalov.systems about your request. That page says whether the data of every Page you connected is deleted, and if you had connected no Page, that there was nothing to delete. You can also ask us by email.
- People who messaged a business or answered its lead ad: your messages are deleted automatically after 30 days, and the lead record about you, with any lead ad answers, 12 months after the last activity on it. To have them deleted sooner, ask the business, or email us with the business's Instagram username or Facebook Page name and roughly when you wrote, or the email address or phone number you gave in its lead ad.
- People who wrote in the chat on a business's website: your messages are deleted automatically after 30 days, and the lead record about you 12 months after the last activity on it. You delete the visitor ID yourself by clearing that website's data in your browser. To have the rest deleted sooner, ask the business, or email us as section 14 says.
16. Notices for US states
California
This notice is for California residents, under the California Consumer Privacy Act as amended (CCPA).
- What we collect (in the last 12 months): identifiers (email address, IP address, Instagram user ID and username, Facebook app-scoped user ID, Facebook Page ID and name, Instagram-scoped and Page-scoped IDs, website chat visitor IDs, account identifiers); professional information (business name, a business's facts and brief, an agency's name, brand, logo and the prices it records for its clients); internet activity (logs, and sign-in to and use of Studio); and the content of messages, comments and website chat messages sent to businesses that use the Service, and the answers people give in their lead ads (such as a name, email address or phone number), which we handle as each business's service provider.
- Sensitive personal information: the email address and password that sign you in to Studio. We use them only to sign you in and keep your account secure, which the CCPA allows without a right to limit.
- Sources: you, your agency (including the email address it types to invite you), Instagram and Facebook (Meta), Google when you sign in with it, the websites you name and the files you import, and the visitors of a business's website who write in its chat.
- Purposes: as section 6 describes.
- Disclosures for a business purpose: to the service providers and contractors in section 4 (Contabo, OpenAI, Mistral AI, Cloudflare, Resend and our developer), to Meta and Google as section 4 describes, to Let's Encrypt for an agency's own address, and to the agency whose client your business is.
- No sale or sharing. We do not sell personal information or share it for cross-context behavioral advertising, and we have not done so in the past 12 months. We have no actual knowledge of selling or sharing the personal information of anyone under 16.
- Retention: section 9.
- Your rights: to know and access, delete and correct your personal information; to opt out of sale or sharing (we do neither); to limit the use of sensitive personal information (we use it only as the law allows); and not to be treated differently for using these rights. An authorized agent can make a request for you with your signed permission. We verify your identity first.
For messages, comments, website chat messages and lead ad answers sent to a business, that business is the CCPA business and we are its service provider.
Washington
Washington's My Health My Data Act protects consumer health data. We do not collect it for our own purposes. If a business uses the Service to answer messages, website chat messages included, or to collect lead ad answers that contain it, for example a clinic, we process it only as that business's processor, under the binding contract in our Data Processing Addendum, and the business's own consumer health data privacy policy applies.
Other states
Residents of other US states with privacy laws have similar rights, which they can use as section 14 describes. We do not sell personal data, use it for targeted advertising, or use it for profiling that has legal or similarly significant effects.
17. Changes to this policy
We publish every change here with a new Effective date. If a change matters, we tell business users by email or in Studio before it takes effect. This policy is at https://app.kamalov.systems/studio/legal/privacy.
18. Contact
Fittcoaching LLC 7654 19th St W, Tacoma, WA 98466-3615, United States Email: [email protected]