Legal
Privacy Policy
Last updated: 15 October 2026
The short version
- The file you send is deleted once its model is made. We keep the finished 3D model for you until you delete it.
- We never sell your data, and we never use your files or models to train AI.
- We keep only what we need to run your account, count your usage and keep the service safe.
- You're in control. You can delete your account, its sites and its models at any time.
1. Who we are
AtlasAR Cloud is made by Atlas AiDev, Dhaka 1207, Bangladesh (“we” or “us”). We are responsible for the personal data described here.
This policy covers the AtlasAR Cloud website, the API, the dashboard (including its Create 3D page), model hosting, and the AtlasAR WordPress plugins when they connect to these services. The separate website atlasaidev.com has its own privacy policy (opens in a new tab).
2. What we collect
When you create an account or connect a site
- Account details: your email address, your name if you give it, and your password (stored only as a secure one-way hash).
- Sites: the address, name and platform of each website you connect (for example, WordPress).
- API keys: stored only as a secure hash plus a short prefix so you can recognise them. We can't read your full key.
- Licences: if you add an AtlasAR Pro licence, we keep the licence's ID from Freemius, never the licence key itself.
- Webhooks: the address you give us for model updates, and its secret (stored encrypted).
When you make a model
- The file you send: a 3D file (GLB) or a product photo, with the name and real height you give it. We need it only while your model is being made: we delete it as soon as the model is ready or has failed. Photos are cleaned of hidden details such as location and camera data before we use them.
- The finished model: the 3D file we make, with its size and statistics. It is kept until you delete it (models made on the dashboard's Create 3D page: 2 hours). Anyone with a model's link can view it, so don't send anything private.
- Usage totals: how many models each site made per day and per month. Failed requests are logged with their time, site, error code and client version, so you can see what went wrong in your dashboard.
- Webhook deliveries: when we told your site about a model, and whether it answered.
- 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 site to an existing account.
- Messages you send us: support messages.
From the WordPress plugins
The AtlasAR plugin sends nothing to AtlasAR Cloud until you connect it and tick the agreement. Connecting sends your site's address and name and the email you enter. After that, a file is sent only when you click Optimize with AtlasAR Cloud or Make 3D model (Photo to 3D) on a product. The Flat product tool runs in your browser and sends nothing. No data about your site's visitors is ever sent.
When a website shows your models with the viewer
When a page shows one of your AtlasAR Cloud models (<atlasar-viewer model="mdl_…">), the viewer adds one to daily totals for that model when a shopper sees the 3D view, turns it, opens it in AR or uses the try-on. We store only the day, the model and the totals: no cookies, no IP address, no visitor, device or page information. The address is used for a moment only to stop floods, in memory. You see the totals under Analytics. A page can turn this off with analytics="none". The try-on camera picture never leaves the shopper's device.
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.
On the examples and free model pages, the 3D viewers count what visitors do with them (seen, turned, opened in AR, try-on, colour changes) as daily totals per example or model, and we count free model downloads, the answers to Was this page useful? and What do you build on? the same way: no cookies, no IP address, no visitor id. If you write a note in that box, we keep the note and the page's address only; we remove anything that looks like an email address, phone number or key before saving it, so please do not write personal details there. The try-on camera picture never leaves your device.
3. What we don't do
- We don't keep the files you send after your model is made.
- We don't sell your data, and we don't use your files or models to train AI.
- We don't collect anything about the shoppers who view your models on your site.
- This website uses no advertising cookies.
4. Why we use your data
- To provide the service you asked for (our contract with you): your account, making and hosting your models, counting your allowance and applying your plan.
- To keep the service safe and working (our legitimate interest): preventing abuse and fraud, rate limits, 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, site approvals and allowance alerts. We don't send marketing email from the service.
- To meet legal obligations, where the law requires us to keep or share information.
5. Who helps us run the service
We use a small number of trusted providers, only for the purposes below:
| Provider | What they do |
|---|---|
| Our hosting provider | Hosts our servers. We'll name them here before AtlasAR Cloud opens. |
| Cloudflare | Delivers and protects our websites and API, stores finished models and delivers them to your shoppers, and stores our off-site backups. |
| Our GPU provider | Runs the AI that makes models from photos (Photo to 3D). The photo passes through it and isn't kept. We'll name them here before Photo to 3D is switched on. |
| Freemius | Sells AtlasAR Pro licences, handles payments and confirms whether a licence is valid. |
| Namecheap (Private Email) | Sends our account emails. |
6. International transfers
Our servers may be outside your country, so your 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
| Data | Kept for |
|---|---|
| The file you send (GLB or photo) | Until its model is ready or has failed (a direct upload you never use: about 15 minutes) |
| Finished models | Until you delete them or your account |
| Models made on the Create 3D page | 2 hours |
| Failed-request logs | 14 days |
| Webhook delivery history | 30 days |
| Daily usage totals | 400 days |
| Viewer analytics (daily totals per model, no visitor data) | 400 days, or until the model is deleted |
| Monthly usage totals | Kept as your billing history |
| Sign-in sessions (IP address and browser) | Until the session ends, then deleted |
| Sign-in codes | 1 day |
| Pending site-approval requests | 7 days |
| Account, sites and settings | Until you delete your account |
| Website statistics (daily totals per page, no visitor data) | 25 months |
| Website examples and free models: viewer totals and notes from Was this page useful? | 400 days |
| Backups | 30 days |
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:
- Delete models one by one in the dashboard, through the API or from the WordPress plugin.
- Delete your account yourself from the Account page in the dashboard. This removes your account, sites, keys, usage, sessions and models straight away, and their files leave our storage within minutes (backups roll off within 30 days).
- Contact us for anything else through our contact page (opens in a new tab). We reply within 30 days.
- Complain to your local data protection authority if you think we've handled your data wrongly.
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. If we ever add Google Analytics, 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 (ar_staff) so that our own visits are left out of the statistics.
10. Security
Passwords, API keys and session tokens are stored only as secure hashes, and webhook secrets are stored encrypted. All traffic is encrypted, every uploaded file is checked before any program opens it, 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
AtlasAR Cloud is for businesses and adults. It isn't intended for anyone under 16, and we don't knowingly collect their 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? Reach us through our contact page (opens in a new tab) or by email at contact@atlasaidev.com.