Updated October 29, 2026 · Version 2026-10-29.2

Privacy and data

Callback is in development. Purchase and live messaging are unavailable. Paid-service policies below describe the approved planned subscription; they do not activate billing or unverified app controls.

Contact and scope

Matthew Baumli, an individual, is the Callback seller. Contact vulnarity@gmail.com with privacy enquiries. This notice distinguishes the public website, local development app, customer-owned Twilio account and information voluntarily sent to support.

Website and billing

This static product site has no signup form, payment collection, app-data collection form, analytics or cookies added by Callback. The billing review is informational and sends nothing. Cloudflare Pages can process technical request information under Cloudflare’s privacy policy. No real payment processor has been configured. Its identity and data practices must be disclosed before paid checkout opens.

Local records and drafts

The reviewed development app stores customer names and phone numbers, messages, delivery errors, job descriptions, locations, timing, photos, quotes, estimates, notes, consent evidence and send receipts in local SQLite. Unsent Inbox/Jobs drafts live in the native browser profile. Ordinary business records and drafts are not application-encrypted; Windows account and disk protection matter. Local job photos are not an MMS feature.

Provider credentials

Native setup passes the account identifier, API key and selected number to the trusted native process. The reviewed vault uses Electron safeStorage with OS-backed encryption and refuses unavailable/plaintext fallback storage. Secrets exist transiently in setup/native memory and provider authentication. They are not intentionally logged, returned in status, stored in browser localStorage or included in JSON/CSV exports. Credential encryption does not encrypt the whole customer database.

Twilio data flow

When separately connected, the integration makes HTTPS requests to Twilio’s US1 API for the selected customer-owned account and number. Manual sending transmits authentication, the business number, recipient number and text. Sync downloads retained message history and delivery/status information. Initial sync covers the last 30 days; later catch-up depends on retained history and provider availability. There is no Callback-hosted cloud inbox. Twilio, carriers and authorized provider-account users process data independently under their services and policies. MMS attachment counts may be indicated; media is not downloaded, displayed or sent by this integration. Live activation and carrier delivery remain untested. See Twilio’s privacy notice.

Exports, backups and development fixtures

JSON and customer/job CSV exports contain readable business/customer information but exclude provider secrets. CSV export guards against spreadsheet formula interpretation; exports are not anonymous. JSON export does not provide an import/restore workflow. Existing explicitly approved local update backups copy records/drafts, not the credential vault. Private billing-test fixtures store local subscription states, acceptance snapshots/hashes, actor labels, timestamps and action/event receipts. They collect no real payment data and are not evidence of an actual subscription. Exports and backups are user-controlled copies and are not removed by disconnecting.

Support and updates

If you contact vulnarity@gmail.com, send only the purchase reference, description or diagnostic information needed. Do not send API secrets or unnecessary customer records. Support messages and attachments pass through Gmail under Google’s policies. The reviewed development release has update hosting disabled and no remote app analytics added. A future updater, payment flow or diagnostic service will need a corresponding notice update before activation.

Retention, disconnect and deletion

The current app has no automatic record expiry. Disconnect removes the saved encrypted credential and stops future local sync/send; it does not revoke the API key at Twilio or erase business records, exports, backups or provider history. Confirmed local deletion is now implemented in the private development build, including its normal workspace; it has not been publicly released or installed into the stable app. It requires a scope/count preview, a matching JSON export from the last five minutes, confirmation that the downloaded file was verified, and the exact typed confirmation phrase. Changed records invalidate the preview/export. Twilio must be disconnected with no saved connection or active sync/configuration, and uncertain sends must be resolved first. The transaction rolls back on failure. Stale-tab edits are rejected; browser drafts and in-memory selections clear when connected app tabs next synchronize or reload.

Cancellation and requests

The approved paid-service policy keeps existing local records readable/exportable, stops paid send/sync at paid-period end and makes deletion a separate explicitly confirmed choice. No automatic local deletion is promised. The development deletion workflow removes current-workspace customers/jobs, message bodies, notes, photos and retry payloads. It retains business settings, legal/subscription audit and pseudonymous safety records: keyed hashes of opted-out phone numbers, deleted event/action identifiers, a deletion cutoff and workspace epoch. These records are not anonymous. Provider history at or before the cutoff is not reimported; later requests can create fresh records while prior opt-outs remain enforced. A newly verified START plus owner review is required to remove suppression. Exports, backups and Twilio/carrier copies remain. This is logical SQLite deletion, not forensic disk erasure or deletion of every copy. No actual user records were deleted during verification; tests used disposable profiles. No automatic deletion is promised. Production billing and trusted entitlement enrollment remain unconfigured. Local deletion does not erase Twilio-side copies or independently saved exports/backups. Email vulnarity@gmail.com for a privacy enquiry. Request handling distinguishes seller-held support/billing information from customer-controlled device files and independently held provider/carrier records; the seller cannot erase another party’s records simply by disconnecting an account. Applicable legal rights remain available.