Privacy Policy
Last updated: September 18, 2026
Who we are
Adamas is a call-center agent workspace operated by Daniel Hipskind (“we”, “us”). This policy explains what data the product handles and where it lives.
Local-first design
Most day-to-day workspace data stays in your browser (localStorage / sessionStorage), including formatting patterns, notes, timers, themes, and many settings. That data does not leave your device unless a feature you enable sends it to a third party or to our API while you are signed in.
Account data (when you register / sign in)
If you create an Adamas account, we store on our servers:
- Username and email address
- A hashed password (we do not store plaintext passwords)
- Optional profile / synced settings you choose to save to the cloud
- Call logs and notes you explicitly sync to the server while signed in
Authentication uses an httpOnly session cookie
(adamas_session). That cookie is required for signed-in
API access and is not readable by page JavaScript.
Anonymous use
You can use core tools without an account. In that mode we do not create a user record. The app still loads over the network (HTML/JS/CSS), and infrastructure providers may see standard request metadata (see Cloudflare below). Contact-form submissions and similar explicit actions still send the information you enter.
Sensitive formatting inputs
Number formatting (phones, account numbers, SSNs, etc.) is processed in your browser. Patterns and inputs you keep for the formatter remain in local storage unless you export or sync them. You are responsible for handling sensitive data in line with your employer’s policies and laws such as HIPAA, GDPR, or CCPA where they apply.
When signed-in call logs include SSN-related fields, our API stores a masked form (last four digits) rather than the full number.
CRM and telephony integrations
Adamas can connect to CRM / contact-center systems (for example Cisco Finesse, Five9, Salesforce, Zendesk, HubSpot, Dynamics). Depending on the provider:
- Some connections run from your browser to the provider (credentials kept in browser storage for that session).
- Cisco Finesse requests are proxied through our server so the browser can talk to your Finesse host securely. In that case the server briefly sees the Finesse URL and auth header you supply for the request, then forwards the call. We do not intend to retain Finesse call payloads as a product feature.
Only connect systems you are authorized to use. Clear stored credentials when finished.
SMS (Twilio) and email
Optional SMS uses Twilio. Credentials you configure for SMS are associated with your account / settings and used only to send messages you initiate. Message content is delivered by Twilio under their terms. Optional outbound email similarly uses credentials you or the server operator configure; we do not use those features without your setup.
Cookies and similar technologies
We use:
-
Session cookie (
adamas_session) for signed-in users — httpOnly, SameSite=Lax, Secure in production. - Browser storage for preferences and local workspace data (not httpOnly cookies).
We do not use third-party advertising trackers or marketing pixels in Adamas itself.
Cloudflare
The live site may be fronted by Cloudflare for CDN, TLS, and DDoS protection. Cloudflare may process IP address, user agent, and request metadata under Cloudflare’s Privacy Policy.
Contact form
Messages you send via the contact page are emailed to us so we can respond. The form uses Google reCAPTCHA to reduce spam; Google may process your interaction under their privacy policy. Do not include passwords or unnecessary sensitive data.
Data security
We use HTTPS, httpOnly cookies, content security policy, and access controls on authenticated APIs. Local data security also depends on your device, browser, and who can access your workstation.
Your choices
- Clear site data in the browser to remove local storage
- Sign out to clear the session cookie
- Delete your account (when signed in) to remove server-side user data we store for that account
Children
Adamas is intended for workplace use by adults. We do not knowingly collect personal information from children under 13.
Changes
We may update this policy. The “Last updated” date at the top will change when we do.
Contact
Questions: use our contact page.