Privacy Center

Percia is the umbrella brand operated by VELVEE, INC. (“Percia,” “we,” “us,” or “our”). The Percia product family includes Percept Vision and the Percia Assistant. This neutral privacy center explains the principles shared across Percia products and provides product-specific disclosures.

Product disclosures

The detailed disclosure below currently applies to the Percia Assistant, including its iPhone and Mac applications and supporting cloud services. Percept Vision and other Percia products may provide additional product-specific notices at collection points or through this privacy center. If a product-specific notice differs from this general notice, the product-specific notice controls for that product.

Percia Assistant privacy notice

This beta is intended for adults. It is not directed to children under 13.

Information we handle

Account and authentication

When you sign in with Google, we receive the account identifiers needed to authenticate you, such as your Google account email address, display name, and a stable account identifier. Authentication is provided through Google Sign-In and Firebase Authentication. Percia does not receive your Google password.

Conversations and assistant context

Percia processes the text you type and transcripts created when you use voice input. To answer a request, the app sends your prompt, its system instructions, and a bounded amount of relevant assistant context to Percia Cloud, which uses Google Cloud Vertex AI to generate a response. This context can include preferences, tasks, commitments, and—only after you separately connect Google data—limited Calendar and Google Tasks information described below.

Conversation history may be stored locally on your device when Retain conversation history is enabled and Incognito Mode is off. Local application state is written using Apple's complete file-protection option. Percia's current beta generation service does not intentionally write prompt or response bodies to Percia's application database. Infrastructure providers may process request and operational metadata to run, secure, and troubleshoot their services.

Voice and audio

The microphone is activated only after you explicitly start a foreground voice turn. During that turn, the app streams microphone audio to Google Gemini Live through a Percia-authenticated, short-lived session. Gemini Live produces the input transcript and returns response audio using the single configured Aoede voice. App-authored spoken text, including the introductory greeting, is also rendered by Gemini Live using Aoede. The current beta does not use Apple speech recognition or Apple system text-to-speech.

Percia does not intentionally persist raw voice-input audio, Gemini Live response audio, ambient audio, private check phrases, or raw approval audio. Conversation transcripts may be retained under the conversation-history choices described above. Leaving the foreground or changing audio routes stops the Live session; Percia does not substitute another speech provider when Gemini Live is unavailable. Google may process transient audio, transcripts, and operational metadata to provide and secure Gemini Live under its applicable terms.

Optional Google data

Google identity sign-in is separate from optional Google data access. When you select Connect Google data, Percia requests the scopes needed for the beta capabilities you choose:

• Google Calendar, to read upcoming events and to create or edit an event only after you approve its exact fields;
• Google Tasks, to read tasks and to create or edit a task only after exact review;
• Gmail, to search message metadata, create drafts, and send a selected draft only after exact review and confirmation;
• Google Drive, to search and read a file you explicitly identify; and
• Google Contacts, to look up contact details for an explicit query.

The current beta holds fetched Google provider results in app memory and excludes them from its local application-state file. After relaunch, Percia rechecks live provider access instead of treating cached connection status as proof of access. The native Google refresh grant remains in Google Sign-In's platform storage and is not uploaded to Percia Cloud.

When you ask Percia for general conversational help, a bounded subset of Calendar event titles, times, and locations and Google Task titles and due dates may be sent through Percia Cloud to Google Vertex AI solely to generate the response you requested. Gmail, Drive, Contacts, Places, Routes, and Google write commands use explicit provider routes rather than being represented as completed by the language model.

Percia does not use Google user data for advertising, surveillance, credit decisions, or to train generalized AI models. Percia's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Maps, webpages, memory, and Percept watches

For an explicit place search or travel-time request, Percia sends the query or origin and destination through its authenticated backend to Google Places or Google Routes. The restricted Maps credential is not stored in the app.

For an explicit browse https://… request, Percia sends the public HTTPS URL to its isolated browser service. The service returns bounded webpage evidence that the app labels and treats as untrusted content. Percia does not use this path for signed-in sites, credentials, checkout, or CAPTCHA or human-verification bypass.

Memory claims are created only from an explicit save and are stored with account ownership, source, kind, and timestamps. Percept watches are created only after exact review and confirmation; Percia stores the authenticated mapping to the Percept provider and retrieves structured provider events. Production memory, watch mappings, and relevant payloads are encrypted at rest. Incognito Mode blocks durable memory and watch creation.

Notifications and device information

