Privacy Policy

1. Who we are and what this covers

Dial is a creator profile and link-sharing app at dial.bio, operated by Onyx LLC, a company in the United States ("Dial", "we", "us" or "our"). This policy covers pages that link to it and explains the current app, including its account features and browser-local previews. Our contact details are in section 12.

Social sign-in stores your account and session in the server database. Signed-in profiles and private media kits are also saved in that database and load across devices. Save and publish claims your username and makes your name, bio, photo, links, portfolio and design public at your Dial address. Media kit PDF report settings and thumbnails are excluded from public profile responses. Shared media kit details publish only when you enable the public Work with me section. Anonymous/sample profiles, appointments, subscriber entries, creator analytics and team previews remain in the browser being used. Existing account-local profile edits are uploaded only when you explicitly save and publish. Email delivery, automatic social content synchronization, payment processing and AI connections are not provided. Account services, fonts, external media and network requests mean that not all activity stays on your device.

Information a creator chooses to display on a profile is intended for visitors to see. Creators and outside services are responsible for their own processing when you contact them or visit their sites. Future shared booking and subscription services will require this notice to be updated before those features collect information.

2. Information the app handles

Profiles and creator content: Names, usernames, biographies, social and website links, descriptions, portraits or GIFs, custom icons, backgrounds, portfolio work, sponsors and appearance settings. Media kits may include a location, partnership email, topics, audience information, rates and case studies. These are supplied by you. Signed-in profiles are saved to your account database; Save and publish shares the public design. PDF report settings remain available to the signed-in owner; shared media kit details are public only when you explicitly enable public sharing. Anonymous and sample edits stay in the browser.
Appointment requests: Name, email, optional discussion notes, service, duration, date, time, timezone, status, record identifier and timestamps. Requests stay in the browser where they are entered. They do not currently reach a creator, reserve a real calendar slot or generate a meeting link.
Subscriber entries: Email address, creation time, a record identifier and the subscription checkbox selection and wording. Email ownership is not verified. This preview does not send email or notifications, and an entry is not automatically shared with the creator on another device.
Team preview: A proposed manager's name and email, invitation status and expiry, and an activity history. This is a local simulation; no invitation is emailed and no authenticated manager account is created.
Local creator analytics: Views, opens, clicks and booking actions, with timestamps, random visit identifiers and relevant link identifiers or labels. These power the local dashboard and are separate from developer analytics.
Developer analytics and replay: Optional Umami events and session replay are disabled for launch. Earlier analytics events and recordings remain in Dial's self-hosted analytics database; disabling collection does not erase them. Section 4 describes this separate processing.
Network and communications information: Services receiving a request can receive an IP address, browser information and other ordinary connection metadata. If you contact the operator, the recipient also receives your contact details, message and any attachments you provide.

Please avoid entering government identifiers, financial account details, passwords, health information or other sensitive information into Dial. Do not provide another person's information without authority. Apart from the identity information used for social sign-in described below, Dial does not currently import content from social accounts, access your contacts or request precise device location.

3. Why information is used

Account profile records let the app restore your edits across devices, reserve your username, and display your published design. Browser-local records retain anonymous/sample edits, demonstrate appointment and subscriber flows, and show local dashboard activity. Optional developer analytics, disabled for launch, are intended to help us understand feature use and investigate usability problems. Connection metadata may still be processed by the services delivering and protecting the site.

Information you send directly to the operator may be used to answer your request, investigate reports, protect users and the service, or meet legal obligations. We do not use the current app to deliver behaviorally targeted advertisements, send marketing emails or train an AI model. Sponsor banners are content selected by the creator.

The Design Kit's export downloads a file with your public name, bio, link addresses and appearance settings. It excludes your username, uploaded images, private profile sections and account credentials. Imports are validated and previewed locally; Dial does not send these files to an AI provider. If you choose to share an export with your own AI service, review its contents first and consult that service's privacy terms. Applying an import changes an editor draft. For a signed-in profile, Save and publish stores the resulting profile in your account and updates its public design. In the anonymous/sample preview, Save changes stores it in that browser.

Legal bases, where required. Before this notice becomes effective, the operator must confirm the applicable legal bases. The proposed approach is performance of a requested service for its necessary operations, legitimate interests for proportionate security and support, legal obligations for legally required processing, and consent for optional analytics, replay or marketing where required. This draft does not establish that an analytics exemption applies or that consent has already been obtained.

Social sign-in and sessions

When you choose Google sign-in, Google authenticates you and sends Dial your account identifier, name, email address, email-verification status and profile picture, where available. Dial requests Google's basic openid, profile and email permissions to create your Dial account and authenticate you. It does not request access to your Gmail, Drive, contacts or social posts, or request offline access. Your sign-in name and photo do not automatically populate your public creator profile.

