EN

Privacy and security

Secure meeting recording API

Give each customer control over capture, participant notice, storage and deletion. Meeting media stays behind authenticated endpoints, retention is explicit and the same policy follows every capture strategy.

Discuss your requirements Explore the Notetaker API

Privacy controls by design
POST /v2/{account_id}/notetakers/{id}
Explicit capture
Private artifacts
Scoped access
RetentionDeletionAudit history
  • Private

    Artifact responses

    Authenticated and marked no-store for shared caches

  • 3 modes

    Retention policy

    None, timed or long-term retention

  • Audio first

    Conservative defaults

    Audio on and video off by default

  • 1 endpoint

    Delete the capture

    Erase personal artifacts while retaining anonymous usage

Controls for GDPR-aware meeting products

Meeting audio, video and transcripts can contain confidential business information and special-category personal data. Security therefore starts before the bot joins: your product decides which meetings qualify, how participants are informed, what artifacts are generated and how long they remain available.

Unipile is generally the processor for Notetaker data while you remain the controller. You are responsible for the appropriate legal basis and participant notice in each market. The API gives you the technical controls to implement that policy; it does not replace legal review.

Make retention explicit in every workflow

Use no retention for delivery-only workflows, a timed window for operational access, or long-term retention where the customer contract requires it.

Create with timed retention
curl --request POST "https://api.unipile.com/v2/$ACCOUNT_ID/notetakers" \
--header "X-API-KEY: $UNIPILE_API_KEY" \
--header "Content-Type: application/json" \
--data '{
  "meeting_url": "https://meet.google.com/abc-defg-hij",
  "bot_name": "Acme Notetaker",
  "capture_settings": {
    "audio_recording": true,
    "video_recording": false
  },
  "artifact_settings": {
    "transcript": { "enabled": true },
    "summary": { "enabled": false },
    "action_items": { "enabled": false }
  },
  "retention": { "type": "timed", "hours": 24 }
}'
Delete when no longer needed
curl --request DELETE "https://api.unipile.com/v2/$ACCOUNT_ID/notetakers/$NOTETAKER_ID" \
--header "X-API-KEY: $UNIPILE_API_KEY"

Privacy controls across the lifecycle

  • Capture is opt-in

    Enable the beta per organisation and define recording rules deliberately instead of silently activating every connected account.

  • Participant-facing identity

    Set your application name, avatar and announcement so a visible notetaker explains why it is present.

  • Artifact minimisation

    Generate only the audio, video, transcript, summary and action items your product actually needs.

  • Authenticated delivery

    Media and artifact responses require Unipile authentication and carry private, no-store cache controls.

  • Scoped configuration

    Apply application defaults, then override policy for an account scope or one connected account.

  • Deletion and auditability

    Delete upstream artifacts and personal Notetaker data while preserving anonymised billing evidence and an operational history.

Turn policy into product behaviour

  1. Define the lawful workflow

    Document the meeting categories you capture, the legal basis, participant notice and the artifacts your feature truly needs.

  2. Configure least retention

    Choose none or the shortest timed retention compatible with delivery, support and contractual requirements.

  3. Expose user control

    Show status clearly, provide a stop action for active capture and connect your deletion workflow to the Notetaker DELETE endpoint.

What happens when you delete a Notetaker

Deletion removes upstream artifacts and personal Notetaker data. An active job must leave the meeting first; a scheduled job can be cancelled before deletion. Anonymised billing seconds remain so usage exports and invoices stay reconcilable without retaining the meeting content.

Never copy transcript or media into application logs, traces or webhook histories. If your product stores an artifact after fetching it, that copy falls under your own retention and deletion implementation too.

Continue exploring the Notetaker API

Secure meeting recording — frequently asked questions

Is the Notetaker API GDPR compliant?

The API provides controls for privacy-aware implementations, including scoped access, retention and deletion. Compliance depends on your purpose, legal basis, participant notice, configuration and downstream storage, so it should be assessed for your use case.

Are recordings publicly accessible?

No. Artifact and media endpoints require Unipile authentication and are marked private and no-store for shared caches.

Can I avoid storing recordings?

Yes. Select a no-retention policy for delivery-only workflows, or use a timed policy from 1 to 8,760 hours. You can also disable video or any generated artifact you do not need.

Can participants see who is recording?

Cloud capture appears as a participant with the name and avatar you configure, and can use a configured announcement. Your product remains responsible for appropriate notice and consent flows.

What remains after deletion?

Upstream artifacts and personal Notetaker data are removed. Anonymised usage is retained so billing can still be reconciled.

Ready to integrate every channel?

Talk to our team or start building today.

Book a demo Start for free