Privacy at a glance
SenvoAI only needs enough information to provide the features you use. The exact services connected to a particular installation can vary, so the person or organisation operating that installation may also have its own privacy notice.
1. Account information
When accounts are enabled, SenvoAI may store details such as your display name, email address, profile image, sign-in information, preferences and plan or access level. These details are used to sign you in, keep your workspace separate from other users and remember your settings.
2. Chats, projects and memory
Normal chats, project conversations and messages may be stored so you can return to them later. Memory is separate from ordinary chat history and is intended to keep useful longer-term context. Temporary Chat is designed to avoid adding that conversation to normal chat history and to avoid using long-term memory for that session.
3. Files and images
Files you upload may be stored in your Library or attached to a chat, depending on what you choose. When you ask SenvoAI to analyse a file or image, the relevant content is processed to answer your request. Only upload material you are comfortable processing and are allowed to use.
4. Search and external information
When web search or another connected feature is used, the request may be sent to an external service that can provide the needed information. SenvoAI aims to send only what is needed for that feature. Search results and webpages are treated as external content, not as instructions that can override SenvoAI's security rules.
5. Voice and microphone
Voice features require microphone permission. Audio or speech data is processed only when a voice feature is active. Available voices and speech processing can depend on your browser, device and the services enabled for this installation.
6. Location
Location-aware features ask for browser permission when location is actually needed, such as a nearby-place request. A one-off location lookup is not automatically treated as a long-term memory.
7. Device storage and sessions
SenvoAI may use cookies or local browser storage for sign-in sessions, interface settings, drafts and other product state. Browser-stored drafts are intended to help you recover unfinished text on that device.
8. How information is used
Information may be used to provide requested features, keep your account secure, preserve chats and preferences, improve reliability, prevent abuse and diagnose product errors. SenvoAI should not expose another user's private workspace simply because a model or browser asks for it.
9. Retention and deletion
Deleting a chat removes it from the normal workspace according to the installation's deletion behaviour. Archiving is different: it hides a chat without deleting it. Files, projects, memories or other items can have separate controls and may need to be removed separately.
10. Your choices
- Use Temporary Chat when you do not want a conversation added to normal history.
- Review and change personalization or memory options that are available to your account.
- Remove chats, files or projects you no longer want to keep.
- Decline optional browser permissions such as microphone or location access.
11. Security
SenvoAI uses account checks and server-side permission controls to separate user workspaces. No online or local service can promise perfect security, so keep your sign-in details private and report unexpected account activity.
12. Changes to this notice
This notice may change as SenvoAI adds or removes features. The updated date at the top shows the version of the notice currently presented by this installation.
13. Sign-in providers
If you choose Google, GitHub or another supported sign-in provider, that provider handles its own login page and sends SenvoAI the account information needed to identify or create your SenvoAI account. SenvoAI should never ask you to paste a Google or GitHub password into a chat.
14. AI and media providers
AI chat, image understanding, image generation or video generation can use connected external providers. The text, image or media prompt needed for the request may be sent to the selected provider. Provider availability, retention and processing practices are governed by that provider as well as any settings chosen by the SenvoAI operator.
15. Scheduled tasks and notifications
Scheduled tasks store the task instructions, timing information and status needed to run later. When browser notifications are enabled, SenvoAI can ask the browser to display a task result. Notifications may be visible on a device lock screen depending on your operating-system settings, so avoid putting highly sensitive information in task titles.
16. Generated media
Generated images and videos can be stored in the Library so you can reopen them. Generated media can contain errors or unexpected details; review the result before sharing or relying on it.
17. Adaptive communication style
If “Adapt to how I write” is enabled, SenvoAI may summarise non-sensitive writing preferences from your own recent messages, such as whether you usually prefer concise, detailed, casual or formal replies. This feature is not intended to infer sensitive traits, identity, health, beliefs, politics or other private characteristics, and it should not copy spelling mistakes as a personality trait. You can turn the feature off in Personalization.
18. Search sources and external providers
For current-information requests, SenvoAI may send a focused search query to connected search providers and may fetch public webpages. Search cards can include the title, domain and available publication information. External websites can change after they are indexed, so important information should still be checked at the original source.
19. Railway hosting, backups and persistence
Cloud installations can use persistent storage for chats, account settings, uploads and generated files. A deployment without persistent storage can lose local container data when it is replaced. Operators should configure backups and persistent volumes where available. Import tools should be used carefully because a backup can contain private account data.
20. Authentication and account recovery
Email/password, Google and GitHub sign-in are separate authentication methods that can point to the same SenvoAI account when configured correctly. SenvoAI stores provider identifiers and the minimum account details needed for sign-in; it does not receive your Google or GitHub password. Password reset codes and verification codes should never be shared in chat.
21. Diagnostics, reliability and abuse prevention
Basic technical information such as request timing, provider status, failure type, rate-limit state and server logs may be processed to keep the service reliable, detect abuse and diagnose bugs. Logs should avoid storing secret keys, passwords or full authentication tokens.
22. Young users and supervised accounts
Some people using SenvoAI may be young users. The service should use age-appropriate safety controls and should not encourage users to bypass family, school, platform or legal restrictions. Where parental, school or organisational supervision is required, those controls may apply in addition to this notice.