Dial stores account, provider and session records, including authentication tokens, in its server database. The authentication library encrypts stored access and refresh tokens; this does not mean every token or database field is encrypted by the application. Sessions may include creation and expiry times, IP address and browser information used by the authentication service. A Secure, HttpOnly session cookie maintains sign-in on the HTTPS site.

Dial does not ask for or store your Google password and has no email/password or magic-link login. Signing out invalidates the session; clearing a local demo profile does not delete your server account. Account settings offers profile export, reversible deactivation and permanent deletion of your live Dial account. Deletion requires recent social sign-in and explicit confirmation; see section 7 for these controls and section 6 for the separate treatment of backups and local records.

4. Developer analytics and session replay

Disabled for launch. Dial's optional Umami tracker and session recorder are disabled in the launch configuration. The app does not load them under that configuration. Browser-local creator statistics are separate and remain available. These legal pages do not load the tracker or recorder.

Integration retained in the code. The optional integration targets um.dial.bio. Its event payloads use generic profile/dashboard page names and allowlisted actions, platform names or content categories. They exclude form values, custom profile names, custom link labels, full destination URLs, query strings and URL fragments; a referring website is reduced to its origin.

Replay and historical records. The separate recorder, when enabled on an eligible page, can capture displayed profile content, images, layout, clicks, scrolling and other interactions. Private forms and account controls are marked for exclusion, but public names, links and displayed information can appear in a recording. Earlier events, session records and replay data remain in Dial's self-hosted Umami database on the same U.S. Hetzner server. Access is restricted to the operator. Disabling the integration does not erase these records or associated network metadata; their retention and deletion handling are separate from disabling new collection.

Before any reactivation. The existing integration checks supported privacy signals and an opt-out preference; it does not provide a prior-consent flow. Analytics or replay must not be reactivated on the basis of this draft. Their data handling and any required consent controls need to be verified and disclosed first.

6. Account storage, browser storage and retention

Dial stores signed-in account records, saved profiles and private media kits in its server database. Browser storage separately remembers anonymous/sample profiles, existing local edits and preview records; it can contain uploaded images and personal information and persist across visits. Turning off developer analytics does not clear either type of storage. Storage technologies other than cookies can also be subject to privacy rules.

Accounts, saved profiles and private media kits: there is no automatic expiry for these records. They remain in the live database until changed or removed through account deletion. Deactivation preserves them while hiding the public profile. Editing and saving changes the stored profile and its published fields. Clearing browser storage or signing out does not erase these database records.
Deletion record: after account deletion, Dial retains only the internal account identifier and deletion time in a separate record used to prevent a restored backup from bringing that account back. This record does not contain your profile, email address or sign-in tokens. It has no automatic expiry while backup recovery may require it.
Database backups: Dial's deployment process creates separate, access-restricted database snapshots on the same U.S. server before migrations. These can contain earlier account and profile data. They do not expire automatically through that process, and no separate scheduled pruning was found in the server configuration checked for this launch. Changing or deleting a live record does not erase its copy from an existing backup. This draft does not promise a backup deletion deadline or claim that no provider-managed or externally made copies exist.
Browser-local profiles, uploads, bookings and subscribers: no automatic expiry is implemented. Local records remain until removed through an available control, overwritten, cleared in browser settings or removed by the browser. These actions do not remove copies already saved to an account.
Local creator events: when another tracking event runs, the app filters events older than 180 days and keeps up to the latest 10,000. This is not a scheduled deletion service.
Team records: an invitation stops being acceptable after seven days, but its stored personal information does not automatically disappear. The activity history keeps the newest 100 entries. Removing a manager does not erase earlier activity entries.
Historical Umami data: earlier analytics events, sessions and recordings remain stored on Dial's U.S. server with access restricted to the operator. The service settings checked for this launch do not define an automatic retention period, and no scheduled cleanup was found in the inspected server configuration. Disabling analytics or clearing browser data does not erase these records. Contact the privacy address with requests about information previously collected.
Server logs: Dial's web, account-service and database container logs rotate based on file size, not a fixed number of days. The inspected Umami and Cloudflare tunnel logging configuration does not specify rotation limits. This draft does not promise a fixed log deletion period.
Support records: correspondence and request records are separate from account and browser data. [Confirm support-record retention and secure request handling.] Browser-data clearing does not delete correspondence already received.

Cancelling an appointment changes its status without erasing its details. Restoring a sample profile or resetting an account profile changes the editor draft; it does not delete an account or immediately change its saved profile. Saving applies the replacement profile, but does not clear separate bookings, subscribers, team records or analytics.

7. Your choices

Analytics and replay in this browser

Optional analytics and replay are disabled for launch. You can still save an opt-out below; choosing Use site defaults does not enable a feature disabled by the site's configuration.

Checking this browser's preference…

Applies to this site address in this browser. Reload or close other open Dial tabs to stop an already loaded recorder. This does not delete earlier recordings or change local creator analytics. Using site defaults removes your saved opt-out; it is not consent to recording.

