Data export, switching providers and infrastructure

Last updated: 10 September 2026. This register describes Sendequelle’s available data structures, export formats and transfer methods, and the jurisdiction governing its infrastructure. Section 13 of the Terms and Conditions additionally governs contractual switching rights. Information on personal data processing is provided in the Privacy Notice.

1. Requesting an export or a switch

Authorised members can export available individual reports and organisation data in the relevant account area. To switch providers, request a complete export owed by law, or terminate a service with data deletion, contact emailn@emailn.de in text form. Identify your organisation, the affected services, the requested scope and, where relevant, the destination provider. Do not send passwords, API keys or private email content without being asked.

We verify your authority for the organisation and coordinate the available data, transfer method, timetable and necessary assistance with you. You may also switch to your own infrastructure. A broader statutory right to export does not depend on an account button already existing for each category of data.

The handling of a complete switch through this contact process must be distinguished from the automatic individual and organisation exports described below. No function automatically combines every module, original and configuration into a complete migration package. Additional data that remain available and must be provided are supplied separately during the requested switching process in a structured, commonly used and machine-readable format. The scope and file structure are communicated as part of that process.

2. Available export types

Area	Format and content	Access and limitations
Organisation data	UTF-8 JSON with version identifier sendequelle.organization-export.v2. Includes the master data, configurations, states, report overviews and metrics listed in section 3.	Through the Data and Privacy area and the authorised API. This file is a selection of organisation data, not a complete export of every module’s originals.
Email forensics	JSON, UTF-8 TXT and PDF technical reports. JSON contains structured findings and evidence information. TXT and PDF present these in readable form.	Within the same authorised organisation. Standard exports are redacted; full technical reports and originals require additional permissions.
Forensic comparisons	JSON, TXT and PDF containing stored comparison results.	Restricted to authorised comparisons within the same organisation. A comparison does not automatically include its underlying original messages.
Forensic originals	The original file still in storage; TXT for pasted header text, or the corresponding supported input format for a file upload.	Requires specific permission and an unexpired original retention period. For a pasted complete email source, header analysis retains only the separated header; the discarded body is not an original that can later be exported.
Delivery diagnosis	UTF-8 JSON and TXT containing the presented bounce or log diagnosis.	Authorised access to the report within the organisation. Report output is redacted and does not replace a complete original file.
Raw DMARC/TLS report	The stored incoming report message as EML.	Separate raw download where the original remains available and the user has permission. Organisation JSON contains report overviews, not automatically the full content of every raw report.
Abuse/threat cases	CSV for the case overview; CSV or TXT for filtered address or domain lists.	Subject to organisation, role and selected scope. The case overview does not contain every evidence attachment.
Enabled API reading endpoints	JSON for the relevant organisation resources, paginated where applicable.	Requires authentication or a valid API token with the necessary permission. API access does not replace a complete switching export.

JSON is suitable for structured further processing. Readable TXT and PDF reports are not a promise that another provider can directly import their contents as configuration. The PDF presentation can limit some technical detail characters; JSON is the relevant format for unchanged structured transfer.

The Abuse module’s CSV files use a semicolon separator and quotation marks where escaping is necessary. Cells are protected against execution as spreadsheet formulas. A protective character added during export is therefore not an unchanged original value.

3. Organisation export data structure

The JSON file contains top-level schema, generated_at and organization fields, followed by the lists below. organization is an object with public_id, name, legal_name, country_code, timezone, locale, status and created_at. The other groups are lists of records; a list is empty if no corresponding data exist.

Links between groups use public identifiers such as domain_id, source_id or monitor_id. Missing values may be null. Date and time values originate from storage maintained in UTC; date-only values identify calendar dates. Structured configuration or metric fields may be included as JSON strings within the file. Importers must therefore distinguish the outer JSON structure from any encoded values inside it.

