FEBPHONE · PRIVACY
Privacy policy
Updated 10 September 2026 · Current internal-test service
FebPhone is a subproject of FebCloud, a Singapore cloud computing company. This notice explains how the website, communication service, AI features and diagnostic testing handle data. The scope of each feature matters: a diagnostic report and a call recording are different kinds of data.
Website accounts and membership
We process your email address, password hash, login session and membership orders, including plan, payment status and administrator confirmation. Passwords are stored as hashes. The current website payment flow is manual; it does not collect payment-card details.
Calls, SMS and contacts
Communication features process device registrations and pairing, SMS content and phone numbers, call events, and contacts you add or import. These are used to route and display your communications and keep the devices in your account connected. Communication data is not restricted to the device.
AI participation and service providers
When you select AI answering, translation, calling or summarization, the relevant authorized audio, transcripts, task instructions and context may be processed by our servers and AI providers. The current implementation uses OpenAI for AI processing. Current AI calls enable recording, transcription and summaries; end AI participation before stopping recording. Review your selected mode and recording settings before use. Obtain any participant consent required for the conversation.
Recordings and access
Enabled call recordings are stored in private UCloud UFile object storage. Playback requests are checked against your account and use short-lived signed links. Keep playback links private. We do not claim that the entire service is end-to-end encrypted. FebCloud’s Singapore location does not mean that every processing operation takes place in Singapore.
Automatic diagnostics and adaptation requests
The current Android test APK uploads operational diagnostics automatically after it is opened, bound and connected. Reports include model, firmware, app version, permissions, module state, reported audio capabilities and failure clues. Diagnostic content excludes SMS bodies, phone numbers, recordings, transcripts and credentials; the upload is associated with an authenticated account and installation/batch identifiers. AI adaptation analysis uses a separate confirmation before sending limited, redacted evidence to the AI provider. Passive checks do not record the microphone or place calls.
Cookies and local preferences
The website uses a login-session cookie for account functions. A language choice is remembered in a first-party cookie for up to one year. Theme preference is stored in your browser’s local storage. You can clear these in browser settings; clearing login cookies signs you out. This redesign does not add third-party advertising or analytics scripts.
Your choices, retention and deletion
Choose when AI joins and review recording settings. Stopping Background service disconnects the gateway but does not guarantee that automatic diagnostic uploads stop. This test build has no in-app automatic-diagnostics switch; contact your testing support channel to discuss pausing diagnostics. Stopping the service does not delete uploaded data. Some app records, such as SMS, contacts and call-history events, have delete controls. Deleting a call-history event does not also delete the recording or AI summary. The current release does not offer complete self-service account or cloud-recording deletion, and this notice does not promise automatic deletion after a fixed number of days. Contact the project team for access, correction, retention questions or deletion requests.
Contact and updates
For privacy, access, correction or deletion requests, contact the FebPhone team at [email protected]. Include the account email and the scope of your request; never send your password. We will update this page when the published service or its data practices change.