Last updated: 10 August 2026 · v1.2
This register provides the information required by Art. 26 of the EU Data Act on data structures, data formats, relevant standards and procedures for switching to another provider or to on-premises infrastructure. SonicR1 does not provide an automated switching tool; the switching and exit plan agreed with the customer governs the process.
| Provider | Ömer Dertlioglu · SonicR1, Kurfürstendamm 96, 10709 Berlin, Germany |
|---|---|
| Service | SaaS — AI-supported analysis and guidance of sales conversations |
| Scope of this register | All service plans; processing exclusively in EU regions (incl. Frankfurt, Belgium, the Netherlands) |
| Contact | legal@sonicr1.com (switching/exit) · info@sonicr1.com (support, Mon–Fri 9:00–18:00, Europe/Berlin time) |
| Change history | 10.08.2026 – v1.2 – AI suggestions and briefings added to sections 2/2b, seller portrait and practice evaluations explicitly excluded, residual categories named, statements on authorisation, logging and transport clarified · 08.08.2026 – v1.1 – data structures and standards added, periods under Art. 25 clarified, person-level AI evaluations explicitly excluded · 07.08.2026 – v1.0 – initial publication |
| Calls & transcripts | Call metadata, transcript segments with speaker attribution and timestamps — JSON (UTF-8) |
|---|---|
| AI analyses (team-level) | Including summaries, next actions, deal assessments, e-mail and agenda drafts, CRM preview per call — JSON. Person-level evaluations are excluded (section 3). |
| Call briefings | Cold-call briefings with inputs, the evidence drawn on and the generated sections — JSON |
| Audio recordings | Original audio files where stored in the selected processing mode — original container in a ZIP archive |
| Knowledge base | Objections/responses/proofs, battlecards, company profile, products, competitors, personas, playbooks, document metadata, and AI suggestions for maintaining these entries (with rationale and source references) — JSON, CSV |
| Account & workspace data | User profiles (name, e-mail, role), team and workspace settings — JSON, CSV |
| Consent records | Processing mode, time and method of attestation per call — JSON |
| Imported data | CRM snapshots (deals, persons, activities, notes), calendar events — JSON |
| Billing data | Invoices and payment history via the Stripe customer portal (PDF) |
Person-level AI evaluations of individual users (scorecards, coaching moments, rephrasing alternatives, live-vs-post comparison, training plan) are visible in the product only to the individual concerned and are therefore not part of the workspace export (see section 3). Individuals may request their own evaluations separately via legal@sonicr1.com.
The export is a directory tree of JSON and CSV files plus audio files. Each file contains an array of records of the same kind. Every export additionally includes a machine-readable field description (schema.json) and a manifest with record counts; the schema.json restates the same field list as this register in machine-readable form and adds the actual number of rows per file. A file with zero rows is still included with its complete field list. Rows with a set deleted_at field are entries deleted in the source system.
workspace/project.json | Workspace — id, name, slug, description, settings, created_by, is_personal, created_at, updated_at, deleted_at |
|---|---|
workspace/members.json / .csv | Members — user_id, role, joined_at, display_name, email, timezone |
workspace/workspace_settings.json | Settings — id, project_id, settings, retention_months, redaction_profile, redaction_map_ttl_days, output_ttl_days, created_at, updated_at |
workspace/workspace_reflexes.json | Reflexes (detection rules) — id, project_id, key, label, description, domain, is_built_in, is_active, language_dependent, keywords_by_lang, workspace_extra_keywords, sensitivity_override, parent_key, created_at, updated_at |
workspace/workspace_workflows.json | Workflows (automations) — id, project_id, name, description, nodes, edges, is_active, scope, priority, cooldown_seconds, reflex_key, created_at, updated_at |
calls/calls.json | Call — id, project_id, created_by, title, filename, status, source_type, call_mode, processing_mode, duration_sec, created_at, updated_at, reviewed_at, content_purged_at, transcript, words, raw_text, speaker_overrides, insights (without judgement keys), insights_updated_at, sentiment, topics, followup_draft, followup_lang, talk_ratio_pct, briefing_id, calendar_event_id, hubspot_deal_id, storage_bucket, storage_key, origin_meta |
calls/analyses_debrief.json | Analysis run — call_id, latest_run_id, processing_status, review_status, reviewed_at, reviewed_by, created_at, updated_at |
calls/analyses_debrief_modules.json | Analysis module — id, call_id, run_id, module_key, status, payload, user_edits, error, skipped_reason, attempt_count, model, cost_usd, latency_ms, created_at, updated_at |
calls/consent_records.json | Consent record — id, call_id, workspace_id, user_id, processing_mode, gate_for_mode, disclosure_version, disclosure_text_snapshot, attestation_method, stores_audio, stores_transcript, stores_ai_notes, ephemeral_only, attested_at, external_tool, copy_version, copy_snapshot |
knowledge-base/playbook_sections.json | Playbook section — id, playbook_id, title, sort_order, created_at, updated_at |
knowledge-base/playbook_blocks.json | Playbook block — id, playbook_id, section_id, block_type, title, content, bullets, stage_tags, persona_tags, topic_tags, keywords, language, is_pinned, priority, created_at, updated_at |
knowledge-base/company_profile.json / .csv | Company profile — id, project_id, name, industry, company_size, value_proposition, differentiators, target_markets, founding_year, headquarters, website, sales_methodology, average_deal_cycle, typical_deal_size, tone_of_voice, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/products.json / .csv | Products — id, project_id, name, description, short_pitch, features, pricing_info, pricing_tiers, common_objections, roi_metrics, use_cases, ideal_customer, is_primary, display_order, proof_points, competitive_advantages, target_personas, persona_ids, deal_stage, industry, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/competitors.json / .csv | Competitors — id, project_id, name, website, description, strengths, weaknesses, pricing_comparison, key_differences, common_situations, win_strategies, loss_reasons, talk_tracks, questions_to_ask, trigger_keywords, counter_objections, market_position, overlap_products, persona_ids, product_ids, industry, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/personas.json / .csv | Personas — id, project_id, title, seniority, department, description, pain_points, goals, decision_criteria, common_questions, objections, communication_style, preferred_proof_points, budget_authority, typical_concerns, influence_level, success_metrics, reporting_to, industry, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/objections.json / .csv | Objections — id, project_id, objection_text, category, trigger_phrases, recommended_response, follow_up_question, proof_point_ids, persona_ids, product_ids, competitor_ids, deal_stage, industry, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/proof_points.json / .csv | Proof points — id, project_id, claim_supported, proof_type, metric_value, before_after, attribution_source, persona_ids, product_ids, competitor_ids, deal_stage, industry, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/battlecards.json / .csv | Battlecards — id, project_id, competitor_id, title, one_liner, why_we_win, watch_outs, pricing_comparison, objection_handlers, proof_point_ids, trigger_keywords, persona_ids, product_ids, industry, deal_stage, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/plays.json / .csv | Plays — id, project_id, name, objective, steps, deal_stage, trigger_keywords, persona_ids, product_ids, industry, display_order, created_by, updated_by, last_reviewed_at, last_reviewed_by, created_at, updated_at |
knowledge-base/documents.json | Documents — id, project_id, name, description, doc_type, original_content, content_hash, linked_product_id, linked_competitor_id, linked_persona_id, file_size, page_count, source_url, processing_status, processed_at, storage_path, chunk_count, created_at, updated_at |
knowledge-base/playbooks.json | Playbooks — id, project_id, name, description, type, methodology, language, status, default_stages, is_team_featured, created_by, created_at, updated_at |
knowledge-base/ai_suggestions.json | AI suggestion for the knowledge base — id, project_id, kind, operation, target_entity_id, target_field, proposed_value, rationale, confidence, frequency, source_call_ids, source_quotes, status, reviewed_by, reviewed_at, applied_entity_id, run_id, created_at, updated_at |
briefings/briefings.json | Briefing — id, project_id, created_by, briefing_type, crm_provider, crm_company_external_id, crm_contact_external_id, crm_deal_external_id, manual_input, input_hash, evidence_snapshot, generated_sections, status, generation_id, error, last_used_at, not_relevant_at, created_at, refreshed_at |
imports/crm_*.json | CRM snapshot — id, project_id, provider, external_id, data, update_time, received_at, created_at, updated_at, deleted_at |
imports/calendar_events.json | Calendar event — id, workspace_id, provider, external_id, start_time, end_time, payload, deleted_at, synced_at, created_at, updated_at |
audio/<call_id>.<ext> | Audio recording — binary file in the original container; mapped via the file name (calls.id) |
No harmonised standard and no common specification for interoperability has currently been published in the central Union repository for this service category. The export therefore uses the open, widely adopted formats listed above. Once relevant standards or specifications are published, we will update this register and the export accordingly (Art. 30(4) Data Act).
Apart from the categories listed above, all content contributed by the customer or jointly generated through use of the service is covered by section 2. The person-level AI evaluations (first bullet) are not lost: they are provided to the individual concerned on their request (section 3b). These exclusions are not used to impede, delay or complicate switching.
The person-level evaluations excluded under section 3, as well as practice and simulation calls, are bound to the individual rather than to the workspace. They are therefore not part of the company export but follow a separate path:
Practice and simulation calls arise from an individual's own training and contain their evaluations; for the same reasons as in section 3 they are not part of the workspace export.
| Maximum notice period | no more than 2 months (Art. 25(2)(d) Data Act) |
|---|---|
| Transitional period | 30 calendar days from the end of the notice period (Art. 25(2)(a) Data Act) |
| Extension by the customer | The customer may extend the transitional period once for a period it considers more appropriate for its own purposes (Art. 25(5) Data Act). |
| Technical unfeasibility | Where the transitional period is technically unfeasible, we notify the customer within 14 working days of the switching request, justify the unfeasibility and indicate an alternative transitional period of no more than 7 months (Art. 25(4) Data Act). |
| Delivery of the export | within 14 calendar days of the agreed plan (our own commitment, independent of the period under Art. 25(4)) |
| Data retrieval period | at least 30 calendar days after the end of the transitional period (Art. 25(2)(g) Data Act) |
SonicR1 does not charge switching fees (cf. Art. 29 Data Act).
This register serves to fulfil Art. 26 Data Act. Contractual terms including periods, erasure and the retrieval phase follow from the service contract pursuant to Art. 25 Data Act.