peiloJoin the early access list
Home / Peilo Privacy

Peilo privacy — Camera, local records, and AI requests

Understand what stays on your device, what optional sync sends, and what happens when you request an AI insight.

AnyoneKit · Updated October 6, 2026 · About us

What happens when you visit this website?

Visiting the Peilo website does not activate your camera or microphone or read work records on your devices.

With your permission, we use Google Analytics to understand which pages people visit and whether they complete a signup. This uses analytics cookies and sends Google information about page visits, devices and browsers, and events such as a successful signup. We do not send your signup email, camera images, or work records from the app to Google Analytics. You can change your choice using “Analytics cookie settings” in the footer. Declining analytics does not affect browsing or signup.

Netlify Forms receives your signup email and optional app preference so AnyoneKit can contact you about opportunities to try Peilo.

How will you use my signup email?

We use your email only to contact you about opportunities to try Peilo. You can optionally tell us whether you are interested in the phone app, desktop app, or both. Joining the list does not subscribe you to unrelated marketing.

Joining the list does not guarantee test access. Invitations will be sent in batches; we do not have a confirmed invitation date.

You can leave the list or request deletion of your signup email at any time. Write to support-peilo@anyonekit.com from the address you used to sign up, with the subject “Leave the Peilo early access list”.

Local processing.

With authorization, the PC app reads available Codex account data and local WorkBuddy records for usage and conversation review; it does not modify the source records. Raw phone camera frames are processed locally without being saved or uploaded. Structured observations and app records may be stored locally. Older data folders may still be named DeskBot.

Optional device connection and history sync.

A paired phone receives PC information you have agreed to share, such as session counts, recorded tokens, and available allowance. Separately enabling history sync transfers recent phone observations and subsequent changes. It does not transfer raw camera frames or audio. Keep pairing credentials private.

External services and AI insights.

Checking Codex allowance may contact its service. Verifying a DeepSeek key checks connectivity and balance without sending work excerpts or automatically generating an insight.

When you request an insight or ask about the week, selected work excerpts and phone records you have agreed to sync may be sent to DeepSeek using your key. The app tries to remove sensitive details, but this may not catch everything. Provider charges may apply. These requests do not send camera frames, audio, or device secrets. Local statistics do not require a cloud key.

The provider’s own policies apply after receipt; keeping records on your device does not prevent a provider from retaining text you send to it.

Control and deletion.

You can skip cloud configuration, delete the saved key, revoke a phone connection, or withdraw camera permission. Revoking a connection does not erase previously saved history. PC may continue in the tray after closing its window; choose Quit to stop it.

For complete local cleanup, quit the app and back up any records you need before removing its DeskBot compatibility data directory. Do not delete original Codex records. Uninstalling the app may leave saved records on your computer.

Read the operating guide

About this page

This notice explains how the Peilo phone app, desktop app, and website handle data. Refer to your version of the app for the available features and settings.

Maintained by AnyoneKit · Updated October 6, 2026

About AnyoneKit and how to contact us