1. Who we are
StrideAX.AI Private Limited (CIN U62099KA2026PTC226254), registered office No. D 202, The Coach, Neeladri Road, Electronics City Phase-1, Bangalore 560100, Karnataka, India, is the Data Fiduciary responsible for the personal data described in this notice.
This policy covers the StrideAX website and the StrideAX platform — ServiceHub, IntegrationHub and the services delivered through them.
2. What we collect, and why
| What | Why we hold it |
|---|---|
| Account details — name, work email, organisation, role | To create and operate your account, apply your access rights, and contact you about the service |
| Enquiry details — name, work email, organisation, job title, and anything you write to us | To answer you. This includes details you submit through a form on a social platform such as a LinkedIn lead form |
| Content you submit — documents, spreadsheets and records processed by a workflow you run | To perform the work you asked for. We process this on your instruction; we do not mine it for any purpose of our own |
| Connection credentials — for a cloud drive, object store or ERP you choose to connect | To fetch the files a run needs, at the moment it needs them. See section 4 |
| Operational records — sign-in events, workflow runs, the audit trail of each run, error reports | To keep the service secure, to bill accurately, and to give you a reviewable record of what ran |
We do not buy personal data, and we do not sell or rent it to anyone.
3. Where your data is held
- Hosted on Google Cloud Platform, which operates regions worldwide.
- Encrypted at rest with AES-256, with additional application-level encryption for stored credentials.
- Encrypted in transit with TLS 1.2 or higher on every connection.
- Backed up daily with point-in-time recovery, on a regional configuration with multi-zone failover.
- Isolated per organisation: every query is scoped to the requesting group in the data-access layer, so one organisation's records are not reachable by another.
4. Connections to your own systems
Where you connect a cloud drive, object store or ERP, the platform reads from it only when a run you started needs a file. Every such connection is outbound and opt-in: we never require inbound access into your network, and nothing is polled or crawled in the background.
Sources are read, not written to — with one exception you control: Google Drive is also used to deliver generated reports into a folder you nominate.
Credentials are held under a two-level encryption envelope, with the master key kept outside the database and outside source code. A one-time credential supplied only to fetch a single file is used and discarded, not stored, unless you choose to save the connection.
5. Who else processes it
These are our sub-processors. The list is exhaustive, and this page changes when it does.
| Who | What for |
|---|---|
| Google Cloud Platform | Hosting, database, storage and backups |
| Google Vertex AI | Optical character recognition, for scanned documents only |
| Sentry | Error reporting, so faults are diagnosed and fixed |
If you reach us through a form hosted on a social platform, that platform is the controller of the data you enter there under its own privacy policy, and passes it to us as described in section 2.
6. AI processing
- Your data is not used to train any AI model — not ours, and not a third party's. This is a contractual commitment under the enterprise terms of the AI service we use, and a commitment we make to you in turn.
- Spreadsheet and export formats are read entirely within our own infrastructure. Excel, CSV, HTML and system exports are parsed by deterministic code, with no AI model involved.
- Scanned PDFs and images are sent to Google Vertex AI for optical character recognition, and for nothing else. If you submit no scanned document, no document content leaves our infrastructure.
- Whether an AI agent is involved at all is your configuration. Each step of a workflow runs deterministic or agentic, decided by you per step. Where a step is agentic, the run record shows which tools the agent actually called.
7. Cookies and browser storage
This site sets no advertising or analytics cookies, and no third-party tracker runs on it. We use your browser's own storage only to keep you signed in, remember your theme preference, and cache public page content so the site loads quickly.
Clearing site data in your browser removes all of it, and signs you out.
8. How long we keep it
- Audit trail: 24 months.
- Account and workflow data: for as long as your subscription is active, and for a reasonable period after it ends so that records can be closed out and legal obligations met.
- Enquiry data: until we have answered you and a reasonable follow-up period has passed, unless you become a customer.
- Data you submit to a run: retained with that run, and removed when you delete the run or your account.
You can export your data in open formats at any time, at no charge, including on exit.
9. Your rights
Under the Digital Personal Data Protection Act, 2023, you may ask us to:
- tell you what personal data of yours we hold and who we have shared it with;
- correct or complete anything inaccurate;
- erase personal data we no longer have a lawful reason to keep;
- withdraw a consent you previously gave, at any time — this does not undo processing already carried out on that consent;
- nominate another person to exercise these rights on your behalf in the event of death or incapacity.
Write to us at the address in section 10. We will respond within a reasonable period. If you are not satisfied with how we have handled your request, you may complain to the Data Protection Board of India.
10. Contact and grievances
For any question about this notice, or to exercise a right in section 9, write to Support@StrideAX.ai. Please mark the subject line Privacy so it reaches the right person quickly.
StrideAX.AI Private Limited
No. D 202, The Coach, Neeladri Road,
Electronics City Phase-1
Bangalore 560100, Karnataka, India
11. Changes to this notice
When this notice changes in substance, the effective date at the top moves and the new version replaces this one on this page. We do not change it quietly — if a change affects how your data is used, we will tell account holders directly rather than relying on you to re-read it.