Skip to content
Sales PepBack to Sales Pep
All documents
Language
On this page
  1. Who we are and which processing this covers
  2. Data, sources and purposes
  3. Legal bases and use limits
  4. Providers and international processing
  5. Storage, retention and deletion
  6. Your rights, complaints and updates

Sales Pep Privacy Notice

Version 15 October 2026

Who we are and which processing this covers

Sales Pep is provided by TRDL, CVR 43474766, Hyllingeparken 15A, 4070 Kirke Hyllinge, Denmark. TRDL operates Sales Pep. Contact [email protected] about privacy, support, access or deletion. This notice covers the Sales Pep app, account workspace and direct service/support relationship.

TRDL is controller for necessary account administration, contracting, service security and support records. For meeting and preparation content supplied by a business, that business normally determines the purposes and TRDL acts as processor under the DPA. Requests about a meeting should go to that business; TRDL can help route them. Matching company names/domains do not create a team or give managers access to another user's history.

Data, sources and purposes

We use your email, sign-in/session information and necessary device/network metadata to authenticate you and protect the Service. Account details, company/contact context, preparation, notes, confirmed transcripts, coaching and recaps come from your actions and supplied content. Another participant's information may be included by the business using the Service. We use the content to provide the features you request, synchronise your personal history and handle instructed support.

An explicit audio check is local and bounded. Starting a live meeting streams microphone and computer audio separately to Soniox. Computer audio can include other apps and notifications. This flow does not add a meeting bot, screen recording or disk recording of live PCM. Pause listening or End stops capture; Pause coaching keeps audio and transcription running. The business must inform participants and establish the required permissions or other lawful basis before capture.

Relevant transcript, meeting/company and preparation context goes through the backend to OpenAI for coaching and recaps. Optional website import retrieves bounded public-page text for drafting. Output can be wrong and requires human review. Do not supply unnecessary sensitive or confidential material.

Agreement records contain the accepting account/email, server time, self-declared business identity, affirmation and exact document versions/copies. This documents authority as declared, not independently verified identity. Support/request records contain the information needed to handle your case. Do not send passwords, sign-in codes, invitations or full customer transcripts as routine diagnostics.

Legal bases and use limits

For our own controller processing, the bases are contract steps/performance where the individual is a party; legitimate interests in administering business accounts, proportionate agreement evidence, security and support; and a specific applicable legal obligation where required. We consider necessity, minimisation and people's reasonable expectations. You can object to legitimate-interest processing subject to the applicable conditions. The Customer determines the basis for meeting content. Acceptance is not privacy, marketing or participant-recording consent.

We do not sell personal data or use Customer meeting content for third-party advertising. TRDL does not authorise Customer-controlled content for providers' general-purpose model training. Necessary confidential support/security access is limited to the request, incident or lawful purpose; identifiable content is not available for unrelated product research without an appropriate separate basis and permission where required. Sales Pep does not make automated decisions producing legal or similarly significant effects on people.

Providers and international processing

The DPA lists the processing suppliers. Applicable adequacy decisions or contractual safeguards, including relevant Commission transfer SCCs and necessary supplementary measures, apply to transfers where required. Information and available copies of relevant safeguards/onward-provider details can be requested from TRDL. An EU database or contracting entity does not establish EU-only processing. We do not promise account-specific regional hosting or Zero Data Retention that has not been separately agreed.

Storage, retention and deletion

Desktop account/history files use OS-backed encryption where supported. Browser storage, preferences and drafts are not all encrypted. Local storage supports sign-in, settings and saved work; it is not permission for advertising tracking. Protect devices, credentials and exports. No managed backup/restore service or fixed recovery window is currently included.

Managed saved transcript, notes and summaries expire 365 days after the original meeting date; reading, editing and import do not renew it. Daily bounded cleanup removes eligible account content; backlogs, locks or failed/missed runs can delay physical deletion. A successful synced meeting deletion clears its account content and leaves a limited marker with identifiers, timing, state and revision/deletion metadata to prevent stale copies returning.

Closed/offline devices may keep managed copies until trusted sync. Independent local originals, exports and copied notes remain under their holder's control. Protected backup copies, where present, and provider operational records have separate lifecycles. Deleted/expired data must not return to ordinary use on restoration. A delete click is not an instant wipe of all copies, and signing out does not delete an account.

Necessary account/profile data is kept while active, then handled through verified closure and the DPA return/deletion process. Available content may be requested for 30 days after service termination; this does not extend ordinary expiry or reverse earlier deletion. There is no self-service account-delete feature or guaranteed post-deletion login. Contact TRDL to verify the request/scope, arrange export or deletion and explain residual copies.

Necessary agreement/business-identity/closure evidence is retained for the relationship plus three years after verified closure for contractual accountability and claims. A specific legal hold is limited, justified and reviewed; applicable statutory records follow their actual legal duty. Ordinary support-case notes are removed 90 days after resolution and separately collected diagnostic/security notes after 30 days unless an ongoing documented incident requires them. These periods concern TRDL's own case records, not vendor logs or all ordinary mailbox contents. Contract evidence is separate from meeting content and account deletion. Copies/correction/erasure requests remain available through TRDL after proportionate identity checks.

Your rights, complaints and updates

Depending on the applicable conditions, you may request access, correction, erasure, restriction or portability, and object to processing. Withdrawal applies where processing actually relies on consent. Contact [email protected]; identity checks are proportionate and requests are handled under applicable deadlines and exceptions. You may complain to the Danish Data Protection Agency, Datatilsynet (www.datatilsynet.dk), or another competent supervisory authority. Meeting-content requests remain subject to the responsible business's instructions and obligations.

We identify material updates and keep this notice consistent with the Service. Agreement changes follow their separate acceptance rules; an editable web notice does not replace agreed contract copies. This notice does not itself ask you to consent to processing.