If you enable notifications, Percia receives an Apple Push Notification service (APNs) device token along with the device platform, app identifier, and development or production environment. Percia binds that token to your authenticated Firebase account. In production, the raw token is encrypted in Percia's database; a token fingerprint, account identifier, and device metadata are also stored to route and manage notifications. Reminder text is encrypted in Percia's database; the APNs payload uses generic reminder copy and a random job identifier so the exact reminder is retrieved only after authenticated app access. Apple receives the device token and notification payload when Percia sends a notification. Notification previews may appear on a locked screen according to your Apple notification settings. APNs acceptance does not prove that a notification was displayed or viewed.

Operational and support information

Our hosting and security providers may process IP addresses, request timestamps, route names, response status, device or app version, crash information, and similar operational data needed to deliver, secure, and diagnose the service. If you contact us by email or Discord, we process the content and contact information you choose to provide.

Percia watches

Percia watches are monitors you create at percia.ai or through the Percia API. A watch checks a video source you point it at and notifies you when what you described happens. This section covers watches, the percia.ai waitlist and signing in to percia.ai; it is separate from the Percia Assistant notice above.

What a watch stores

To create a watch you provide a goal in plain language, the address of a video source, and how you want to be notified (by email or by a webhook, and optionally also in Slack or another tool you connect, see Alert destinations below). We store the watch and the events it produces. An event is text only: when it happened, the type, a confidence score, a short description written by the model, and whether the notification was delivered. We do not store video. When evidence is on for a watch (the default for watches you create in the app; off for watches created from the landing page, the API or MCP), we keep the keyframe the model looked at for each event, so you can check it. To judge a watch we send a few sampled frames per second to Google's Gemini API (a paid service), which does not use them to train its models but may keep them for up to 55 days to detect abuse. For webhook watches we also store a signing secret, which we show you once and never show again.

Video source addresses can carry credentials. We seal them when they are handed to the machines that run your watch, use them only to run it, and never show the credentials back to you or in our logs. The address is also kept in our database for as long as the watch exists, so the watch can run.

Keyframes, phone cameras and site memory

Keyframes are encrypted with a key specific to your account and deleted automatically after the retention period: 3 days by default for places in the EU, EEA, UK or Switzerland, 7 days elsewhere, and 1 to 30 days if you change it. When you mark an event as correct or a false alarm, its keyframe is kept as a test case until you delete it, and is used only to test your own agents. Email alerts link to the event in the app and never attach images. We do not use your video, frames or keyframes to train models.

If you use a phone or laptop as a camera, its video goes from the device to our media server and on to the machine running your watch; it is not recorded. If you group watches in a site, we keep a short written memory of what was observed there (for example, that a package has been on the step since 14:02) so your watches and your questions can use it; you can edit or clear it at any time.

Who processes watch data

Google (Gemini API): sampled frames and keyframes for judging, test runs and descriptions; site memory and questions you ask. Cloudflare: hosting, database and encrypted keyframe storage. OVH: the machines that run watches and the media server for phone cameras (video passes through, not stored). Our email provider: alert emails (text and a link only). Slack, and any other tool you connect: the alert you chose to send there (see Alert destinations). PostHog: product analytics, never frames, goals or camera addresses.

Alert destinations

You can connect tools so a watch also posts there when its goal is met: Slack, Home Assistant, or a webhook you run (Discord and Telegram are planned). You approve each destination yourself in your signed-in account; an AI app cannot add one for you. With Slack you pick one channel and Slack gives us an address that can only post to that channel; the access token Slack sends back is discarded and only that posting address is kept, so we cannot read your messages or any other channel. For every destination we store its address, encrypted, only to deliver your alerts, and never show it back to you.

Each alert contains the watch goal, the model-written reason, the time, a link to the event in Percia and, when the watch keeps keyframes, a link to the keyframe. That link does not expire by itself: it works until the keyframe is deleted (see the retention table above), and anyone who has the message or the link can open the image, so keep the destination channel private. That message leaves Percia and is then held by the tool you chose, under its own terms; for example Slack may keep or copy the image. We record whether each delivery worked (status, number of attempts, an error code) but not the message text, and we retry a failing delivery for up to 2 hours. Disconnecting a destination removes it and its rules.

AI apps and API access

You can let an AI app, such as Claude, or your own software act on your Percia account, through an API key or by signing in to the app with Percia. You choose what it may do on Percia’s consent screen (see watches, create and change watches, read events and images, manage cameras, see connected tools, and, off unless you turn it on, delete). What the app reads is sent to that app and its provider and handled under their terms. We keep the app’s name, its permissions and when it was last used, and you can revoke it at any time under Settings, API keys. For product analytics we count tool calls by operation name, result and time, and the app’s name, never what was read or written.

