Bibimer privacy policy
- Application
- Bibimer (app.bibimer)
- Operator
- Andineering
- Contact
- andy@andineering.com
- Effective date
- October 11, 2026
1. Purpose and information processed
Bibimer lets you control coding agents running in Termux on the same Android phone. It processes project names and folder paths, session identifiers and settings, instructions, responses, terminal and tool output, and files you choose to work with. This information is used to display your projects and sessions, send your instructions, show results, and provide the features you request.
The Android interface communicates with an authenticated bridge on the same device. The app stores preferences and connection information in its private storage, with the connection token encrypted using Android Keystore. Termux separately stores project and session metadata and agent records. The current Android app has no advertising or analytics SDK and no feature that uploads your conversations to a Bibimer-operated server.
2. Coding agents and external services
When you send an instruction, the agent you select may transmit prompts, code, files, conversation context, and tool requests to its configured AI providers and other services. Processing and retention depend on the agent, provider, account, permissions, and settings you use. A local bridge connection does not mean that AI processing stays on your device.
If you choose to continue a conversation with another agent, the context you review and send is delivered to that agent and may be kept in its records. Termux, package repositories, development tools, and external websites also handle requests when you install tools or open their links. Check the policies of the services you select.
3. GitHub and opening files
GitHub import uses GitHub CLI in Termux to authenticate, list repositories you can access, and clone the repository you select. GitHub CLI manages its credentials in Termux. Bibimer displays the account status, repository information, and a temporary sign-in code when needed; it does not send the authentication token to its WebView or ordinary logs. Cloned files remain in the folder you select.
When you choose to open a project or Download file in another Android app, Bibimer creates a temporary copy in its private cache and grants the selected viewer temporary read access. The viewer then processes the file according to its own practices. Editing that copy does not change the original project file. Cached copies are subject to size limits and expiry and are cleaned on subsequent app use or disconnection.
4. Notifications and permissions
With notification permission and response monitoring enabled, completion alerts can include project and session names and up to 180 characters from the completed response. The public lock-screen version uses a general completion message. Android notification settings and other apps with notification access can affect who can see notification content. You can stop monitoring in Settings or from its ongoing notification.
Termux command access requires your Android permission and Termux external-app settings. Bibimer uses that access for the setup and development actions you request. Completion previews are not stored in bridge metadata files or ordinary logs.
5. Retention, deletion, and control
App settings and connection information remain until you clear the app's data or uninstall it. Recent bridge output and queued messages are limited to the running session's memory and may disappear on process termination or bridge restart. Termux project files, session metadata, and native agent records are stored separately; their lifetime depends on your actions and the agent's retention settings.
Removing a project registration or deleting an ended session from Bibimer's list removes only its Bibimer registration information. It does not delete project folders, Git worktrees, or original agent records. Use Termux and the relevant agents to delete those files and records. Uninstalling Bibimer does not remove them. Request deletion of provider-held information directly from that provider.
Bibimer does not create a separate Bibimer user account. GitHub and AI provider accounts are managed by those services. You can disconnect Bibimer from the local bridge in the app and revoke external service access using the relevant service or tool.
6. Age range
Bibimer is intended for users aged 13 and older. External agents, providers, and development services have their own age and account requirements, which may be higher.
7. Website hosting
This website is hosted on Cloudflare Pages. Cloudflare processes request information, such as IP addresses and traffic data, to deliver and protect the website. Its infrastructure may process information internationally. Details are available in Cloudflare's privacy policy. This static site has no account, contact form, advertising, or analytics script added by Andineering.
8. Contact and changes
Send privacy questions and access, correction, or deletion requests to the contact address above. When you contact us, we process your email address, message, and any attachments to respond to and resolve your request. Include only information needed for your request. This policy and its effective date will be updated when the app's data practices change.