Group	Fields per record
members	public_id, first_name, last_name, email, role, status, joined_at
domains	public_id, unicode_name, ascii_name, status, verification_status, verified_at, monitoring_enabled, report_ingestion_enabled, created_at
mail_servers	public_id, domain_id, hostname, source, mx_priority, expected, monitoring_enabled, current_status, first_seen_at, last_seen_at
mail_server_addresses	mail_server_id, ip_address, ip_family, source, ptr_hostname, asn, provider, first_seen_at, last_seen_at, active
service_endpoints	public_id, domain_id, hostname, service_type, port, source, verification_status, expected_tls, monitoring_enabled, current_status, first_seen_at, last_seen_at
dkim_selectors	public_id, domain_id, signing_domain, selector, source, expected, active, current_status, first_seen_at, last_seen_at
report_endpoints	public_id, domain_id, type, status, activated_at, rotates_at, revoked_at, last_received_at
monitors	public_id, domain_id, definition_key, definition_version, target_type, execution_key, enabled, expected_state, configuration, interval_seconds, timeout_seconds, last_run_at, next_run_at, created_at
monitor_current_states	monitor_id, status, result_code, severity, since, last_success_at, last_failure_at, consecutive_successes, consecutive_failures, updated_at
incidents	public_id, domain_id, monitor_id, assigned_to, status, severity, title, summary, current_evidence, recommendation_key, recommendation_params, rule_version, reopen_count, occurrence_count, resolution_code, opened_at, acknowledged_at, resolved_at, closed_at, last_detected_at, created_at
incident_events	incident_id, type, actor_type, payload, occurred_at, created_at
incident_comments	incident_id, user_id, body, created_at, updated_at
sending_sources	public_id, domain_id, source_key, source_ip, source_cidr, asn, ptr, provider, spf_domain, dkim_domain, dkim_selector, header_from, classification_status, source_label, customer_note, risk_score, confidence_score, risk_reason, current_metrics, reputation_approved_at, reputation_approved_by, first_seen_at, last_seen_at, classified_at
source_classification_events	source_id, actor_user_id, old_status, new_status, reason, note, created_at
dmarc_reports	public_id, domain_id, reporter_name, reporter_contact, report_id, date_begin, date_end, policy_domain, policy_p, policy_sp, policy_np, policy_adkim, policy_aspf, schema_version, total_message_count, status, overlap_status, received_at, parsed_at
tls_reports	public_id, domain_id, reporter_name, report_id, date_begin, date_end, contact_info, total_success, total_failure, status, dkim_verification_status, dkim_signing_domain, dkim_selector, received_at, parsed_at
domain_daily_metrics	domain_id, metric_date, health_score, health_score_version, coverage, uptime, incident_minutes, report_metrics, unknown_sources, min_certificate_days
dmarc_daily_metrics	domain_id, metric_date, reporter_key, total_count, dmarc_pass_count, spf_aligned_count, dkim_aligned_count, fail_count, dispositions
tls_daily_metrics	domain_id, metric_date, policy_type, failure_type, mx_hostname, reporter_key, total_success, total_failure
source_daily_metrics	source_id, metric_date, reporter_key, message_count, dmarc_pass_count, spf_aligned_count, dkim_aligned_count, fail_count
daily_usage_metrics	metric_date, metric_key, value, dimensions
domain_intelligence_findings	domain_id, rule_key, rule_version, observed_on, severity, result_code, input_metrics, thresholds, explanation, resolved_at
source_intelligence_findings	source_id, rule_key, rule_version, observed_on, severity, result_code, input_metrics, thresholds, explanation, workflow_status, consecutive_listed, consecutive_clean, first_detected_at, last_detected_at, recovered_at, reviewed_at, reviewed_by, review_reason, resolved_at
notification_channels	public_id, user_id, type, label, verified_at, enabled, last_tested_at, created_at
notification_rules	public_id, name, filters, routes, escalation, enabled, priority, created_at, updated_at
notification_deliveries	public_id, incident_id, channel_id, channel_type, recipient_ref, status, attempt, queued_at, sent_at, delivered_at, failed_at, next_retry_at, redacted_error, created_at
webhook_integrations	public_id, label, event_filters, status, last_tested_at, last_success_at, last_failure_at, created_at, updated_at
api_token_metadata	name, abilities, last_used_at, expires_at, created_at
subscriptions	plan, status, starts_at, trial_ends_at, current_period_start, current_period_end, external_provider, cancel_at, ended_at
audit_events	public_id, actor_type, action, target_type, correlation_id, created_at

The file contains no passwords, reusable API tokens, private keys, secret report address tokens or webhook secrets. Certain security, notification and log data are exported only as a limited selection. These limits of the standard export do not categorically reject a valid claim to additional customer configurations or metadata. Required additional data are assessed and provided separately during switching; access keys should be newly created at the destination.

In particular, this standard JSON does not include every individual email original, complete forensic and delivery report, forensic reference version, comparison content, test profile, all historical individual measurements or complete abuse evidence. Where such data remain available and are covered by the right to obtain them, they form part of the separate coordination and provision during switching.

