WArkAiMation
← Back to home

Privacy Policy

Last updated: 8 October 2026

The short version

WArkAiMation is a WhatsApp inbox, automation and marketing service run by Victory TechNxt Private Limited. This policy covers the people who sign up for it, the contacts a business messages through it, and the visitors to websites that carry its tag.

For the account data of people who sign up, we decide why and how it is used. For a business's contacts and website visitors, the business decides and we process the data for it. We do not sell personal data.

A visitor's own tick on an unticked, optional WhatsApp box on a business's form counts as consent to WhatsApp messages from that business straight away, and replying STOP ends them (section 3). The website tag keeps a short list of entries in a visitor's browser, and for visitors in the EU, EEA and UK most of them wait for the website's own consent signal (section 8). To ask a question or use a right, write to [email protected].

  1. Who runs WArkAiMation?
  2. What personal data do we collect?
  3. Why do we use it, and on what basis?
  4. Who do we share it with?
  5. How do we protect it?
  6. How long do we keep it?
  7. What are your rights, and how do you use them?
  8. What cookies and browser storage do we use?
  9. What about children?
  10. Does personal data leave India?
  11. How do we change this policy?
  12. How do you contact us?

1. Who runs WArkAiMation?

WArkAiMation is operated by Victory TechNxt Private Limited (CIN U62090MH2026PTC467479), whose registered office is Office No 906, Plot No 47, Sector 15, Navi Mumbai, Panvel, Raigarh (MH), Maharashtra 410210, India. In this policy "we" and "us" mean that company. You can reach us at [email protected].

We act in two roles. For the people who sign up for WArkAiMation, we are the controller of their account data. India's Digital Personal Data Protection Act, 2023 (the DPDP Act) calls a controller a "data fiduciary". For the contacts a business messages and the visitors to a business's website, the business is the controller or data fiduciary and we are its processor: we handle that data on the business's instructions, to run the service. Section 2 says which role applies to each kind of data.

2. What personal data do we collect?

Account data (we are the controller)

When you sign up we collect your name, your company name, and an email address, a WhatsApp number, or both, depending on how you sign up. We confirm a WhatsApp number with a one-time code sent to it and keep the time you confirmed it. If you set a password we keep a one-way hash of it and do not keep the password itself. We also keep your role in the workspace, the workspace's billing email, and the referral code if someone introduced you.

If you tick the box asking for setup help and trial reminders on WhatsApp, we keep the time you ticked it and the version of the wording you saw. We read your country from your IP address and use it as the workspace's starting default country, which you can change in Settings. During a trial we record steps such as connecting WhatsApp, sending a first message or paying, so that we can time our emails and reminders and see where trials stall.

For plans and payments we keep the plan, the billing period, the amounts, and the order and payment references the payment gateway gives us. Card, UPI and bank details are typed into the gateway's own window or page and do not reach us.

Contacts and conversations (the business is the controller)

A business keeps its customers' details in its workspace. For each contact that is usually the name, WhatsApp number and WhatsApp profile name, email address and company, the business's own notes, tags and custom fields, the language the contact writes in (we work it out from their messages), and whether they have opted in to or out of WhatsApp marketing, with when and why that was recorded. The workspace also holds deals, tasks, message templates, automations, broadcasts and usage records. The business decides what goes in. We process it for the business.

WhatsApp messages (the business is the controller)

Messages reach us through Meta's WhatsApp Business Cloud API. We keep each message a contact sends to the business's number and each message the business sends, with its text, its type, a link to any media, its time and its delivery status. Anyone in the workspace who has access to the inbox can read them. Meta keeps its own records of these messages under its own terms. If the business has connected another Victory TechNxt product, the first message of a new contact is also copied to it (section 4).

Website visitors (the business is the controller)

