This page describes how Pxie (“we”, “us”) handles data for customers of the Pxie API and MCP server. It supplements our Terms of Use and Privacy Policy. Customers who need a signed data processing agreement can request one at hello@pxie.ai.
1. Roles
- Account and billing data (your email, plan, usage records): Pxie decides why and how this is used, and acts as the responsible organization for it. See the Privacy Policy.
- Customer-supplied data (for example substation and line details, field boundaries and coordinates you send, and alert email or webhook addresses): Pxie processes it on your behalf and on your instructions to provide the Service.
2. What we process for you
| Feature | Data | Purpose |
|---|---|---|
| Any API or MCP call | Request parameters (such as coordinates and dates), your key identifier, response status, credits used | Return the result, apply rate limits, bill credits |
| Grid alerts | Substation names and locations, transmission lines, alert levels, alert email addresses and webhook addresses | Calculate risk and send the alerts you configure |
| Soil and agriculture | Point or field boundaries you send | Calculate the response; results may be cached to speed up repeat requests |
| Account | Email, plan, API key hashes, optional IP allowlist | Authenticate and bill |
| Account security | The five most recent different IP addresses used with your account | Protect the account and detect abuse |
We do not sell your customer-supplied data and we do not use it to train models. API keys are stored only as one-way hashes.
3. Service providers (sub-processors)
| Provider | Service | Processing location |
|---|---|---|
| Cloudflare, Inc. | Edge gateway, website hosting, database (D1), object storage (R2), key-value cache, spam protection (Turnstile), inbound email routing | Global network; database and storage in North America |
| Google LLC (Google Cloud) | API processing (Cloud Run); secret storage | API processing in Montréal, Canada; secret storage is managed by Google and its location is set automatically |
| Clerk, Inc. | Sign-in and user accounts | United States |
| Stripe, Inc. | Payments, subscriptions and invoices | United States and Canada |
| Resend | Sending email: account messages, alerts, contact form delivery | United States |
We will update this list before adding a new sub-processor that handles customer data and will notify customers with an active agreement by email.
4. Retention and deletion
- Usage records (account, key, endpoint, credits, status, time) are deleted after 2 years.
- The five most recent IP addresses of an account are replaced as newer ones appear. After you close your account they are kept for 180 days and then deleted, unless a legal obligation or a legal claim requires us to keep them longer.
- When you close your account, we revoke your API keys and alert subscriptions straight away and wipe personal details; the account shell is deleted after 30 days. We also ask Stripe to delete the customer record, retrying if needed.
- Grid substations, lines and alert subscriptions are removed with your account, and you can remove them yourself at any time.
- Nightly backups of the account database are deleted after 35 days. Until then a backup can still contain details of accounts that have since been closed, including their recent IP addresses. Access to backups is restricted to authorized Pxie personnel.
- On request we will return or delete your customer-supplied data when your agreement ends, unless the law requires us to keep it.
5. Security
Our security measures are described on the Security page. Access to production systems is limited to authorized Pxie personnel.
6. Requests and incidents
If someone asks us about your data (for example an access or deletion request), we will pass it to you and help you answer where the request concerns customer-supplied data. If we learn of a breach affecting your data, we will tell you without undue delay and give you the information you need to meet your own obligations.
7. International transfers
Our providers may process data in Canada, the United States and other countries. Where required, transfers rely on the safeguards offered by those providers, such as standard contractual clauses.
8. Contact
Privacy Officer, Pxie · hello@pxie.ai · Edmonton, Alberta, Canada T5T 6Z8