VamimiExplore products

Privacy

What VamimiAI stores, why, and how to download or delete it.

What we store

  • Your account: your email address and name. With Google, the name and picture on your Google profile; with email and password, the name you give, and your password only as a one-way hash kept by our sign-in provider, never readable by us.
  • Your workspace: chats, diagrams (as their plans and layouts), folders and their instructions and files (as text), settings and saved prompts. Keys or passwords found in an imported n8n, Make or Zapier export are removed before anything is saved.
  • Usage: for each request that uses the AI model or imports a workflow: when, its size in tokens, its cost, how long it took, whether it worked, and the country it came from (from the network, never your IP address).
  • Product analytics (you can turn these off in the app): named actions such as “diagram built” or “handover created”, with counts. Never the text you write.
  • Approximate location and device: your country (from the network, not your address), language, time zone, device type, browser and operating system names, a screen-size range, and the site that sent you. We do not store your IP address.
  • Feedback you choose to send on a reply.
  • Before you have an account: if you send an AI message without signing in, we count it against a random number your browser makes up and keeps. With it we store how many AI messages that browser sent, when, the country, and, if you then sign in from the same browser, that it did and with which account. Your browser forgets the number when you sign in. Never the text you write, and not your IP address.

Why

To run the service you signed up for (your account and workspace), to bill and apply plan limits (usage), to keep it secure and stop abuse, and to understand how it is used so we can improve it (analytics, which you can switch off).

Who processes it

Our hosting provider, our database and sign-in provider, Google (for signing in), and an AI model provider that processes the messages and files you send so it can write replies. They act on our instructions. We do not sell your data, and the only advertising tool we use is TikTok's, described below.

Who can see your chats

You. VamimiAI can open an account's chats to give support or to stop abuse; every time that happens it is recorded in an audit log.

How long

Your workspace and account details: until you delete them or your account. Usage records: as long as your account exists (they are used for billing). Raw analytics events: 180 days, after which only daily totals remain. The random number of a browser that chatted without an account: until 180 days after its last message, after which only daily totals remain.

Your choices

In the app you can download everything (Settings › Your data), turn usage analytics off, and delete your account, which removes your workspace and records for good. For anything else, including a copy of what we hold or a correction, write to a.mhamimi@outlook.com.

Advertising measurement (TikTok)

We advertise on TikTok. To learn which ads bring people who sign up, start a trial or pay, our pages load TikTok's pixel, a script from TikTok that records page views and sets TikTok's cookies, and keeps the click id TikTok adds to an ad's link in a cookie of ours for 30 days. When you sign up, start a trial, open checkout or pay, we also tell TikTok directly from our server. What TikTok receives: the event, its time, the page, that click id and TikTok's cookie, your browser's user agent and IP address (sent to TikTok, never stored by us), and your email address and account id only as one-way hashes, never in the clear. Never the text you write. TikTok uses this under its own privacy policy.

Turning usage analytics off in the app also turns this off for your account and stops the pixel loading in that browser.

Cookies and storage

We use your browser's storage to keep you signed in, remember your preferences and keep a working copy of your chats so the app is fast and works offline. TikTok's pixel also sets its own cookies, described below.

Last updated 2026-11-19.