4. Structures of other files

Forensic JSON reports contain a report identifier report_id, an export timestamp exported_at and the available report fields. These may include schema_version, engine_version, analysed_at, original information, state, authentication, findings, delivery information and subsequent DNS checks. The scope and nested details depend on the input format, available evidence and the selected redacted or full export. Missing findings are not replaced with invented results.

A forensic comparison uses schema version p10-comparison-1 and a comparison field containing available comparison results. Redacted output may mask addresses and remove raw headers, recipients, body sections, filenames or signature material. Redacted individual reports are intended to limit disclosure; they do not replace any broader export of the Customer’s own data owed by law.

Delivery reports contain report_id, exported_at and the presented diagnostic fields for the submitted DSN or log information. JSON preserves the structured presentation; TXT presents the diagnosis as readable text.

The complete Abuse CSV overview uses the columns received_at, source, external_id, subject, type, severity, status, email_address, domain, provider_feedback_status, provider_feedback_outcome and provider_feedback_sent_at. Filtered address or domain lists contain one corresponding value column or one value per text line.

Original files are output in the format still stored. An EML remains a message with its header and MIME structures; reconstructing an MSG does not turn it into byte-identical SMTP evidence. Further technical processing must consider the actual format and schema information in each file. Identical import of every Sendequelle function across providers is not promised; statutory interoperability and cooperation duties remain unaffected.

5. Security, time limits and deletion during switching

File retrieval requires access to the relevant organisation and the necessary role. Organisation, raw-report and forensic downloads use short-lived, single-use grants assigned to a user. If a link expires while the file remains available and permission continues, a new link can be requested. A link’s short validity period is not the retention period of the underlying data.

Ordinary account use is subject to the displayed retention periods for the module and plan. Standard availability of an organisation export file is configured for seven days; any validly agreed different period and the expiry shown in the application must be considered. Diagnostic originals and reports have separate retention periods. Data already lawfully deleted cannot subsequently be exported.

For a statutory switch, Sendequelle arranges secure availability of the remaining data covered by the switch independently of ordinary download time limits. The transition is governed by section 13 of the Terms and Conditions; after the transition ends, the covered exportable data remain available for retrieval for at least 30 calendar days. Necessary preservation and coordination with automatic deletion periods are arranged for the individual request. This does not describe a complete automated data-hold process as an account function.

After successful switching and expiry of the retrieval period, or following valid termination without switching, the agreed deletion is performed. Statutorily required residual retention remains limited to its respective purpose. For affected backup copies, the scope, limited continuing need and removal date are communicated during the individual process. This page does not claim that a uniform technical backup cycle has been established and grants no indefinite retention right.

Security and identity checks protect your data. They must not improperly prevent or delay a valid switch. Data belonging to other organisations, internal software and protected third-party secrets are not disclosed merely because an export is requested. This must not result in a blanket exclusion of data required within the legitimate scope.

6. Infrastructure and international governmental access requests

The Provider is Norbert Sehm, Sendequelle, Von-Möller-Str. 23a, 33649 Bielefeld, Germany. According to the operating arrangements specified for Sendequelle, the platform server is hosted by Hetzner Online GmbH in Falkenstein, Germany. This infrastructure is subject to German law and applicable European Union law. The skymail.de email service used for Sendequelle belongs to the same operator.

The application separates access between organisations through permission checks and keeps private originals and reports outside public result pages. Individual email originals used for forensic analysis and delivery diagnosis are stored encrypted; report contents stored for these functions are also processed or stored with encryption. This is not a blanket statement that every other platform record, log or backup is encrypted in the same way.

For governmental requests for access or disclosure, Sendequelle undertakes to examine jurisdiction, legal basis and scope, obtain necessary professional advice and refrain from a transfer contrary to European Union or national law merely because a foreign authority has requested it. Legally required objections and safeguards will be used. Where permitted, the affected customer will be informed; any legally required disclosure will be limited to what is necessary. These measures also concern non-personal customer data.

Confidentiality and processing on instructions are additionally governed by the relevant data processing agreement. This information replaces neither the conclusion of that agreement nor evidence of individual service provider agreements. It does not promise that every governmental access is legally or technically impossible.

Optionally selected DNS or registry lookups may send the domain names or public IP addresses required for the lookup to the relevant external services. Those lookups must be distinguished from storage of private platform data. The Privacy Notice explains other recipients and international processing routes where applicable to the particular function used.