Privacy policy

Who is responsible

briefly Contact is published by Dustin DeBard under the brieflyOS brand. This policy covers the briefly Contact app and contact.brieflyos.com. Other brieflyOS products have their own policies. Privacy questions: support@brieflyos.com.

Cards, photos, and contacts

The app stores the cards you create in its local app storage: names, titles, companies, phone numbers, email addresses, websites, addresses, social links, wording, QR settings, appearance choices, selected portraits, and logos. There is no briefly Contact account or app-operated card-sync database.

Photo selection uses the system picker. You choose which image to provide; the app does not scan your photo library. Selected images are resized and re-encoded without their original photo location metadata. Optional contact import uses the system contact picker and copies only the contact you select into an editable card; it does not upload your address book.

Optional background removal uses Apple Vision on your device. It does not send the photo to a generative AI service. A restore copy is saved with that card; replacing or removing its photo removes that restore copy from the current card. Card data is eligible for device backups, which follow your Apple and device settings.

Optional Apple Wallet signing

The release candidate uses wallet.brieflyos.com. The app shows that signing host and requests your confirmation before sending a card over HTTPS. The request includes the selected card’s details, current portrait and logo, QR content, appearance, and card identifier. The original portrait restore copy is excluded.

The deployed signing service processes cards to create a signed pass without a card database or request-body logging. Temporary signing files are removed after the request. The service keeps request IP addresses and request counts in memory for rate limiting; stale entries are removed as later requests arrive, and restarting the process clears that state. There is no persistent card store. Cloudflare processes connection metadata and security events to connect and protect this service. Our host keeps bounded operational container logs (up to three 10 MB files per service); these may include startup or connection diagnostics. Our application does not write card bodies or request access logs. Infrastructure security records follow the providers’ policies, so we do not promise that every connection trace is immediately erased. Importing an existing signed pass uses Apple’s system interface.

Apple handles Wallet storage under its own policies. Deleting a card inside this app does not remove an existing pass from Wallet. Pass updates are not automatic; changed details require a replacement pass.

Advertising, tracking, and analytics

The app contains no advertising SDK, embedded analytics, or cross-app tracking. We do not sell card data or share it for targeted advertising. The app does not request your device location, camera, or microphone to create a card. Apple may separately process purchases, diagnostics, backups, or Wallet data according to your settings and its policies.

This website and infrastructure

The site has no signup form, advertising scripts, analytics tags, external font requests, or social embeds. Images and fonts are served with the site. Its own code does not set cookies, use local storage, or build visitor profiles.

Hosting and network providers, including OpenAI Sites and Cloudflare, process normal web-request information such as IP address, requested URL, timestamps, browser information, and security events to serve and protect the site. Infrastructure cookies or security checks may be used by those providers. Their retention and processing follow their service policies; this policy does not promise an unverified log-deletion period. See Cloudflare’s privacy policy and OpenAI’s privacy policy.

Support correspondence

If you email support, we receive your email address, message, and any attachments you choose to send. We use them to answer the request, diagnose the reported problem, and meet applicable legal or security obligations. We keep correspondence while needed for those purposes. Do not send signing keys, passwords, complete contact libraries, or other unnecessary private information. You can request deletion of support correspondence using the address below; legal or security obligations may require some records to be retained.

Retention and your choices

Saved cards remain until you delete them or delete the app’s data. Recovery copies created after a library error can remain in app storage. Deleting the app, rather than offloading it, removes its local container; separate device backups and files you exported require their own management. Changing a card does not erase older copies in backups or with recipients.

See Privacy Choices & Deletion for steps to delete cards, restore copies, Wallet passes, exports, and backup copies, and how to revoke permissions. We do not operate an account system, so there is no account to delete. For information-access, correction, deletion, or other applicable privacy requests, contact support@brieflyos.com. We may ask for limited verification to avoid disclosing someone else’s data.

Children and policy changes

This is a professional card-creation tool, not a service directed to children under 13. We do not knowingly collect children’s personal information through a service account. If you believe a child sent personal information to support, please contact us. We will update the date and relevant disclosures when practices change. No storage or transmission method can be guaranteed perfectly secure.