Privacy Policy

1. User Ownership

Your data belongs to you. PALION does not claim ownership of your conversations, memories, notes, files, preferences or identity information. This policy describes the information used by available features and the limits of current data controls.

2. Identity and Continuity

PALION stores account identifiers, email, display names, preferences, linked-account information and sign-in/session records. Linked services may provide profile images or other account details.

Conversation history, remembered facts, tasks, reminders and work context help you continue across interactions and signed-in devices. Relevant earlier information can be selected automatically for a new request. Information you provide may be retained even when you have not explicitly asked PALION to remember it.

3. No Surveillance: Device Permissions

Device and sensor features depend on enabled settings, browser or operating-system permissions and, where needed, an authorised PALION Driver. Voice listening, camera recognition and location tracking can continue while the relevant mode is enabled; they are not necessarily limited to one request.

Device information can include identifiers, names, device type, operating system, available features and online status. Enabled features may send application/window information, screenshots and action results to PALION. Location features can store coordinates, accuracy, update times and saved places, and use them in reminders, maps or research queries. Saved screenshots or captures may be retained.

4. Local vs Cloud Operations

PALION stores account, conversation, memory and operational information on the server used by your service. That server may be local or hosted. Using PALION in a browser does not mean information stays on your device.

Configured Gemini or OpenAI models can receive your request, relevant history and memory, account/device context and selected attachments. Search providers receive queries; speech and connected services receive information needed for their features. Providers handle information under their own data practices. Do not assume all providers have the same retention or model-training settings.

Research queries, retrieved material and source information may be retained with your work.

5. Files and Connected Services

AVAULT stores uploaded or generated files, names, file types and related summaries or source details. Selected content, extracts and images may be used in conversation or sent to a provider.

Connected calendars and email use account tokens and relevant events, messages, recipients or drafts. Connected information may be synchronised and retained. Supported Apple features can receive contacts or health metrics, and medication reminders can contain health information. Enable only the features agreed for your pilot and avoid unnecessary sensitive information.

Discord and enabled notification channels can receive the content needed to deliver an interaction or notification.

6. Microphone, Voice and Camera

Voice input may use your browser's speech recognition service. When the audio-recording fallback is used, captured audio is sent to PALION and OpenAI for transcription. Transcripts may enter conversation history. Spoken responses use the configured speech service or your browser.

Enabled voice or face enrollment can store matching data, sample text, device details and optional images. Face checks can also retain snapshots and match results. Dismissing a snapshot does not delete it.

Camera features can relay frames through PALION for authorised viewing. Saved snapshots are separate from live camera display. Face and voice matches do not sign in another account or grant access to other people's private information or devices.

7. Payment Information

PayPal handles subscription payment approval. PALION stores subscription identifiers, plan and status information, payer email, account association and payment-status information received from PayPal. See the Terms of Service for billing information.

8. Diagnostics and Support

PALION records usage, action status and timing, errors, sign-in/security events and support information. Diagnostic records may include identifiers, request text, links or action results. Failed service checks can automatically send limited status information through the configured support channel.

Support access is limited to the information permitted for the support task. A support role does not automatically include access to private conversations, memories, files or biometric material. Operational reports can still include account identifiers; they should not be assumed to be fully anonymous.

9. Guest Sessions and Browser Storage

Guest use has a session identifier. Requests and conversations can still be stored and processed by providers. Guest use does not mean no data is retained. Moving guest conversation context into an account requires an explicit request.

Browser cookies, local/session storage and caches can hold sign-in state, preferences, device identifiers and display state. Signing out or switching accounts does not erase server records or backups.

10. Data Controls and Their Limits

Available controls include editing account settings, unlinking supported identity providers, removing selected conversation entries or learned facts, downloading or deleting individual AVAULT files, deleting your face enrollment and disconnecting supported calendars.

PALION does not currently offer a complete self-service account export or full-account erasure. Removing a selected item does not necessarily remove related memories, other records, backups or copies held by providers. Account removal should not be treated as complete erasure.

There is no complete user-configurable retention schedule. Records and provider copies can remain beyond an individual interaction or deletion. Use the privacy contact supplied with your invitation to ask what information can currently be accessed, corrected, exported or removed.