Privacy policy
Your device, your agents, your choices.
Effective date: 28 October 2026. Sponic Garden, Inc. ("we", "us") publishes BRIDGIT Device Manager for Android and operates bridgit.cc. This policy explains how the current app, this website and our support channel handle information. Contact us at support@bridgit.cc for privacy questions or requests.
1. What BRIDGIT does
BRIDGIT lets you connect named AI agents to an Android device you own or are authorized to manage. The app runs a device API; you choose agents, permissions and enabled capabilities. The current app does not require a BRIDGIT online account. Direct device access uses your Tailscale network. Planned appliance workflows, live monitoring and voice-triggered family help are not covered as available services.
2. Information processed on your device
- Agent and security information: agent names, settings, permission choices, credential hashes and pairing information. Pairing or key-rotation screens temporarily handle the credential needed to connect your agent. Treat those credentials as secrets.
- Device and request information: app and Android versions, capability status, battery and connection information, request identifiers, timestamps, calling-agent information, network addresses and activity/error records.
- Content you authorize: camera images, microphone clips, gallery photos, screen captures and location when the relevant feature and Android permission are enabled. Screen captures may include information from other apps. Interactions, speech/audio playback, agent messages and feedback reports can contain text, responses, attachments or screenshots you or your agents provide.
The exact available capabilities depend on your app version. Android permissions, the app's feature switches and agent controls determine access. The app's local status and logs help you review activity. Enabling one feature does not make every feature available to every agent.
3. Where information goes
Device content and API results go to the agents and destinations you authorize. If you configure callbacks, the app can send events to the configured recipient. A recipient may be an AI provider, an agent on another computer or another service you choose. That recipient may retain copies under its own policies. Data sent to an agent does not necessarily stay on your phone.
Pairing an agent does not by itself upload your gallery or device content to a BRIDGIT-operated content repository. We do not have a central BRIDGIT account dashboard through which we can browse or erase your device. If you deliberately send content to us in a support message, we receive that content.
4. Crash reports and update checks
Current distributed app builds use Sentry for crashes, unhandled errors and application-not-responding reports. Crash reporting is enabled by default and can be switched off under Settings → Privacy → Send crash reports. Reports can include error messages, stack traces, app/Android versions and device facts such as model, battery and memory.
The app is configured not to attach screenshots or view hierarchies, not to send session tracking or performance traces, and not to set a user identity or persistent device ID in these reports. Error text is filtered for credentials. The receiving service necessarily handles the network connection, including its source IP address; the app's settings do not by themselves guarantee removal of all connection metadata from a provider's systems. These safeguards reduce the information sent; they are not a reason to put secrets in error messages.
The in-app updater requests version information and, when an update is selected, an APK from a Cloudflare-hosted download service. Those requests expose ordinary connection information, including an IP address, to the hosting provider. Android asks you to approve installation.
5. Website visits and support email
Cloudflare hosts bridgit.cc and processes requests to deliver and protect the site. This includes information such as IP address, requested URL, request time, browser information and security/operational logs. The website's application code does not add advertising trackers, product analytics, session replay, marketing forms or external font requests.
When you email support@bridgit.cc, Cloudflare Email Routing forwards the message to our Google-hosted support inbox. We receive your email address, message, mail headers and any attachments you send. We use these to answer questions, investigate problems and handle privacy requests. Do not send agent keys, pairing QR codes, passwords or unnecessary personal media.
6. Why we use information
Information is used to provide the device functions you request, authenticate agents, enforce your controls, show activity, diagnose faults, deliver updates, operate and secure the website, and respond to support or privacy requests. We do not sell personal information or use device content for targeted advertising.
Where data-protection law requires a legal basis for information we process, these purposes include responding to your requests and providing requested services, our legitimate interests in operating and securing the software and website, complying with legal obligations, and consent where required. Device operators and the AI services they select are separately responsible for the purposes for which they capture or use other people's information.
7. Storage and retention
Agents, settings, activity logs, feedback and interaction records are kept in app-private storage on the device. Android app backup is disabled. Current log defaults are 30 days and 20,000 activity entries, with periodic trimming; settings can change those limits, and records may temporarily exceed them between trims. Other stored items follow their own app controls and cleanup behavior. Temporary capture files are normally removed during request cleanup, but an interruption can leave temporary files until later cleanup or an app-data reset.
Removing an agent revokes its access but does not erase every historical log, feedback record or recipient copy. Original gallery media and exported files remain outside app-private storage. Support correspondence and diagnostic information are retained for resolving issues, necessary follow-up, security and applicable legal obligations, rather than as a permanent device-content archive. Provider logs and copies held by agents follow the relevant provider's retention practices. Contact us about information held in our support or diagnostic systems.
8. Service providers and international processing
Relevant providers include Cloudflare for web hosting, updates and email routing, Sentry for crash reporting, and Google for support email. Tailscale provides the networking service you configure separately. Your chosen agent providers have their own privacy policies.
Provider infrastructure and support processing may involve countries other than yours. The provider policies and any applicable contractual safeguards describe their processing and transfers. We may disclose information we hold when legally required or as necessary to investigate abuse or protect people and systems.
9. Your controls and rights
You can stop the listener, disable features, revoke Android permissions, remove or rotate agent keys, change log retention, clear activity history and turn off crash reporting. Clearing activity history does not remove every diagnostic record. Clearing BRIDGIT's Android app storage or uninstalling it removes app-local records and pairing. See Your data for the limits of local deletion.
Depending on applicable law, you may have rights to access, correct, delete, restrict or obtain a copy of personal information, object to certain processing, withdraw consent or complain to a data-protection authority. Email support@bridgit.cc and describe the information and request. We may need proportionate information to verify your request. We can act on information we hold; for device-local data use the app controls, and contact an agent/provider separately for its copies.
10. Children and other people
BRIDGIT is intended for adults managing devices. It does not offer child accounts or a child-directed online service. Obtain the permissions and notices required before capturing another person's image, voice, location or screen information. A future monitoring feature will need its own review and disclosures before release. If you believe a child has sent personal information to our support channel, contact us.
11. Changes
We will update this page and its effective date when our practices change. Material changes to device access or new hosted services will also need appropriate in-app notices and controls. This policy describes the services available now; it does not authorize planned features in advance.