Privacy policy

1. Who we are

Selleena AI provides a messaging assistant for shops that sell through direct messages, and is operated from Bangladesh. In this policy, “we” and “us” mean Selleena AI; “you” means the person using the workspace, or the person reading this page.

For the account, shop and billing information of a shop using Selleena AI, we are the data controller. For the customer conversations a shop receives through Facebook, Instagram or WhatsApp, the shop is the controller and we are a processor acting on the shop’s instructions — see section 3.

2. What we collect

We collect what the product needs to work, and nothing that reads like a wish list.

Account

Your name and email address; a password, stored only as a salted hash (we can never read it); when you signed up and last signed in.

Sign-in shortcuts

If you use Google or Facebook to sign in: the provider’s account id, the email and name on that profile, and the time of the sign-in. We never receive your password for those services.

Shop profile

Shop name, category, description, website, country, currency, team size, sales channels and expected message volume.

Assistant settings

The assistant’s name, tone, language and greeting, whether auto-reply is on, and the keywords that hand a conversation to a person.

Catalogue

Products you import — names, prices, descriptions, images and stock notes — used to answer questions about what you sell.

Channel connections

The Facebook Page you connect, its name and id, the linked Instagram account, and the access token needed to reply. Tokens are encrypted before they are stored.

Conversations

The messages exchanged with your customers, their delivery status, and the notes the assistant writes for your team. See section 3.

Technical records

Server logs containing your IP address, the time and the request, kept for security and rate limiting. These are ordinary web-server logs, not a browsing profile.

Payments

None today: this version does not take payments and has no billing code. If paid plans are introduced, card details will go to a payment processor and never to us.

3. Messages and customer records

When someone messages a shop through a connected Page, we receive the message, the sender’s page-scoped id (or WhatsApp number), their display name, the channel, the language they wrote in, and the time. If the conversation contains a delivery address or a phone number, we store it with the customer record so the shop can fulfil the order, and we mark whether a person typed it or the assistant inferred it.

The shop decides what happens to that data. It comes from the shop’s Page, it is answered on the shop’s behalf, and it is deleted when the shop asks us to delete it or closes its account. We do not use it for advertising, we do not sell it, and we do not build profiles of customers beyond what is needed to answer them.

If you are a customer rather than a shop, the fastest route is to ask the shop whose Page you messaged. You can also write to us (see section 13) and we will pass the request on and delete what we hold.

4. Cookies and local storage

We do not use advertising cookies and we do not run analytics or tracking pixels on the public pages. What we do store in your browser:

• Sign-in token — a refresh token in localStorage, so you are not asked to sign in on every page. It is removed when you sign out.
• Password reset state — a short-lived value in sessionStorage while you are resetting a password. It disappears when the tab closes.
• Admin session cookie — only if you use the Django admin, which is restricted to staff accounts.

Clearing site data in your browser signs you out and deletes all of the above. The data deletion page explains what to do when you want the server-side copy gone as well.

5. Why we use it

• To run the service — sign you in, keep your shop settings, answer messages, show the inbox.
• To answer accurately — match a question to your own catalogue rather than inventing an answer.
• To keep accounts secure — rate-limit sign-ins, expire tokens, detect abuse, investigate incidents.
• To support you — when you write to us about a problem, we look at the records needed to fix it.
• To meet the law — respond to a lawful request, and keep the records we must keep.

Where a legal basis is required, we rely on your contract with us for the first two, our legitimate interest in security for the third, consent where you have given it, and legal obligation for the last.

6. Who else sees it

We do not sell personal data. It is shared only with the services that make the product work:

• Meta Platforms (Facebook, Instagram, WhatsApp) — messages arrive from Meta and replies are sent through it, so Meta necessarily handles their content.
• Google — only if you choose to sign in with Google, to confirm your identity and verified email address.
• An AI provider — only when the server is configured with a language model key. In that case the text of a customer’s question and the relevant catalogue entries are sent to generate a reply. Without a key, the built-in rule set answers locally and nothing leaves our server.
• Our email provider — to deliver password-reset and notification messages, which includes the address it is sent to.
• Our hosting provider — the servers and database where the data is stored, under a contract that limits their use of it.
• Authorities — when the law compels us, and only to the extent required.

7. Where it is processed

Your data is stored on servers we operate, currently in one data centre. The providers listed above — Meta, Google, and any AI provider configured for your workspace — may process data outside your country, including in the United States. Where that happens we rely on the providers’ standard contractual terms for international transfers.

8. How long we keep it

• Account and shop records — while your account exists, then deleted (or irreversibly anonymised) when you close it.
• Conversations and customer records — until the shop deletes them or the account is closed. There is no automatic expiry of your shop’s message history.
• Sign-in attempts and OAuth state — minutes. A consent link is good once, for ten minutes at most.
• Password-reset codes — fifteen minutes, stored only as a hash, and single-use.
• Refresh tokens — seven days from last use; revoked on password change.
• Server logs — a short rolling window for security and debugging, not archived indefinitely.

9. How it is protected

Passwords are hashed with Django’s default hasher and never logged. Page access tokens are encrypted at rest with a key held in the server environment. Traffic to the site is over TLS. Access to the production database is limited to the server and to us. No system is perfect: if a breach ever affects your data, we will tell you and the relevant authority without undue delay.

10. Your rights

Subject to local law, you can ask us to:

• Show you the personal data we hold about you;
• Correct anything wrong — most of it you can edit yourself in Settings;
• Delete your data, as described on the data deletion page;
• Export it in a machine-readable file;
• Stop certain processing, or withdraw consent you gave earlier;
• Complain to your data protection authority.

We answer within 30 days. We may need to confirm you control the account before acting — usually by replying from its email address.

11. Children

Selleena AI is a tool for businesses and is not intended for anyone under 18. We do not knowingly create accounts for children. If a child has sent a message to a shop, that message is handled like any other customer message and can be deleted on request.

12. Changes

When this policy changes in a way that matters, we will update the date at the top and tell account holders by email before the change takes effect. Earlier versions are available on request.

13. Contact

Questions, requests and complaints: support@selleena.com. We aim to reply within five working days.