A business can paste one line of code, the website tag, into a website it controls. The tag has two parts, and the business switches each on or off: a WhatsApp button, and a copy of the website's enquiry forms. Form copying is off until the business turns it on, and it works only on a website the business has proved is its own. If you visit such a website, this is what happens to your information.

  • Enquiry forms. When you send a form, the tag sends us a copy of what you typed: usually your name, email, phone number and message, and up to 40 fields in all, each with its label. We also keep the form's title, the page address without anything after a question mark, the first campaign tags (utm) the tag saw in that browser tab, each cut to 150 characters, a random identifier for the browser tab, and the country of your IP address. Every checkbox on the form that mentions WhatsApp, email, SMS, a newsletter or updates is recorded with its wording and whether it was ticked, ticked in advance, required, or part of a terms box.
  • What the tag leaves out. It is built to leave out passwords, sign-in and password-reset forms, hidden fields, files, card details and any card number typed into another field (replaced with "[card number removed]"), one-time and verification codes, PINs, bank account numbers, government ID numbers such as Aadhaar, PAN, passport, voter ID and driving licence numbers, and answers to security questions. It recognises these by field names and labels, so an ID number typed into a box that is labelled only "Number" could be kept. Our servers apply the same rules again.
  • What happens to a form copy. If the form has a phone number we can place with a country, the business gets a contact. If it has none, the business sees the enquiry and may add a number. A field about someone else, such as a child, a student, a friend or a referral, is kept in the enquiry but never becomes the contact. Answers about health, religion, caste and similar subjects are kept like any other field. Your form still goes to the website's own handler as before. We receive a copy.
  • The WhatsApp button. When you tap it, we keep the page address, the page title, any utm tags and a short reference code for 72 hours. We do not store a visitor id with it. The reference code is added to your first WhatsApp message as "(Ref XXXXXX)", so the business can see which page you came from, and that text stays in the message. If you send that message within the 72 hours, the page address, title, utm tags, reference code and time of the tap are kept with your contact. Pages the business marks as meant for children get no reference code and no record.
  • Country. We read the country of your IP address from the header Cloudflare adds to the request. We use it to place a phone number typed without a country code, and to apply the rules for visitors in the EU, EEA and UK. The form record holds the country and no IP address.

The tag sets no cookie. Section 8 lists the browser storage it uses.

Technical data (we are the controller)

Our servers keep request logs with IP addresses, for security and to apply rate limits. The counters that limit form posts and button taps per IP address (and, for forms, per tab identifier) last five minutes. We also count, per website and per day, how many form posts or button taps we refused and why. Those counts name no person. When someone asks for a WhatsApp sign-in code, we record the number, the IP address, the time, the outcome and a keyed hash of the code, so that we can limit requests and spot abuse.

3. Why do we use it, and on what basis?

For each purpose below we name the basis that applies under the GDPR and the UK GDPR. Under the DPDP Act we rely on your consent where we ask for it, and on the uses the Act allows without consent, such as data you gave us for a purpose you asked for and compliance with the law.

  • Running your account and the service: sign-in, the inbox, automations, sending and receiving messages, support. Basis: contract.
  • Payments and billing records. Basis: contract, and our legal obligations.
  • Emails about your account, such as the verification link, billing notices and, during a trial, a short series about setup and the trial. Basis: our legitimate interest in running the service and helping trials work. The series stops when you subscribe. You can ask us at [email protected] to stop it sooner.
  • WhatsApp setup help and trial reminders. We send them only if you ticked the box at sign-up. Basis: your consent, which you withdraw by replying STOP.
  • Security and abuse prevention: request logs, rate limits, the record of sign-in code requests, and a one-way hash of the WhatsApp number used to start a free trial, so that a number gets one trial. Basis: our legitimate interest.
  • Understanding trials through the steps listed in section 2. Basis: our legitimate interest.
  • Processing a business's contacts and website visitors. We do this only on the business's instructions, to provide the service. The business is responsible for its own basis and for its notice to those people.
  • Legal obligations and lawful requests from public authorities. Basis: legal obligation.

We do not sell personal data.

WhatsApp marketing and the tick on a form

WhatsApp's rules require a business to have a person's opt-in before it starts a marketing conversation. WArkAiMation keeps one of three states for each contact: unknown, granted or denied, with the time and the reason.

  • Granted. A contact is marked as granted when the person ticks a box that names WhatsApp on a business's website form, as long as the box was not ticked in advance, was not required to send the form, and was not part of agreeing to terms or a privacy policy. The same happens when the person messages the business first or sends START, or when the business's staff records their consent.
  • A form tick counts at once. WArkAiMation does not send a confirmation message or ask a second time. From the moment the form is sent, the business can message that person on WhatsApp, including broadcasts and automatic messages, until the person replies STOP.
  • STOP. Replying STOP, or a short phrase such as UNSUBSCRIBE, ends marketing messages from that business through WArkAiMation. A later form tick does not undo it. Only the person's own START message, or the business's staff recording the person's consent, does.
  • No tick. If no box was ticked, the business still receives the enquiry and, when the form gave a phone number the platform can place with a country, the contact. The platform leaves that contact out of the business's broadcasts until the person opts in or messages the business first.
  • The notice belongs to the business. The business that owns the form writes the wording next to the tick and is responsible for it. We do not see that wording on the page, and we cannot check who typed a phone number into a form. If a business messages you after someone else entered your number, reply STOP, tell the business, and write to us if you need help.

