Privacy Policy
Effective 7 August 2026
What PilotWorks4u collects, why, who else sees it, and how to make us delete it. This covers pilotworks4u.com and the products run from it — DevPilot, SEOPilot and OpsPilot.
PilotWorks4u runs pilotworks4u.com and the products described here, and is responsible for the data in this policy — it is the one holding it. For anything in this policy, including a request to see or delete what we hold about you, write to hello@pilotworks4u.com.
Two things are worth saying before the detail, because they are the parts people actually care about and the parts a policy usually buries:
- Our products hold the keys to your website. DevPilot stores the credential that lets it change your live site. What that means, and what protects it, is in section 3.
- Your content is sent to an AI provider. To do the work you ask for, page content and site data are sent to a third-party AI model. Which one, and what they may do with it, is in section 5.
1. Who this policy is for
- Customers — people and businesses with a PilotWorks4u account.
- Visitors — anyone browsing pilotworks4u.com.
If you are a visitor to a website that our customer runs, we are not the controller of your data; that customer is. We process it on their behalf.
2. What we collect
From you, because you gave it to us
| What | Why |
|---|---|
| Name, email address, workspace name | To create and run your account |
| Password | Stored only as a hash — we cannot read it, and neither can anyone who takes a copy of the database |
| Payment reference, transaction ID, payment screenshot | To confirm a payment and activate a plan |
| What you type into the product | It is the instruction. We cannot do the work without reading it |
| Files you attach — documents, spreadsheets, images | Same reason |
From your website, because you connected it
| What | Why |
|---|---|
| Pages, posts, media, menus, plugin and theme names | To know what is there before changing it |
| Site settings, SEO fields, form definitions | To change the right thing |
| The credentials to reach it — see section 3 | Without them nothing can be read or changed |
| Snapshots taken before every change | So a change can be undone |
Automatically
| What | Why |
|---|---|
| IP address, browser, pages visited, timestamps | Security, abuse prevention, and knowing what is used |
| An audit trail — who did what, and when | So an unexpected change to a live site can always be traced to a person |
| Session cookie | To keep you signed in. It is not used for advertising |
| Google Analytics cookies — _ga and _ga_F81C4QRRTK | To count visits to pilotworks4u.com and see which pages get read. They last up to two years and are set on every visit, including your first one |
Analytics. We use Google Analytics 4 on pilotworks4u.com. It sets the two cookies above and sends Google your IP address, the pages you view, and basic device and referrer information. We use it to understand how many people arrive and what they read — nothing more. Google processes that data as our analytics provider and also under its own terms for sites that use its services.
You can stop it. Install Google’s opt-out add-on or block the cookies in your browser — nothing on pilotworks4u.com stops working if you do.
Beyond that, we run no advertising or retargeting pixels on pilotworks4u.com, we do not serve advertising anywhere, and we do not sell, rent or trade personal data to anyone, ever.
3. Your website credentials
This is the most sensitive thing we hold, so it gets its own section.
What we store.For a WordPress site: the address of the site and an application password issued by its administrator, or a connector pairing secret. For a Shopify store: an access token issued through Shopify’s own OAuth flow. For Google: an OAuth refresh token — see section 4.
What it lets us do.Exactly what you have granted, and no more. On WordPress that can include editing pages, theme files and plugins, because that is what “change my site” requires. Our products can therefore make changes that are hard to reverse, which is why every change is snapshotted first and can be rolled back.
How it is protected. Credentials are stored encrypted, are never displayed back to you or to anyone else after they are saved, are never written into a support ticket or a log, and are never sent to an AI provider. They are used by our server and by nothing else.
How to revoke it. You can disconnect a site at any time from the product. You can also revoke access from your own side — delete the application password in WordPress, uninstall the app in Shopify, or remove access in your Google Account. Doing so stops us immediately and does not require our cooperation. That is deliberate.
One honest limitation. Anyone with administrator access to the machine our software runs on could read what that machine can read. We keep that circle as small as we can and we will tell you without delay if we ever believe it has been breached.
4. Google user data
SEOPilot connects to Google Search Console and Google Analytics 4 when you choose to connect them.
What we ask for. Read-only access to your Search Console properties and Analytics properties — the performance, indexing and traffic data for the sites you select. We request the narrowest scopes that let the product work.
What we do with it. We use it for one purpose: to produce the SEO analysis, reporting and recommendations you asked for, inside your own account. Nothing else.
PilotWorks4u’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Specifically, and to state the Limited Use terms plainly:
- We do not use Google user data for advertising, and we do not serve advertising at all.
- We do not sell, rent or transfer Google user data to third parties, and we do not use it to build any profile or dataset beyond serving you.
- Humans do not read your Google user data, except: with your explicit permission while helping you with a support request; where it is necessary for security purposes such as investigating abuse; or where we are required to by law.
- We do not use Google user data to train, fine-tune or improve any generalised AI or machine-learning model. Where an AI model is used to produce your report, the data is sent for that single request and is not retained by us or by the provider for training — see section 5.
How long we keep it. Only as long as your Google account stays connected. Disconnect it, or revoke access at myaccount.google.com/permissions, and the stored token is deleted and the data derived from it is removed within 30 days.
5. AI providers
Our products work by sending your instruction, and the relevant parts of your site’s content, to a large language model. There is no version of this product that does not do that, so it is stated plainly rather than in a footnote.
Who.Anthropic (Claude) is the default provider. You may configure a different provider in your workspace settings, in which case that provider’s terms apply instead and this section describes them, not us.
What is sent. Your instruction, the page or file content needed to carry it out, and the facts stored about your site. Notsent: your password, your website credentials, your payment details, or any other customer’s data.
What is not sent. We do not send data to an AI provider for the purpose of training their models, and we use these providers under terms that do not permit customer inputs to be used for model training.
One risk you should know about. Our products can be asked to read a public web page and act on what it says. If someone can publish text on a site you have connected — an open comment form, a review widget — text they write is text the model reads. Keep untrusted publishing switched off on a connected site.
6. Who else sees your data
We use these companies to run the service. Each sees only what its job requires.
| Sub-processor | What it does | What it sees |
|---|---|---|
| Amazon Web Services | Hosts the application server | Everything the application holds |
| Supabase | Hosts the database | Account data, site data, snapshots |
| Vercel | Hosts this website | IP addresses, request metadata, anything you send a form |
| Cloudflare | Routes traffic to the application | IP addresses, request metadata |
| Anthropic | The AI model that does the work | Instructions and site content — see section 5 |
| Google Analytics | Measures traffic to this website | IP address, pages viewed, device and referrer — see section 2 |
| Search Console and Analytics, when you connect them | See section 4 |
We will update this table when it changes. We do not sell data to anyone, and no one in this table is permitted to use your data for their own purposes. We may also disclose data if the law requires it — and if we are legally allowed to tell you first, we will.
7. How long we keep things
| What | How long |
|---|---|
| Account and workspace data | While your account is open, then 90 days |
| Site content and scans | While the site is connected, then 90 days |
| Snapshots taken before a change | 90 days, so a change stays reversible |
| Google user data | Until you disconnect, then deleted within 30 days |
| Audit trail — who changed what | 12 months. It is the record of who touched a live site, and shortening it would defeat the point |
| Payment records | As long as Indian tax and accounting law requires |
8. What you can ask us to do
Write to hello@pilotworks4u.com and we will answer within 30 days:
- See it — a copy of what we hold about you.
- Correct it — fix anything wrong.
- Delete it — we delete your account and its data, except records the law requires us to keep. This is not reversible.
- Take it elsewhere — your data in a machine-readable file.
- Withdraw a permission — disconnect a site or a Google account, at any time.
We do not charge for any of this. We may ask you to confirm who you are first, because handing someone else’s data to the wrong person is the failure this whole policy exists to prevent.
9. Security
Passwords are hashed. Credentials are encrypted at rest. Traffic is encrypted in transit. Access to production systems is limited to people who need it. Every change to a customer site is logged with the person who caused it, and snapshotted so it can be undone.
No system is perfectly secure and we will not pretend otherwise. If we discover a breach affecting your data, we will tell you and the relevant authority without undue delay, and we will tell you what actually happened rather than a sanitised version of it.
10. Children
Our products are for businesses. They are not intended for anyone under 18, and we do not knowingly collect data from children. If you believe a child has given us data, write to us and we will delete it.
11. Where your data is
Our application servers are in India. Some sub-processors in section 6 process data outside India. Where that happens, we rely on their contractual protections and use only providers who commit to appropriate safeguards.
12. Changes to this policy
If we change something that materially affects you, we will email you and update the date at the top before it takes effect. Continuing to use the service after that means you accept the change.
13. Governing law
This policy is governed by the laws of India. Any dispute is subject to the exclusive jurisdiction of the courts at Jaunpur, India.