This policy explains what Nexa collects, why, and what you can do about it. “We” means Rayudu Sai Lekha, a sole proprietor in India trading as Nexloid, who provides Nexa. “You” means anyone who visits our website or uses Nexa.
What we collect
- Account details: your name, email, designation and password (stored hashed), or your Google sign-in.
- Organisation details: the organisation name, website, members and their roles.
- Connected data: reports and metadata we read from the sources you connect, such as GA4 and Google Ads. We only read. Nexa never changes anything in a connected account.
- Your definitions: the events, funnels, goals and names you set in Nexa.
- Usage: requests to our servers and errors, to keep Nexa working. For the Nexa MCP server, we record the requests your AI tool makes, how long they take and whether they fail.
- Messages to us: the name, email, company and message you send through the contact form.
- Payments: handled by Razorpay. We receive the plan, amount, status and the payment method type. We never see or store full card numbers or bank details.
How we use it
To run Nexa, answer your questions through the AI tool you connect, send the emails you ask for, bill your organisation and keep the service secure. We don’t sell your data, we don’t use it for advertising and we don’t use it to train AI models.
Your AI tool
When you ask a question in Claude, ChatGPT or another MCP client, Nexa sends that tool the data needed to answer. The provider handles it under its own terms, which you accepted when you signed up with them.
Google user data
When you connect Google Analytics 4 or Google Ads, you sign in with Google and approve access on Google’s own screen. This is what happens with that data.
- What we access: with the
analytics.readonlypermission, the GA4 accounts and properties you can see, their event and field names, and the report numbers you ask for. With theadwordspermission, the Google Ads accounts you can see and their performance reports, such as campaigns, cost and conversions. We only read. Nexa never creates, changes or deletes anything in your Google accounts. - How we use it: only to answer the questions you and your teammates ask, and to show the reports and dashboards your organisation builds. Your organisation’s roles decide who sees what.
- Who receives it: the people in your organisation you allow, and the AI tool you connect, which receives the numbers needed to answer each question. To help you set up your definitions, Nexa may send account, property and field names, never report numbers, to an AI model through OpenRouter, using only providers that don’t keep or train on what they receive. We don’t read your Google data ourselves unless you ask us to for support, it’s needed to keep Nexa secure, or the law requires it.
- How we store it: we keep the account, property and field names we find so your definitions keep working. Report answers are kept for up to two hours so repeat questions don’t go back to Google, then they expire. Your Google access token is kept apart from the rest of your data, and only the Nexa server can read it.
- Removing it: when you disconnect a source in Nexa, we revoke our access with Google and delete its token and saved report answers. You can also remove Nexa’s access at any time from your Google Account permissions.
- What we never do: sell Google data, use it for advertising, or use it to train AI models, ours or anyone else’s.
Nexa’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who we share it with
Only the service providers that help us run Nexa. Inside your organisation, Viewers only see what is shared with them.
| Provider | What for | Where |
|---|---|---|
| Google Cloud | Our servers and database | Mumbai, India |
| Sign-in with Google, and the Google data sources you connect (GA4, Google Ads) | Google’s data centres | |
| Razorpay | Payments | India |
| Resend | Sending account and notification emails | United States |
| Langfuse | Monitoring of requests to the Nexa MCP server | Outside India |
| OpenRouter | Setup help from AI models that don’t keep or train on what they receive (names only, never report numbers) | United States |
Your data is stored in India. Resend, Langfuse and OpenRouter process only the parts they need, outside India, under their own security and privacy terms.
How long we keep it
While your organisation is active. When a trial ends without a plan, or a paid plan ends, we keep your workspace for at least 30 days so you can pick up where you left off. We email your Admins 7 days before we delete it. Then we delete the workspace, its definitions, dashboards and connected-source tokens. Report answers from Google expire after two hours. Invoices are kept as long as Indian tax law requires.
Your rights
You can see, correct, export or delete your data. For any of these, write to us through the contact form or at privacy@nexloid.com, and we’ll reply within 30 days.
Grievance officer
If you have a complaint about how we handle your data, contact our grievance officer: Sudeep Penugonda, privacy@nexloid.com, No. 44, 4th Main, 2nd Block, Sir M V Nagar, Ramamurthy Nagar, Bengaluru 560016, Karnataka, India.
Security
Data is encrypted in transit with HTTPS. It is stored on Google Cloud servers in Mumbai, India, whose disks are encrypted at rest. Tokens for connected sources are kept apart from the rest of your data and only the Nexa server can read them. You can disconnect any source at any time.
Contact
Rayudu Sai Lekha, trading as Nexloid, No. 44, 4th Main, 2nd Block, Sir M V Nagar, Ramamurthy Nagar, Bengaluru 560016, Karnataka, India. privacy@nexloid.com, or use the contact form.