Contents
- Who we are and what this policy covers
- Our role: controller and processor
- Information we collect
- How we use information
- AI features
- How we share information
- International transfers
- How long we keep information
- Facebook, Instagram, Messenger and WhatsApp (Meta)
- Connecting Google Tag Manager
- Cookies and browser storage
- How we protect information
- Your rights and choices
- Deleting your data
- Children
- Changes to this policy
- Contact us
Appendices: A. Meta permissions · B. Service providers · C. Retention schedule
At a glance
- Two kinds of data. Data about you as a visitor or account holder, which we decide how to use; and data a business (a "Merchant") keeps about its own customers inside the Platform, which the Merchant decides how to use and we handle on its behalf.
- Facebook, Instagram, Messenger and WhatsApp. Merchants connect these so every conversation arrives in one inbox. We use data from Meta only to provide the features the Merchant uses (Section 9).
- AI. If a Merchant switches AI on, customer messages are sent to Google's Gemini service to draft or send replies. Google does not train on this data. We never use WhatsApp, Messenger or Instagram message content to train or improve AI models (Section 5).
- We do not sell personal data and we do not use it for advertising.
- Deleting your data. Anyone, including people who messaged a Merchant, can ask us to delete their data (Section 14).
1. Who we are and what this policy covers
ottomi.ai ("we", "us", "our") provides business software for small and medium businesses: inventory, sales, purchasing, accounting, point of sale, online stores and customer messaging.
This policy explains what personal data we collect, why, how we use, share, protect and delete it, and the choices you have. It applies to:
- our Website;
- the Platform: the merchant dashboard, our API, the online stores Merchants build on it (at an address we provide or a Merchant's own domain), the live chat on those stores, and the tools that let Merchants connect Facebook, Instagram, Messenger, WhatsApp and Google Tag Manager; and
- our communications with you by email, SMS, WhatsApp, phone or support channels.
Together these are the "Services". Use of the Services is also governed by our Terms and Conditions.
| Term | Meaning |
|---|---|
| Merchant | A business or individual that uses the Platform to run its business. |
| Team member | A person a Merchant invites to its workspace. |
| End Customer | Anyone who visits, shops at, messages or comments on a Merchant's store or channels. |
| Merchant Data | Data that a Merchant, its Team members or its End Customers put into, or generate in, the Platform for that Merchant's business. |
| Meta | Meta Platforms, Inc. and its affiliates, including Facebook, Instagram, Messenger and WhatsApp. |
| Channel | A connected Facebook Page (Messenger), Instagram professional account, WhatsApp Business number, or a store's web chat. |
2. Our role: controller and processor
| Data | Our role |
|---|---|
| Website visitors; Merchant and Team-member accounts; billing; security logs; our own communications | Controller — we decide how it is used |
| Merchant Data: customers, orders, addresses, conversations, supplier and employee records, files | Processor — we handle it on the Merchant's instructions |
| Data received from Meta or Google because a Merchant connected an account | Controller for the connection itself (account IDs, tokens, permissions); processor for the conversations and customer data that flow through it |
If you are an End Customer, the Merchant you dealt with is responsible for how your data is used in its business and should give you its own privacy notice. You can contact the Merchant or us to exercise your rights; if the Merchant cannot be reached or has closed its account, we will act on your request ourselves (Section 14).
Each Merchant's data is kept separately. It is held in its own database schema and is never combined with another Merchant's data. We do not build profiles of a person across different Merchants.
3. Information we collect
3.1 Website visitors
- What you tell us when you contact us: name, email, phone number, company and your message.
- Technical data: IP address, browser and device details, pages requested, referring page and time.
- Fonts: pages load typefaces from Google Fonts, so Google receives your IP address and browser details.
3.2 Merchants and Team members
- Identity and contact: name, mobile number (your login, verified with a one-time passcode), email, date of birth (used only to confirm account holders are adults), preferred language.
- Credentials: password and one-time passcodes, stored only as hashes; session tokens.
- Business profile: business name, industry, size, store address and domain, and the company details and logo you add.
- Team members: name, mobile number, email, optional photo, role and permissions.
- Tier and billing: your pricing tier, usage in each billing month, invoices and payments received. We do not collect payment card numbers.
- Support: what you send us and our notes.
- Activity records: what was created, changed or deleted in your workspace, by whom, when, and from which IP address and device.
- Sign-in index: a platform-level index linking Merchant users' email addresses and mobile numbers to their stores, and for owners of several stores, organisation records and daily totals (counts and sales totals, not customer details).
- Connections: account IDs, tokens and settings for Meta, Google, couriers, payment providers and advertising pixels.
3.3 Merchant Data
What a Merchant and its Team put into the Platform, and what its End Customers send through its channels. For example: customer names, numbers, emails, delivery addresses, labels the Merchant applies and order history; orders, deliveries, returns and refunds; suppliers and purchases; payments, expenses and ledgers; owner and employee records; products, store pages and policies; files, images and voice notes; conversations, comments, saved replies and templates; and courier, payment and pixel credentials (stored encrypted).
3.4 Shoppers on a Merchant's online store
- Account (optional): mobile number (sign-in by one-time passcode), name and email. You can also check out as a guest.
- Basket and wishlist: kept on your device and, if you are signed in, saved to the store so the Merchant can see them, including abandoned baskets.
- Orders: name, mobile number, optional email, delivery address, notes, items, coupon and payment method.
- Reviews: display name, rating and text, shown publicly on the store.
- Live chat: your messages, attached photos and any name you give.
- Usage data: IP address and browser details with the records you create; a random visitor identifier stored in your browser; and simple browsing events (page views, product views, add-to-basket, with product, quantity, value, page and time), linked to your account if you are signed in, to show the Merchant how its store performs.
- Tracking tools the Merchant switches on: a Merchant may add Meta Pixel, Google Tag Manager or TikTok Pixel, or switch on Meta's Conversions API. Those providers may then collect data about your visit, and the Merchant is responsible for telling you. With the Conversions API, our servers send Meta the store's events using the Merchant's own pixel and token; contact details are hashed (SHA-256) before sending, and only IP address, browser details and Meta's browser identifiers are sent unhashed.
3.5 People who contact a Merchant on Facebook, Instagram, Messenger or WhatsApp
When you message a Merchant's Page, Instagram account or WhatsApp number, or comment on its posts, we receive and store that for the Merchant:
- Identifiers: a Page-scoped or Instagram-scoped ID; for WhatsApp, your phone number and WhatsApp ID.
- Profile details: your name and profile picture (we keep a copy so it keeps displaying) and, for Instagram, your username. Meta's profile response can also include your language setting and gender and, for Instagram, your follower count and whether you follow the business; we do not store or use those details.
- Messages and attachments: text, photos, videos, voice notes, documents, stickers, reactions, locations or contacts you choose to share, button replies, timestamps, and delivery and read status.
- Comments and mentions on the Merchant's posts, and the Merchant's replies.
- Preferences: whether you have stopped marketing messages from the business on WhatsApp.
- Order details you give in chat, such as name, phone, address, items and payment screenshots.
- Conversation records: status, labels, whether AI or a person replied, and scheduled follow-ups.
- Earlier chat history: if a Merchant keeps its number on the WhatsApp Business app and connects it to the Platform, Meta may provide past chats, the Merchant's saved contact names, and messages the Merchant sends from its phone.
3.6 Information from Meta and Google
When a Merchant connects Meta or Google accounts we receive account and asset details, described in Section 9, Section 10 and Appendix A.
3.7 Collected automatically
- Device and connection: IP address, browser and operating system.
- Requests: pages and API endpoints requested, time, status and duration.
- Errors: crash reports sent to our error-monitoring provider, configured not to collect personal identifiers; browser errors from online stores are sent to our own servers with email addresses and phone numbers removed.
- Security signals: sign-in and passcode attempts and abuse indicators.
3.8 From other third parties
Couriers and payment providers a Merchant connects (parcel and payment status), Merchants who add you as a customer, supplier or Team member, and our email providers (delivery status).
3.9 Sensitive information
We do not ask for sensitive data such as health, religion, political opinions, biometrics, national ID numbers or card numbers, and the Platform is not designed to hold it. If someone sends it in a message, it is stored with the conversation. We do not use voice notes or photos to identify anyone. We never see your Facebook or Google password.
4. How we use information
| Purpose | Examples |
|---|---|
| Provide the Services | Accounts, stores, orders, inventory, the inbox, file storage and support |
| Connect channels | Receive and send messages and comments; ad reports for the Merchant; keep connections working |
| AI features | Draft or send replies, read attachments, prepare orders, follow-ups (Section 5) |
| Security | Verify identity, prevent abuse and fraud, keep audit logs |
| Communications | Passcodes, security alerts, service notices, invoices, replies to you |
| Marketing | News about our products, only where you opted in or the law allows; you can unsubscribe at any time |
| Billing and administration | Invoices, tier changes, suspension for non-payment |
| Improving the Services | Diagnosing errors and measuring performance using aggregated or de-identified information (Section 5.6) |
| Legal | Tax and accounting records, lawful requests, enforcing our Terms |
Where the law requires a legal basis, we rely on our contract with the Merchant, the Merchant's instructions, your consent, our legitimate interests in running and securing the Services, or legal obligations.
We do not:
- sell personal data, or share it for advertising;
- use Merchant Data or data from Meta or Google to build advertising profiles or to market to End Customers ourselves;
- use data from Meta or Google to decide on credit, insurance, employment or eligibility, or for surveillance;
- use WhatsApp, Messenger or Instagram message content to train or improve AI models (Section 5.6).
Our staff access Merchant Data only to provide support the Merchant asks for, to keep the Services secure, or to comply with law.
5. AI features
5.1 What they do
- AI replies. On Messenger, Instagram, WhatsApp and store web chat, the AI can draft or send replies about the Merchant's products, prices, stock, delivery and policies, using the Merchant's own data. If the Merchant allows it, it can take order details and create an order after the customer confirms.
- Attachments. The AI can read photos, voice notes and short videos a customer sends, such as a product photo or a payment screenshot, which is passed to the Merchant to verify.
- Follow-ups. If enabled, the AI can send a limited number of reminders and a review request after delivery. Automated messages are not sent once the 24-hour messaging window has closed.
- Product autofill. Drafting a product listing from the Merchant's photos and product name.
AI is off by default. A Merchant switches it on and chooses whether it may reply and create orders automatically. The AI hands the conversation to a person for complaints, refunds, payment disputes and anything it is unsure about, and a customer can always reach a person. Merchants are responsible for telling customers when they are talking to an automated assistant where the law requires it.
5.2 What is sent to the AI provider
The recent messages in the conversation; photos, voice notes and videos from the customer's last few messages; the Merchant's AI settings and policies; and, when needed, product, stock and order details and the customer details held for that conversation. We do not send the customer's Meta profile name or picture.
5.3 Who provides the AI
Google (the Gemini API), under Google's paid-service terms. Google processes this content only to provide the service to us and does not use it to improve its products or train its models. Google may keep it for a limited time for abuse monitoring, as its terms describe.
5.4 Records of AI activity
We keep a record of each AI request and response in the Merchant's workspace, so the Merchant can review what was said and we can monitor quality and safety. These records may contain End Customers' personal data (Appendix C).
5.5 Forms of address
Where a Merchant uses different polite forms for men and women (for example "bhaiya" or "apu"), the AI may choose one only when it is clear from the conversation. It is used for nothing else and is not saved to the customer's record.
5.6 How we improve our AI
We improve our AI features in these ways only:
- For each Merchant, from its own data. A Merchant's assistant may use that Merchant's own products, policies, saved replies and past conversations to answer its customers better. This stays inside that Merchant's workspace and is never used for any other Merchant.
- Store web chat, with the Merchant's permission. Where a Merchant has opted in, we may use conversations from its store's web chat, with names, phone numbers, addresses, order and payment references removed, to test and improve our AI features for all Merchants. A Merchant can withdraw this permission at any time.
- Usage measurements. We use aggregated, de-identified measurements, such as how often the AI hands a conversation to a person, how quickly it replies and how often it fails, to improve the Services. These contain no message content.
- Our own test material, written by our team or generated for testing.
We never use the content of WhatsApp, Messenger or Instagram messages to train or improve AI models, and we never let Google or any other provider use Merchant Data to train theirs.
6. How we share information
- Inside a Merchant's workspace: with the Merchant and the Team members it gives access to.
- Our service providers (Appendix B): hosting, storage, email, error monitoring, traffic protection and AI. They process data only on our instructions, for our purposes, under written terms, and must delete it when they stop working for us. We give Merchants advance notice of any new provider that will process Merchant Data.
- Meta and Google: replies to customers go through Meta's systems, and we exchange data with Meta and Google as described in Sections 9 and 10. Each handles data under its own privacy policy.
- Couriers a Merchant books (for example Pathao, Steadfast, RedX, Paperfly or Carry Bee): the recipient's name, phone number and address, the cash-on-delivery amount, item details and the order number.
- Payment providers and tracking tools the Merchant chooses (for example bKash, Nagad, SSLCommerz, Meta Pixel, Google Tag Manager, TikTok Pixel).
- Professional advisers, under confidentiality.
- Authorities, where required by law or to protect people's safety and rights. For Merchant Data we tell the Merchant first where the law allows.
- Business transfers: in a merger, acquisition or sale of assets, with this policy continuing to apply.
- With your consent, for other purposes you agree to.
We do not sell personal data.
7. International transfers
Our servers are run by our hosting provider. Some providers, including Google, Meta, Cloudflare and Sentry, process data in other countries, including the United States. We use written data-protection terms with providers and limit what we send.
8. How long we keep information
We keep personal data only as long as needed for the purposes in this policy, then delete or anonymise it. While a Merchant's account is active, the Merchant decides how long its Merchant Data is kept. Appendix C sets out the periods. We may keep data longer where the law requires or to resolve disputes, and copies remain in backups until they expire.
9. Facebook, Instagram, Messenger and WhatsApp (Meta)
This section applies when a Merchant connects Meta accounts. The Meta app that does this is named ottomi.ai. Meta's own privacy policy applies to Meta's handling of your data.
9.1 How a Merchant connects
- Facebook Pages and Instagram: through Facebook Login for Business. The Merchant approves the permissions and chooses which Page, and linked Instagram account, to connect.
- WhatsApp: through WhatsApp Embedded Signup, a Meta window where the Merchant picks a WhatsApp Business Account and number. The dashboard loads Meta's SDK only for this step.
- Ad accounts: read-only access, requested in the same Facebook login.
We request only the permissions in Appendix A.
9.2 What we receive about the Merchant
- Pages and Instagram: the Pages the Merchant manages; for the chosen Page, its ID, name, picture and access token; the linked Instagram account's ID, username and picture; posts, Instagram media and their comments; and notifications for messages, comments and similar events.
- WhatsApp: the WhatsApp Business Account ID, business phone numbers and their status, message templates, and notifications about messages, templates and numbers.
- Ad accounts: account details, campaigns, ad sets, ads and daily performance for up to 180 days, refreshed daily. This is read-only, and we never see the people who saw the ads.
9.3 What we receive about End Customers
See Section 3.5.
9.4 How we use it
Only to provide the features the Merchant uses:
- showing messages and comments in the inbox, and replying (by the Merchant's staff or, if enabled, the AI);
- sending replies, order updates, follow-ups and approved templates;
- recording and honouring opt-outs;
- linking conversations to the Merchant's own customers and orders;
- showing the Merchant its own ad performance, in aggregate, for its own campaigns only;
- keeping connections working and the Services secure.
We do not publish posts, create or edit ads, or upload customer lists to Meta.
9.5 What we do not do with Meta data
- Sell, license or share it with data brokers.
- Use it for advertising or to build advertising profiles.
- Use it for eligibility decisions or surveillance.
- Use it for our own purposes beyond providing the Merchant's features, or combine one Merchant's data with another's.
- Use message content to train or improve AI models (Section 5.6).
We use Meta data in line with the Meta Platform Terms, Developer Policies, and WhatsApp Business terms and Messaging Policy.
9.6 How we store it
Access tokens are encrypted and held in the Merchant's workspace with its conversations. To route incoming events we keep a platform-level index of Meta account IDs, and a temporary copy of each raw event notification for diagnosis. We keep a copy of contacts' profile pictures because Meta's picture links expire.
9.7 Disconnecting
- In the dashboard (Messaging → Channels → Disconnect): we stop receiving messages, unsubscribe from the Page's notifications and delete the stored access token. Past conversations stay in the workspace until deleted.
- Connecting a different account of the same type replaces the old one and deletes that channel's conversations, contacts, comments and templates.
- Removing our app in Meta's settings (Facebook → Settings & privacy → Settings → Business integrations): our access stops working. To have the data deleted too, see Section 14.
9.8 WhatsApp
We record when a person stops marketing messages from a business and do not send them marketing messages. Outside the 24-hour window, only approved templates are sent.
9.9 Human Agent (Messenger and Instagram)
When a customer's question cannot be resolved within 24 hours, for example over a weekend or while an order problem is investigated, a staff member can still send a personal reply up to 7 days after the customer's last message, using Meta's Human Agent feature. It is used only for messages a person types, never for automated or promotional messages.
10. Connecting Google Tag Manager
A Merchant can connect its Google account so we can set up Google Tag Manager tracking for its store.
- What we receive: the connected account's email address, and access to create and update tag containers and versions in that Merchant's Tag Manager account. We request only
openid,email,tagmanager.edit.containersandtagmanager.edit.containerversions. We do not access Gmail, Drive, Contacts, Calendar or other Google data. - How we use it: only to create and publish the store's tracking tags, as the Merchant asked. The token is stored encrypted.
- Limited Use. ottomi.ai's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- Disconnecting: disconnect Google in the dashboard, which revokes our access and deletes the token, or remove the app in your Google Account under Security → Third-party apps and services.
11. Cookies and browser storage
We use cookies and browser storage only to make the Services work and remember your choices. We do not use advertising or third-party analytics cookies on our Website or the dashboard, and store templates use none unless the Merchant switches on tracking.
- Essential: keeping you signed in, remembering your store, basket, wishlist and live-chat session, and the sign-in step you are on.
- Preferences: language, layout, notification sound, unsent message drafts, recently viewed products.
- Store analytics: an anonymous visitor identifier used to count visits and browsing events for the Merchant.
- Meta cookies (
_fbp,_fbc): set on a store only when the Merchant has switched on Meta tracking, kept for 90 days. - Third parties: Google Fonts on all our pages; Meta's SDK on the dashboard only while a Merchant connects WhatsApp; security cookies from our traffic-protection provider; and tools a Merchant adds to its store, which the Merchant is responsible for disclosing.
You can block or delete cookies in your browser; you may then be signed out or lose your saved basket.
12. How we protect information
- HTTPS for all connections.
- Encryption of stored access tokens and integration credentials.
- Passwords and passcodes stored only as hashes; passcodes expire after 5 minutes.
- Short-lived sign-in sessions.
- Each Merchant's data in its own database schema; files in a per-Merchant area with private, time-limited links.
- Role-based access within each workspace.
- Rate limits and verification of Meta's message signatures.
- Audit logs of workspace actions.
- Nightly database backups.
If a breach affects personal data in a way likely to cause harm, we will tell affected Merchants without undue delay and notify authorities, and Meta where its data is involved, as required.
13. Your rights and choices
Depending on where you live, you may have the right to access, correct or delete your data, get a copy, object to or restrict some uses, withdraw consent, and complain to a data-protection authority.
- Merchants and Team members: edit your profile in the dashboard, or email us.
- End Customers: contact the Merchant, or email us with the store name or the Page or number you contacted.
- Everyone: we may confirm your identity first. We aim to respond within 30 days, normally free of charge.
- Marketing: use the unsubscribe link in our emails. Reply STOP to a business on WhatsApp to stop its marketing messages.
- Connections: remove our app in your Facebook settings or Google Account at any time.
14. Deleting your data
Anyone can ask us to delete their data, including people who messaged or commented on a Merchant's Page, Instagram account or WhatsApp number. Email [email protected] with the subject "Data deletion request".
14.1 If you messaged a Merchant (End Customers)
Tell us the store name, or the Page, Instagram account or WhatsApp number you contacted, and roughly when. We will delete your messages, attachments, profile details and related AI records, tell the Merchant, and confirm by email within 30 days. You can also ask the Merchant directly. Deleting messages in your own Facebook, Instagram or WhatsApp app does not delete the Merchant's copy.
14.2 If you are a Merchant that connected Facebook, Instagram or WhatsApp
- Disconnect the channel in the dashboard (Messaging → Channels → Disconnect). This deletes the stored access token.
- Optionally remove our app in Facebook → Settings & privacy → Settings → Business integrations.
- Email us from your account email with your store name and the Page, Instagram account or WhatsApp number. We will delete the connection data, that channel's conversations, contacts, comments, templates, stored profile pictures and ad data within 30 days, and confirm by email.
14.3 If you close your Merchant account
Email us from your account email. We will provide an export of your data if you want one, and delete your Merchant Data within 30 days after closure.
14.4 What we may keep
Records the law requires (for example invoices), security records for the periods in Appendix C, and backups until they expire.
15. Children
The Services are for businesses and not directed to people under 18. Merchants and Team members must be adults. If you believe a child has given us personal data, contact us and we will delete it.
16. Changes to this policy
We will post any changes here with a new date. For material changes we will tell Merchants by email or in the dashboard before they take effect, and ask for consent where the law requires it.
17. Contact us
ottomi.ai Privacy and data deletion: [email protected]
Appendix A — Meta permissions we request and why
| Permission / feature | Used for |
|---|---|
pages_show_list |
Showing the Merchant its Pages so it can choose one to connect |
pages_manage_metadata |
Subscribing the chosen Page to message and comment notifications |
pages_read_engagement |
Reading the Page's details and posts, and finding its linked Instagram account |
pages_messaging |
Receiving and replying to Messenger messages |
pages_read_user_content |
Reading comments on the Page's posts for the comments inbox |
pages_manage_engagement |
Replying to and hiding comments on the Page's posts |
instagram_basic |
Reading the Instagram account's profile and media |
instagram_manage_messages |
Receiving and replying to Instagram direct messages |
instagram_manage_comments |
Reading, replying to and hiding comments on Instagram posts |
business_management |
Finding the Pages, WhatsApp accounts and ad accounts the Merchant manages in Meta Business Manager, so it can connect them. We never change business settings |
whatsapp_business_management |
Connecting a WhatsApp number, managing its templates and notifications |
whatsapp_business_messaging |
Receiving and sending WhatsApp messages |
ads_read |
Showing the Merchant read-only reports on its own ad campaigns |
| Business Asset User Profile Access | Showing the name and picture of people who message the Merchant |
| Human Agent | Staff replies up to 7 days after a customer's last message (Section 9.9) |
public_profile and email are granted automatically by Meta. We do not read or store them.
Appendix B — Service providers
| Provider | What it does | Data involved |
|---|---|---|
| Cloud hosting provider | Servers, database, file storage, backups | All Platform data |
| Cloudflare, Inc. | DNS and traffic protection | Request data, including IP address |
| Google LLC (Gemini API) | AI processing (Section 5) | Messages, attachments, product and order details |
| Google LLC (Google Fonts) | Typefaces | IP address, browser details |
| Functional Software, Inc. (Sentry) | Error monitoring | Diagnostics, without personal identifiers by default |
| Email delivery provider | Account and service emails | Email address, name, message content |
Meta, Google Tag Manager, couriers, payment providers and tracking tools are services the Merchant chooses to connect; they handle data under their own terms.
Appendix C — Retention schedule
| Data | How long we keep it |
|---|---|
| Merchant and Team-member accounts | While the account is open; deleted within 30 days after closure |
| Merchant Data, including conversations and files | While the account is open; deleted within 30 days after closure, or earlier when the Merchant deletes it or a person asks us to under Section 14 |
| Meta and Google access tokens | Until the channel is disconnected |
| Raw Meta event notifications | 30 days once processed; failed ones until no longer needed for diagnosis |
| AI activity records | While the account is open; deleted with the account's data |
| Activity and audit logs | While the account is open; deleted with the account's data |
| One-time passcodes | Valid 5 minutes; stored only as hashes |
| Shopper and chat sessions | Up to 30 days and 12 hours |
| Billing and tax records | As long as the law requires |
| Database backups | 14 days |
| Website enquiries and support messages | 24 months after the last contact |
| Marketing preferences | Until you unsubscribe or ask us to delete them |