Privacy Policy

1. Scope

This policy explains what data EVE ("we", "us") handles when you use the EVE inventory intelligence platform, why we handle it, and what choices you have. It describes how the product actually works today. Where a capability is not yet enabled, we say so rather than describing an intended future state.

2. Account and authentication data

Sign-in is handled by Supabase Auth, either with Google sign-in or with an email address and password. When you use Google sign-in, Google returns your email address, name and profile image URL to Supabase; we never see your Google password. When you use a password, it is stored and verified by Supabase, not by EVE.

We store a profile record containing your email address, display name, optional avatar URL, timezone and language preference, plan type, and trial dates.

3. Workspace data

EVE organises everything into workspaces. We store the workspace name and identifier, and the membership records that link accounts to workspaces along with their role (owner, admin or member). Every workspace is a separate tenant boundary.

4. Business data you provide or import

EVE analyses inventory data that you upload as a file or import from a connected Shopify store: products and variants, SKUs, sizes and colours, unit cost, selling price, stock levels, lead times, supplier names, and sales history.

If you upload documents such as supplier invoices, the file and the values extracted from it are stored in your workspace. Uploads are limited to 10 MB per file and are subject to a per-workspace storage quota.

5. Connected store credentials

When you connect a Shopify store, Shopify issues EVE an access token. That token is encrypted before it is written to our database, using authenticated encryption with a key derived from a deployment secret held in Google Cloud Secret Manager. EVE requests read-only Shopify permissions (read_products, read_inventory, read_orders) and never writes back to your store. Disconnecting a store removes the stored token.

6. AI processing

EVE uses Google's Gemini API to turn the results of its own calculations into written analysis. The prompts we send can include inventory figures from the workspace you are asking about — for example SKUs, stock levels, costs, prices and sales velocity. We do not send your account password, your Shopify access token, or any other credential to the model.

Google processes this data as our service provider under the Google APIs Terms of Service and the Gemini API terms that apply to paid API usage. We do not control Google's own retention or processing practices; please refer to Google's documentation for those details.

We record metadata about each AI call — the model used, token counts, latency and computed cost — so we can monitor spend and reliability.

7. Recommendations and decision traces

When EVE produces a recommendation, it stores a trace of how that recommendation was reached: the figures used, the reasoning steps, confidence and validation status, the model and model version, and a snapshot of the prompt and response. This exists so you can audit any number EVE shows you. These traces live inside your workspace and are visible only to its members.

8. Messaging channels

Telegram

If you link a Telegram account, EVE stores a salted one-way hash of your Telegram chat identifier, plus the identifier itself in encrypted form so it can send you replies. The text of a message you send is processed to answer your question. Linking uses a single-use, expiring code issued from inside your EVE workspace. You can unlink at any time from the Integrations page.

WhatsApp

WhatsApp support is implemented in EVE but is not currently connected to Meta, so no WhatsApp messages are being received or processed at this time. If that changes, this policy will be updated before the channel is enabled.

9. Usage analytics

On our public website and in the product we use PostHog to understand which pages and features are used. Anonymous visitors do not have a profile created for them. Analytics are disabled entirely when the PostHog key is not configured. We do not send your inventory data to PostHog.

10. Logs and security records

We keep application logs and an audit log of significant events — sign-in events, uploads, integration changes and AI runs — recording the event type, the workspace, the acting account and the originating IP address. These records support debugging, abuse investigation and billing accuracy.

11. Cookies and local storage

EVE uses cookies and browser storage that are necessary for the service: Supabase authentication tokens that keep you signed in, and a local theme preference. Analytics cookies are set by PostHog when analytics is enabled. We do not use advertising cookies and we do not sell personal information.

12. Service providers

The following providers process data on our behalf:

• Google Cloud Platform — application hosting (Cloud Run), file storage, and secret management.
• Google Gemini API — AI analysis, as described above.
• Supabase — authentication and identity.
• Vercel — hosting and delivery of the web interface.
• A managed PostgreSQL provider — the application database.
• PostHog — product analytics.
• Shopify and Telegram — only where you have connected them.

13. Where data is processed

EVE's application servers run in Google Cloud's us-central1 region in the United States. Our other providers may process data in the United States or in other countries. If you are located elsewhere, using EVE involves transferring your data across borders.

14. Retention and deletion

We keep your data for as long as your account is active. We have not yet set fixed retention periods for logs and audit records; when we do, this policy will state them.

You can delete your account from the Settings page. Deletion removes your profile, deletes every workspace that you solely own together with the inventory, sales, document and recommendation data inside it, deletes your uploaded files from storage, and deletes your authentication record. If you share a workspace with another owner, that workspace and its data continue to exist and only your membership is removed. Deletion is not reversible by you or by us through the product.

We cannot guarantee immediate erasure from provider-side infrastructure such as database snapshots or backups held by our hosting providers, which are outside our direct control and expire on their own schedules.

15. Access and export

Your inventory, recommendations and decision traces are visible to you in the product at any time. For a copy of your data, or a question about what we hold, contact us at the address below and we will respond directly.

16. How we protect data

These are the measures actually implemented in EVE today:

• Third-party access tokens are encrypted at rest with authenticated encryption.
• Messaging identifiers are stored as salted one-way hashes.
• Every request is scoped to a workspace in the application layer, and every sensitive endpoint checks authentication, workspace membership and role.
• Incoming webhooks are rejected unless they carry a valid signature or secret — Shopify HMAC, a Telegram secret token, and a Meta signature — and repeated deliveries are de-duplicated.
• Deployment secrets are held in Google Cloud Secret Manager, not in the codebase.
• Traffic to EVE is served over HTTPS by our hosting providers.

To be precise about one point: EVE enforces tenant separation in its application code, not with PostgreSQL row-level security. No system is perfectly secure, and we do not claim to hold any security certification.

17. Children

EVE is a business tool and is not directed at children. We do not knowingly collect data from anyone under 18.

18. Changes to this policy

If we change this policy we will update the date at the top of this page. For changes that materially affect how we handle your data, we will notify account holders by email before the change takes effect.