Privacy policy

Two roles, two kinds of data

We wear two hats, and your rights depend on which one applies:

• For the website, demo requests, and app accounts, Adam Calling decides how data is used - we are the controller.
• For the people our customers ask Adam to call - names, phone numbers, recordings, transcripts, extracted answers - the customer decides. They are the controller; we process on their instructions as the processor.

If Adam called you and you have a request about that call, the company that asked us to call is the right first stop - and we help them honor every request.

What we collect

• Demo requests: name, work email, phone if you share it, what you type in the form, and the technical basics of the submission (IP address, browser). Used to reply - nothing else.
• App accounts: name, email, and the login and usage records needed to run and secure the service.
• Call data (as processor): the lead lists our customers upload, and what calls produce - audio recordings, transcripts, extracted answers, and call metadata such as duration and outcome.

How we use it

• To run the platform and place the calls our customers configure.
• To answer demo requests and support questions.
• To keep the service secure: abuse prevention, debugging, monitoring.
• Never to sell. We don't sell personal data, and we don't use customers' call data to build advertising profiles.

Recordings and transcripts

Calls are recorded and transcribed so our customers get answers instead of notes. Recordings are stored encrypted in AWS Frankfurt and deleted on a schedule the customer controls - 90 days by default, with export or purge anytime. Transcripts and extracted answers stay with the customer until the customer deletes them.

Subprocessors

The platform runs on a short list of vendors:

• Amazon Web Services (Frankfurt) - hosting, storage, database, and email delivery.
• Twilio - telephony, homed in Europe.
• Speech vendors (Deepgram, Cartesia, ElevenLabs) - turning the caller's speech into text and Adam's words into voice during live calls.
• Model vendors (Anthropic; AWS Bedrock EU endpoints for post-call analysis) - the language models behind the conversation and the extraction.

Each vendor gets the minimum it needs to do its job, under a data processing agreement. The current list is available on request.

Where data lives

The platform itself - compute, storage, database - runs in AWS Frankfurt. Some speech and model vendors process audio or text in the United States during live calls; those transfers rely on standard contractual clauses and the vendors' GDPR commitments. As EU endpoints for these pieces become production-ready, we move the processing into the EU.

Security

• Encryption in transit everywhere, and at rest for stored data and recordings.
• Access separated by organization - one customer never sees another's data - and limited by role within each organization.
• Credentials and API keys are stored hashed; we can't read them back.

Your rights

Under GDPR you can ask for:

• Access - a copy of the data we hold about you.
• Correction - fixing inaccurate data.
• Deletion - removing your data where the law allows.
• Portability - your data in a machine-readable format.
• Restriction or objection - limiting how your data is processed.
• Withdrawal of consent - where processing runs on consent, anytime, without affecting what happened before.

Write to hello@adamcalling.com and we respond within a month. If the request concerns a call one of our customers commissioned, we route it to them and assist. You can also complain to a supervisory authority - in Poland, UODO (uodo.gov.pl), or the one in your country.

Retention

• Demo requests: as long as we're in touch about them; deleted on request.
• Account data: for the life of the account, plus a short period after closure for security and billing records.
• Recordings: 90 days by default; the customer sets the schedule.
• Transcripts and extracted answers: until the customer deletes them.
• Where a law requires keeping specific records longer, we keep the minimum it requires.

Cookies

adamcalling.com sets no cookies and runs no analytics. The app uses strictly necessary cookies only: a session cookie that keeps you signed in and a token that protects forms. Nothing tracks you across sites.

Changes

When this policy changes, the date at the top changes with it, and significant changes are announced to account holders by email. Using the service after a change means accepting it.

Contact

Adam Calling · hello@adamcalling.com. A human will answer.