Privacy signals. Dial prevents developer analytics and replay from loading when it detects Global Privacy Control (GPC), Do Not Track (DNT), a saved opt-out, or unavailable browser storage. It checks these signals when loading analytics and sending its custom events. Reload an already open page after changing a signal.

Export your saved profile. In Account settings, download a copy of your saved profile before choosing deletion if you want to keep it. The file includes saved private media-kit information and embedded uploads, so keep it private. It excludes sign-in credentials and provider tokens. Unsaved edits and separate browser-local preview records are not included; this profile download is not a complete export of every record described in this notice.

Deactivate or reactivate. Deactivation hides your public profile and signs out your existing sessions. It preserves your account, saved content and reserved username. Signing in again does not automatically republish your profile: choose Reactivate in Account settings to restore it. You can also export or delete while the account is deactivated.

Delete your account. Account settings offers permanent deletion after a recent social sign-in and explicit confirmation. This removes the live Dial account, its linked sign-in records, sessions, saved profile and private media kit. Dial keeps the minimal deletion record described in section 6 for backup recovery. Deletion does not delete your Google account, revoke consent at Google, erase existing backups or earlier analytics records, or remove downloads and browser records on other devices. A later social sign-in can create a new blank Dial account. Editing profile content or signing out is not account deletion.

Local information. Use "Remove my local subscription" with the matching email, or the subscriber dashboard's removal control, to remove a local subscriber entry. To erase browser-local profiles and preview records, clear site data for this site in your browser's settings. This does not erase your server account, saved profile, published page or server backups. It also removes the saved analytics opt-out, so set it again or use a supported browser privacy signal if desired.

External services. You can choose not to open a link or load an external player. Once you do, use that provider's controls for information it receives. The controls on this page do not govern Google Fonts, outside services or separate browser-local creator statistics.

Future communications. There is no email delivery in the current preview. Any future marketing subscription must offer withdrawal or unsubscribe options. Essential booking messages must remain separate from optional creator marketing.

8. Privacy rights

Depending on where you live and whether the relevant law applies, you may have rights to know about processing, access or obtain a copy of information, correct it, delete it, restrict or object to processing, withdraw consent, and complain to a regulator. Some U.S. state laws also provide rights concerning sales, targeted advertising and significant profiling, an appeal of a denied request, and protection from unlawful discrimination for exercising a right.

Where the EU or UK GDPR applies, relevant rights include access, rectification, erasure, restriction, portability, objection and withdrawal of consent. Withdrawing consent does not affect the lawfulness of processing before withdrawal. You may complain to your local supervisory authority; contact information is available from the European Data Protection Board or the UK Information Commissioner's Office.

Send a request to the privacy contact below, describing the information and relevant site or creator. Verification should be proportionate to the request; do not send identity documents unless they are necessary and requested through an appropriate channel. Authorized agents may make requests where allowed by law. If a request cannot be fulfilled, the operator must explain the reason and any available appeal route as required by applicable law.

Dial cannot remotely inspect or erase records that exist only in your browser. The local controls in section 7 can help with those records. A local profile reset or browser-data clearing does not submit a request to delete your server account, saved profile or analytics records. Support requests are separate from those browser controls.

9. International processing

Onyx LLC is a U.S. company. Dial's account service, self-hosted Umami database and deployment-created backups are on the same Hetzner server in the United States. This includes earlier analytics and replay records. A local browser record remains on that device unless an interaction described above sends information elsewhere. Google and other external services process the requests they receive under their own arrangements.

[Confirm any applicable international-transfer safeguards before making claims about them.] This draft does not claim a particular adequacy framework, contractual transfer safeguard, EU/UK representative or data protection officer.

10. Security and children

Browser storage is not an authenticated private account. People with access to your browser profile may be able to read or alter its records. Use a device you control, keep sensitive information out of this preview, and clear local records when appropriate. No internet service or storage mechanism can guarantee complete security.

You must be at least 16 to create or manage a Dial account or creator profile. The service is not intended for creators under 16. This requirement is not a claim that the app verifies age; it currently has no age-verification system. If you believe someone under 16 has created an account, or a child has provided personal information in circumstances prohibited by law, contact the operator so the issue can be investigated and information under its control removed where appropriate. A local browser record may need to be removed on that device.

11. Changes to this policy

We will update the version and date when this notice changes. Material changes require appropriate notice before new processing takes effect, and consent where required. Adding new account features, payments, email, AI services or new tracking is not authorized simply by including it in a future draft.

This version is a review draft, not a statement that Dial has completed a privacy-law compliance assessment.

12. Contact

Operator: Onyx LLC
Postal address: 18310 Montgomery Village Avenue
Suite 300 #1024
Gaithersburg, MD 20879
USA

Privacy, account-deletion and rights requests: [email protected]
Telephone: +1 (202) 697-3381

This candidate requires the operator's review and approval before it becomes effective. Its retention limits, support-request handling and proposed legal statements are material to that review. Visiting this page does not send a privacy request.