4. Who do we share it with?

Service providers

We use the providers below. Each receives what its part of the service needs.

  • Hosting. DigitalOcean runs the servers and databases that hold the data described above.
  • Cloudflare sits in front of our servers. Every request passes through it, including the visitor's IP address, and it tells us the visitor's country.
  • Meta delivers WhatsApp messages through the WhatsApp Business Cloud API, and delivers our one-time sign-in codes.
  • AI providers (Google, OpenAI, xAI and Anthropic) receive message text when an AI feature runs. See below.
  • Email. An email (SMTP) service sends our messages to account holders: verification links, trial and billing emails, and alerts.
  • Payment gateways. Razorpay, and Stripe where it is switched on, process payments and, with Razorpay, automatic renewal that the account holder has authorised.
  • Google Fonts serves the typeface our pages use. When a page loads, the visitor's browser fetches it from Google, so Google receives the visitor's IP address.

AI providers. When an AI feature runs, the text it works on goes to the AI provider configured for the workspace, or to ours if the workspace has set none. That covers a suggested reply (the contact's name, or their number when there is no name, and the last 12 messages of the thread), a thread summary (the thread), a message template draft (what the user typed), a reply written in the customer's own language (the business's text), and, in an automated flow where AI matching is switched on, the customer's reply, so that the model can pick the menu option the customer meant.

Meta messaging analytics. We have enabled Meta's performance insights on our WhatsApp Business account so we can report delivery, read and click rates on message templates. Under that setting, Meta collects data from conversations sent through the platform and anonymises it to improve the services it provides to us and to other businesses, and message templates carry link tracking so that clicks on links inside them can be reported. This processing is carried out by Meta under its own terms. Link tracking can be turned off for an individual template on request.

Connected Victory TechNxt products

A business can connect its WArkAiMation workspace to ChatAICRM or ProNxt, two other Victory TechNxt products. Nothing is passed on for a business that has not connected its own workspaces. Once it has, WArkAiMation sends the connected product:

  • a copy of each stored website form: name, email, phone, company, the answers after filtering, the page address without anything after a question mark, the utm tags, the country of the IP address, and the WhatsApp and email opt-in or opt-out choices;
  • a copy of each new WhatsApp contact: name, number, email and company if known, language, opt-in state, the page address, title and utm tags of the button tap when the first message carried a reference code, the number of messages in the chat, and the contact's first message cut to 1,000 characters;
  • the first message again when a contact writes after seven days of silence, and any STOP or START change.

Later messages stay in WArkAiMation. Answers about health, religion, caste and similar subjects are left out of form copies unless the business turns that on. When a business connects, it can also choose to send its earlier leads for a period it sets. WArkAiMation keeps its own copy of everything it sends, and the connected product keeps its copy under its own rules. Disconnecting stops further copies. Copies already delivered stay in the other product.

Information also comes back. Every 15 minutes while the connection is on, WArkAiMation reads the connected product's list of opt-outs and its list of erasures. An opt-out recorded there is applied to the matching contact here. An erasure recorded there is applied here at once when the matching record holds only the forwarded enquiry, and otherwise an admin of the business decides. After a disconnect, WArkAiMation stops reading opt-outs and keeps reading erasures for 30 days.

Public authorities

We release personal data to a court, regulator or law-enforcement body only against valid legal process, after we have checked that the request is genuine, lawful and within the authority's powers. We push back on requests that are unlawful or too broad, and we disclose only the minimum needed for the person and period concerned.

People inside an account

Inside a workspace, an admin decides through roles and permissions who can see and do what. An agency can open the workspaces of the client businesses it created. Super administrators at Victory TechNxt can open any workspace.

5. How do we protect it?

  • All traffic to warkaimation.vtnverse.com uses HTTPS, and the site tells browsers to keep using it.
  • Passwords are stored as one-way hashes. API keys are stored as hashes.
  • WhatsApp access tokens, WhatsApp app secrets, AI provider keys and the keys for connections to other Victory TechNxt products are encrypted in the database.
  • We check the signature of every webhook from Meta, Razorpay and Stripe before acting on it. Calls between connected Victory TechNxt products are signed.
  • Each workspace's data is kept apart from every other workspace's, roles limit what team members can do, and requests are rate limited.

No system is perfectly secure. If we confirm a breach of personal data held for a workspace, we tell the account owner by email without undue delay, so that they can meet their own legal duties. Report a vulnerability to [email protected].

6. How long do we keep it?

We have set no automatic time limit on most data. It stays for as long as the workspace exists, until the business deletes it or uses Erase person (section 7). That covers the account, contacts, conversations, website form copies, enquiries held for review, and payment and plan records. These have time limits set in the software:

  • WhatsApp button taps: deleted after 72 hours, by a job that runs once a day. A tap matched to a first message within those 72 hours stays with the contact.
  • Counts of refused form posts and taps: deleted after 30 days.
  • The counters that limit form posts and button taps per IP address: gone after five minutes.
  • Copies waiting to be sent to a connected product: the content is removed 30 days after delivery. A failed or cancelled copy keeps its content for 30 days. A copy held for 30 days is marked failed.
  • Email verification links expire after 48 hours, and WhatsApp sign-in codes after 10 minutes.

The hashes kept for Erase person last as long as the workspace.

When a workspace is deleted. An admin can delete the workspace in Settings, Danger zone. Deletion is permanent and removes the workspace's users, contacts, conversations, messages, form copies, button taps, automations, templates, connections, usage records, payment and plan records, and the copies of our emails to its billing address. Some things remain:

  • A keyed one-way hash of the WhatsApp number used to start a free trial, so that deleting an account and signing up again does not give a second trial.
  • The record of sign-in code requests (number, IP address, time, outcome and the code's keyed hash). We have set no time limit on it, and deleting a workspace does not remove it.
  • Database backups. We take backups for recovery, and a deletion in the live service does not change a backup already taken.
  • Copies held by others: Meta, the AI providers, the payment gateway, the email service, and any connected product that has already received a copy.

7. What are your rights, and how do you use them?

Under the DPDP Act you can ask for a summary of the personal data we process about you and how we process it, ask us to correct, complete or update it, ask us to erase it, withdraw a consent you gave, ask for redress of a grievance, and nominate someone to act for you if you die or cannot act. Under the GDPR and the UK GDPR you can also ask for a copy of your data in a common format, ask us to restrict the processing, and object to it. The law limits some of these rights in some situations, for example where we must keep a record.

If you have an account. Write to [email protected] from the email address on the account, or from the WhatsApp number on it, and say what you want. You can also change your name, email and password in the app, and delete the workspace under Settings, Danger zone. We may ask you to confirm who you are before we act. We answer within the time the law sets, which is one month under the GDPR.

If you are a business's contact or a visitor to its website. Ask the business that runs the website or sends you messages, because it controls your data. It can ask us to act, and you can also write to [email protected]. To stop WhatsApp marketing from a business, reply STOP to its message.

Erase person. A workspace admin can use Erase person on a contact.

  • In this workspace it removes the contact, their messages and conversations, the enquiries that carry their email address or number, and the page-click records that point to them. Deals are kept but unlinked, and a deal title that holds the person's name, phone or email is replaced.
  • If the business has connected another Victory TechNxt product, or disconnected one in the last 30 days, we tell that product to erase the person too. We send it a reference and keyed hashes of the email address, the phone number and the lead's reference. The details themselves are not sent. A hash is made with a secret, so it cannot be read back as an address or number. Only someone who holds that secret and already has the address or number can check whether they match.
  • The other product acts on this only if it received the person from this workspace. It then erases that record at once when it holds nothing else about the person. When it holds more, or when another record there matches only by email address or number, an admin of that business decides.
  • A plain delete or merge of a contact is local to this workspace. It sends nothing to another product and leaves no hash, so it does not count as an erasure.
  • Both products keep the hashes for as long as their workspaces exist, so that an older copy of the person's details passed between them cannot bring the person back. An enquiry the person sends afterwards is accepted as a new one.
  • Erase person does not reach backups, Meta's records, the person's own phone, or the website's own form handler that received the original form.

Complaints. Tell us first, so we can put it right. If you are not satisfied, you can complain to the Data Protection Board of India. If you are in the EU or EEA, you can complain to your national data protection authority, and in the UK to the Information Commissioner's Office.

8. What cookies and browser storage do we use?

Cookies. Our own code sets no cookies, on our own pages or through the website tag. Other providers take part when a page loads and can set their own cookies under their own policies: Cloudflare sits in front of our servers and Google serves our typeface. Razorpay's checkout script loads on every page, this one included, so the payment window can open. When it loads it stores a cookie and entries in local and session storage on our domain. Meta's JavaScript library loads when a signed-in user opens Settings, where one-click WhatsApp connection is available. We start it with its cookie option on, so it can store a cookie of its own on our domain.

The app (local storage in your browser). After you sign in, the app keeps your sign-in token until you sign out or it expires (wa_token), the client workspace an agency admin has opened (wa_acting_ws and wa_acting_ws_name), whether you hid the setup checklist (wa_setup_dismissed) and whether the side menu is collapsed (wa_sidebar_collapsed).

The website tag (on a business's website). These entries sit in the tab's session storage, which the browser clears when the tab closes, unless noted:

  • vtn:cfg:warkaimation:<site key>: a copy of the tag's settings (whether form copying is on, whether the site is for children, which tags to load), read for five minutes.
  • vtn:w:<site key>: a copy of the button's settings (its colour, label and the business's WhatsApp number), read for five minutes. It holds nothing about the visitor.
  • chatai:fc:v: the random identifier for the tab, written when a form copy is sent.
  • vtn:utm: the campaign tags, written the first time a form copy is sent or the button is tapped.
  • chatai:fc:sent and vtn:fc:win: when a form copy was sent, the page path, the form's action address and its field names without anything typed into them, and which product's tag took the copy. These let the steps of a multi-page form join up.
  • vtn:child:<host>, in local storage: a time, written on a page the business marked as meant for children, and honoured for 30 days.

For visitors in the EU, EEA and UK, every one of these entries except the button's settings waits in the page's memory and is written only after the website signals consent, either a data-vtn-consent mark on the page or Google Consent Mode with analytics storage granted. The tag treats a visitor as being in those regions when the country lookup in section 2 says so, and it also waits while the country is not yet known. The button's settings are written for every visitor.

9. What about children?

WArkAiMation is a service for businesses. People under 18 should not create an account.

For websites that carry our tag, the DPDP Act asks the business that runs the website to get verifiable consent from a parent or guardian before processing a child's personal data, and bars tracking and behavioural monitoring of children. That duty sits with the business. To help, we give it a switch, "This website is for children", in Settings, Website. With the switch on, the tag copies no form from that website, adds no reference code to the WhatsApp button and records no taps, and our servers refuse any that arrive. If another Victory TechNxt tag on the same page is marked for children, our tag copies nothing from that page either.

The switch works only where the business uses it. A form on a website that is not marked is copied whatever it asks, including a parent's answers about a child such as the child's name, class or date of birth. Those answers are kept in the enquiry and never become the contact. Our terms ask the business to mark such sites or to turn form copying off for them.

10. Does personal data leave India?

It can. Our hosting provider runs our servers, and Meta, the AI providers, Cloudflare, Google and the payment gateways run their own systems, some of them outside India. Personal data therefore reaches systems outside India whenever a feature that connects to one of them is used: a WhatsApp message, an AI feature, a payment or a page load. The DPDP Act allows transfers abroad except to countries the Government restricts.

EU and UK law require a safeguard when personal data leaves the EU, EEA or UK. If those laws apply to data in your workspace, tell us at [email protected] and we will discuss the transfer terms you need.

11. How do we change this policy?

When we change this policy we update the date at the top of the page. If a change affects how we use personal data in a way that matters to you, we email the account owner or tell them in the app before it applies.

12. How do you contact us?

Write to [email protected]. Say which workspace or website your question is about and what you want us to do. We may ask you to confirm who you are before we act on a request about personal data.

Victory TechNxt Private Limited, CIN U62090MH2026PTC467479, Office No 906, Plot No 47, Sector 15, Navi Mumbai, Panvel, Raigarh (MH), Maharashtra 410210, India.

TermsPrivacyHome