Your conversations.
Your own space.

ImiCall is a two-person browser calling app. It does not ask for an account, phone number or access to your address book. This describes the application’s current behavior, not a promise of perfect anonymity.

What stays on your device

Contact names, your optional display name, invitation secrets, a random notification-device identifier and preferences are stored in this browser profile. They are not uploaded as a phone book. In-call messages live in memory and are cleared after the call. The app does not record audio.

Browser storage is not a secure vault. Someone with access to your unlocked device or browser profile can read your contacts and invite secrets. Clearing site data or using a temporary browsing session can lose your contacts. There is no account-based recovery.

Temporary sessions and IP protection

Temporary sessions keep contacts and presets in page memory instead of persistent browser storage. Reloading or ending a connected call forgets these temporary contacts; background alerts are disabled. A tab-scoped session marker remembers the mode, not contacts. Your existing regular Phone Book stays saved separately. This is not forensic erasure: downloaded backups, clipboard, browser history, screenshots, operating-system memory and copies on other devices are outside this feature.

Calls default to relay-only IP protection. Without a configured TURN relay they stop instead of connecting directly. You may explicitly allow direct calls in Settings; that can expose your IP to the other participant. The service and relay still observe network metadata, and neither mode guarantees anonymity.

What the server temporarily handles

The connection service handles random room identifiers, join-verification tokens, connection status and encrypted call-setup messages. Active routing lives in memory. Call setup is encrypted with AES-GCM using the invitation secret; the media uses WebRTC DTLS-SRTP, with the peer’s certificate fingerprint protected by the encrypted setup exchange. The application does not save call audio, message contents, contact names, room history or call logs to server files.

The host, network and any STUN or TURN service can still observe connection metadata such as IP addresses and timing. A direct call can reveal your IP address to the other participant. Hosting-provider access logs and retention must be reviewed separately by the operator; application code cannot make them disappear.

Tiny messages

Short notes use invitation-secret encrypted signaling without a microphone or media relay. Both people must be online. Notes remain only in app memory, expire after 90 seconds and clear locally when the panel closes. Delivery receipts indicate device receipt, not reading. No server-side offline mailbox is kept. Recipients can still copy messages or take screenshots.

Background notifications are optional

Enabling alerts sends your browser’s push delivery address and public subscription keys to the connection service, associated with a random room and device ID. They stay in server memory for up to 24 hours after the last renewal, and disappear on restart. Opening ImiCall renews subscriptions; an open page renews hourly. Turning alerts off removes this device’s delivery entries and unsubscribes the browser. No durable server backup is kept.

Push providers such as Apple, Google or Mozilla also process notification delivery. Alerts contain a generic incoming-call notice and a random room reference, never the invitation secret or contact name. Delivery depends on connectivity, operating-system settings and browser support. On iPhone or iPad, add ImiCall to the Home Screen before enabling alerts. Alerts cannot be guaranteed at every moment or after routing expires.

Microphone and camera

Microphone permission is required to place or answer a voice call. Setup checks access and immediately stops its test stream. The microphone is released after a call is cancelled, declined, ended or disconnected. Camera access is requested only if you choose to scan a QR code. Notification permission is requested only when you choose Enable.

Keep the invitation private

A new invitation includes a randomly generated 256-bit secret in the URL fragment after #. A fragment is not sent in the HTTP request. Anyone with the complete link can join that connection, so share it privately and create a new connection if a link leaks. Third-party sharing services receive the invite you choose to send through them. Legacy shared-PIN links cannot place calls in this version.

Encryption does not prevent a participant recording with another device, an infected device reading data, or a compromised application host serving modified code. This release has not received an independent security audit. Do not describe it as impossible to intercept under all circumstances.

Backups and optional voice effects

You can export contacts in a password-encrypted file and import it into another browser. Keep that file and password private; there is no password recovery. Voice effects run locally and start turned off. Exported presets contain effect settings only. Effects cannot guarantee that your voice is unrecognizable or cannot be reconstructed.

Remove your local data

Remove a contact from its selected connection panel. In Settings, “Reset All & Create Fresh Line” removes saved ImiCall contacts, your name and alert subscriptions after confirmation, then creates a fresh connection. In Data and backup, “Clear all ImiCall data” removes saved contacts, presets and offline caches and disables alerts. The app caches its interface for faster repeat and offline visits; calls still need internet. You can also clear this site’s storage in browser settings. The other participant controls their own local contact copy.