Your own Gemini key

You can add your own Google Gemini key so that judging and Percia’s model features run on your Google account. We keep it encrypted, show only its last four characters, use it only for your own requests, and delete it when you remove it.

Percia Camera app

The iPhone app turns a phone into a camera for your watches. On the phone it keeps only the camera’s access token (in the system’s secure storage) and a random install number. Video goes to Percia only while the app shows “Percia is watching”; audio is never recorded. To improve the app it sends anonymous usage events (for example, that streaming started or a reconnect happened) to PostHog, identified only by the random install number, never by your account, camera, location or IP address. To deliver app updates it checks Expo’s update service, which receives a random identifier, the app version and the platform.

Signing in and the waitlist

If you sign in with Google, GitHub or Apple, we receive your name and email address (with Apple, possibly a private relay address) and nothing else from that account. Sign-ins with the same email address use one account. If you join the waitlist we store your email address, the optional use case you type, and the time you signed up. We use the waitlist only to invite people to the research preview and send no marketing to anyone who has not asked.

Limits and measurement

Our forms and sign-in are protected by rate limits, and sign-in also uses a bot check (Cloudflare Turnstile), which process your IP address and browser details to tell people from automated traffic. We count product events, such as that a watch was created or someone joined the waitlist, with PostHog. These counts do not include email addresses, camera addresses or the text you type.

Deleting watches and data

You can delete a watch at any time; this removes its settings, its events and its job on our machines. We do not yet delete events automatically, so they are kept until you delete the watch. To remove your waitlist entry or any other account data, email beta@percia.ai from the address you used.

How we use information

We use information only to authenticate you and operate the app; provide requested assistant, connected-data, and notification features; preserve local preferences and history you choose to retain; protect and diagnose the service; meet legal obligations; and respond to support, privacy, and feedback requests.

Percia does not sell personal information, serve behavioral advertising, or track you across other companies' apps and websites.

Service providers and disclosure

We use Apple services for application distribution, device audio, and push notifications, and Google services for authentication, optional Google Workspace and Maps access, Firebase, Google Cloud hosting, Vertex AI, and Gemini Live Aoede voice. We also use an isolated browser service and Percept provider when you explicitly invoke those features. These providers process information on our behalf or at your direction under their terms and privacy commitments. We may also disclose information when required by law, to protect users or the service, or as part of a corporate transaction subject to appropriate safeguards. We do not allow service providers to use Percia data for their own advertising.

Retention and deletion

Local application data remains until you delete it in Settings → Privacy and retention, disable the applicable retention option, sign out where relevant, or uninstall the app. Disabling future conversation retention does not by itself erase history already saved; use Delete local data to remove the local application-state file.

Google OAuth credentials are managed on-device by Google Sign-In. Signing out clears Percia's local Google session and in-memory provider snapshot but does not revoke Percia's authorization at Google. Delete Percia account initiates deletion of the Firebase account and Percia-owned notification, reminder, memory, and Percept-watch mapping records and revokes the connected Google grant. You can also revoke access from your Google Account's third-party access settings.

Server-side notification records are retained while needed to provide notifications and may remain as inactive security records after Apple invalidates a token. You may ask us to delete server-side records associated with your beta account. We retain limited records when reasonably necessary for security, fraud prevention, dispute resolution, or legal compliance.

To request access, correction, or deletion of account-associated data, email beta@percia.ai from the email address linked to your account. We may need to verify your identity before completing the request.

Security

Percia uses HTTPS in transit, authenticated service boundaries, encryption for sensitive production records, Apple file protection for local state, and least-privilege provider permissions. No system is perfectly secure, and we cannot guarantee absolute security.

Your choices

• Decline microphone, Google-data, or notification permissions.
• Use text instead of voice.
• Turn conversation retention off or use Incognito Mode.
• Delete local Percia data in the app.
• Sign out of Google and separately revoke Percia in your Google Account.
• Control notification previews or disable notifications in Apple Settings.

International processing

Percia and its providers may process information in the United States and other countries where they operate. Privacy protections may differ from those in your country.

Changes to this policy

We may update this policy as Percia changes. We will update the date above and provide additional notice or request new consent when a change materially affects how connected Google user data is used.

Contact

Privacy, deletion, and beta support: beta@percia.ai
Founder and CEO: divi@percia.ai
Community support: Percia Discord