Legal

Privacy Policy

Last updated: 5 November 2026

1. Who we are

AtlasLaunch AI is made by Atlas AiDev, Dhaka 1207, Bangladesh (“we” or “us”). We are responsible for the personal data described here.

This policy covers the AtlasLaunch AI website, the API, the JavaScript SDK, the dashboard, and the AtlasLaunch AI WordPress plugin when it connects to these services. The separate website atlasaidev.com has its own privacy policy.

For the visitors of a website that uses AtlasLaunch AI, that website’s owner decides to use the assistant; we process the questions on the owner’s behalf, as described below.

2. What we collect

When you create an account or connect a website

• Account details: your email address, your name if you give it, and your password (stored only as a secure one-way hash).
• Websites: the address, name and platform of each website you connect.
• Keys: secret keys are stored only as a secure hash plus a short prefix. The project key behind a public site key is stored encrypted.
• Licences: if you add a Pro or Agency licence, we keep the licence’s ID from Freemius, never the licence key itself.

Your website’s content (the index)

The pages and products your website sends, or that we read from its sitemap: their address, title, type, date, text and short facts such as price, stock, sale status, categories, rating, author or cooking time. This is the content your visitors’ answers come from. It is stored for your website until you remove it, remove the website, or delete your account. We read only the website you name, follow its robots.txt, and skip pages marked noindex.

Taught answers: questions and answers you write yourself for the assistant are your content too, stored until you remove them, the website, or your account.

When a visitor uses the assistant

• The question and the last few messages are sent to us to find the answer. They are processed in memory and are not stored or written to our logs, except as described under “Learning from visitors’ questions” below.
• Counts: how many answers each website received per day and per month, for its plan. Failed requests are logged with their time, website, error code and client version (not the question), so you can see what went wrong.
• Abuse limits: the visitor’s IP address and a random visitor id made by the SDK are used only to limit how many questions one visitor can send. They are kept in memory counters for at most one day and never written to our database.
• In the visitor’s browser: the SDK keeps the conversation in the browser tab for 30 minutes (sessionStorage) and a random visitor id (localStorage). It sets no cookies. Details a visitor types into a step-by-step form (for example at checkout) stay in the browser and are never sent to us.
• Voice: the microphone and read-aloud buttons use the browser’s own speech features. Some browsers send the spoken audio to their maker’s speech service (for example Google for Chrome) to turn it into text; that happens between the visitor and the browser maker, not us. We receive only the text.

Learning from visitors’ questions (only if the website owner turns it on)

A website owner can switch on “Learn from visitors’ questions” to see what visitors ask, what their assistant couldn’t answer, and teach it better answers. It is off by default. When it is on, we keep:

• the questions visitors ask (answered or not), for the owner’s analytics and review,
• answers a visitor marked “Not helpful”, with the question that was asked, and
• the optional comment a visitor writes in the short survey (“Are you getting the answers you expected?”).

Before anything is kept, we remove email addresses, phone numbers, long numbers (such as card or order numbers), postcodes and the hidden part of web addresses. The same question is kept once, with a count of how often it was asked. We never keep the visitor’s IP address, visitor id or the rest of the conversation with it. Clearly unrelated questions are not kept. For every website, learning on or off, we also keep daily counts only: how many questions were asked in the chat and the search box, how many were answered, how many were spoken, the thumbs and survey stars, what the answers led to (a cart, the pricing or Contact page, a linked page opened, a suggested question clicked), which of the website’s own pages answered, the address of the page the question was asked from (without anything after a “?” or “#”), and the language of the question. These counts contain no question text and nothing about the visitor. Once a week the website owner gets these numbers by email, unless they switch it off. Each question is deleted 30 days after it was last asked, or earlier when the website owner answers or dismisses it, switches learning off (which deletes all of them at once), removes the website or deletes their account. The website owner sees these questions in their dashboard or WordPress plugin, and must say so in their own privacy notice.

When you visit this website

We count page views with our own small script, without cookies and without storing anything on your device. For each page view we use the page address, the site that sent you, your browser type (to tell phones from computers) and your country (as reported by our network provider). To count each visitor once per page per day we use a one-way code made from your address, browser and the date, kept only for that day in memory and never written to our database. Only daily totals per page are stored. If your browser sends a Global Privacy Control signal, you are not counted at all. Site search runs in your browser; we keep only daily totals of the words searched, never who searched.

Other

• Sign-in sessions: the IP address and browser of each signed-in session, used to keep your account secure.
• Security codes and approvals: one-time sign-in codes, and the IP address of a request to add a website to an existing account.
• Messages you send us: support messages.

3. What we don’t do

• We don’t store your visitors’ questions or the answers, unless you turn on “Learn from visitors’ questions” (described above).
• We don’t send your content or your visitors’ questions to an outside AI company: the AI runs on our own servers.
• We don’t sell data, and we don’t use your content or your visitors’ questions to train AI.
• This website uses no advertising cookies.

4. Why we use data

• To provide the service you asked for (our contract with you): your account, your websites’ indexes, answering your visitors, counting your allowance and applying your plan. Questions kept for “Learn from visitors’ questions” are processed on the website owner’s behalf, only because they turned it on.
• To keep the service safe and working (our legitimate interest): limits against abuse, fixing errors and protecting your account.
• To understand how the website is used, counting visits without cookies (our legitimate interest).
• To email you about your account: sign-in codes, security notices, website approvals and allowance alerts.
• To meet legal obligations, where the law requires us to keep or share information.

5. Who helps us run the service

6. International transfers

Our servers may be outside your country, so data may be processed there. Where the law requires it, we rely on appropriate safeguards, such as the standard contractual clauses our providers offer.

7. How long we keep it

8. Your rights

Depending on where you live, you can ask to see, correct, export or delete your personal data, or object to how we use it. You can:

• Remove content from your website’s index at any time, through the plugin or the API.
• Delete your account yourself from the Account page in the dashboard. This removes your account, websites, indexes, keys, usage and sessions straight away (backups roll off within 30 days).
• Contact us for anything else through our contact page. We reply within 30 days.
• Complain to your local data protection authority if you think we’ve handled your data wrongly.

Visitors of a website that uses AtlasLaunch AI can ask that website’s owner, or us, about their data. Questions are not stored unless the owner turned on learning; even then they are kept without anything that identifies the visitor, so we usually can’t tell which question was theirs. The website owner can delete any kept question, or all of them by switching learning off.

9. Cookies

The dashboard uses one essential cookie to keep you signed in. It is secure, can’t be read by scripts, and ends when you sign out or the session expires. This website counts visits without cookies, and the SDK on other websites sets no cookies. If we ever add Google Analytics to this website, its cookies will be set only after you click Accept on a cookie bar, and you can change your choice at any time. Only for our own staff: signing in as staff sets a cookie (ala_staff) so that our own visits are left out of the statistics.

10. Security

Passwords, secret keys and session tokens are stored only as secure hashes, and the keys behind public site keys are stored encrypted. All traffic is encrypted, and our backups are kept off-site with restricted access. No system is perfectly secure, so if we ever learn of a breach that affects you, we will tell you promptly.

11. Children

The AtlasLaunch AI dashboard is for businesses and adults and isn’t intended for anyone under 16. We don’t knowingly collect children’s data.

12. Changes to this policy

We’ll update this page when our practices change, and change the date at the top. For important changes, we’ll let account holders know by email first.

13. Contact

Questions about privacy? See our contact page or email [email protected].