Exportable Data
This page lists the data of the Service that you can export, and the formats you receive it in. It is the list referred to in Section 14 of the Terms of Service ("Switching to another provider") and in the Privacy Policy. Capitalised terms have the meaning given in the Terms.
1. How to export
- Use Export your data in the account settings. You receive one ZIP archive. Each data file in it holds one JSON object per line (newline-delimited JSON, UTF-8), and a manifest file in JSON lists the files and the time of the export. Times are given in ISO 8601 format with their offset from UTC.
- The Account Owner receives the Account's data (Sections 2 and 3) and their own personal data (Section 4). An Authorised User receives their own personal data only (Section 4).
- The self-service export can be used once every thirty days, except during a switch to another provider and the retrieval period that follows it, and on the page where the Account Owner confirms closing the Account; in those cases the thirty-day limit does not apply, and the export can be used again five minutes after the previous one. If you need an export sooner, contact us at contact@byteimagination.com and we provide it without undue delay and within thirty days, for as long as the data exists.
2. Data of the Account
- Users of the Account — the email address and role of the Account Owner and of every Authorised User, and the date each joined.
- API Keys of the Account — for each key: its visible prefix, its label, whether it is active, and when it was created, revoked and last used. The key itself is never included.
- Subscriptions — the plan, the status and the dates of each Subscription of the Account.
- API usage records — for each authenticated API request of the last 365 days: when it was made, the visible prefix of the API Key used, the IP address and the user agent.
- API request logs and usage counters — logs of API requests (kept for 30 days) and quota and rate-limit counters are not in the self-service archive; we provide them on request at contact@byteimagination.com without undue delay and within thirty (30) days, for as long as we hold them. A request about your own personal data can also be sent to privacy@byteimagination.com under Art. 15 GDPR, which has its own time limit of one month.
3. Data of the Service
- Sources — for each source: its identifier in the archive, its slug, its display name, whether it is enabled, its grouping setting, and when it was deleted, if it was.
- Connections — for each connection to a system you operate: its display name, its kind, its address, whether it is enabled, and when it was deleted, if it was. The credential is not included: it is stored write-only and never displayed again, and you have it from when you entered it.
- Destinations — for each destination: its display name, its kind, whether it is enabled, its configuration, when it was last verified, and when it was deleted, if it was.
- Issue groups — for each group of related error reports: its source (by its identifier in the archive and its slug), its grouping fingerprint, its title, severity and status, how many reports it holds, and when the first and the last were seen.
- Error reports — for each report: its identifier in the archive, its source (by its identifier in the archive and its slug), its grouping fingerprint, its title and severity, the exception type, the environment and release you tagged it with, when it occurred and was received, and its content for as long as we still hold it (see the Privacy Supplement), and, for 365 days, the IP address from which it was sent.
- Recipients — each email address you nominated as a recipient, and whether the recipient has confirmed it, declined, or not answered yet.
- Deliveries — for each report and destination: the outcome of the delivery and, for a delivered report, when it was delivered.
4. Your personal data
- your account details — email address, role, and when your user account was created and your email address was verified;
- your records of accepting legal documents — the document, its version, when and how you accepted it, and the language shown to you;
- the API Keys you created, described as in Section 2;
- no list of your actions, because the Service does not record which user performed an action.
5. What is not included
- API Keys and their cryptographic hashes, password hashes, and the single-use tokens sent in emails — these are credentials that secure the Service, not data generated by your use of it;
- billing details held by our payment processor as Merchant of Record — you can obtain your invoices and payment records from Paddle;
- records of the emails we sent and of their delivery, support correspondence and marketing consent records. We provide them on request at privacy@byteimagination.com where they contain your personal data (Art. 15 GDPR);
- the IP addresses and user agents attached to accepted legal documents, which you can request in the same way;
- the records we keep, as controller towards your recipients, of why we stopped sending to an address (see the Privacy Supplement), and the records of individual attempts within one delivery.
6. Switching to another provider
How to start a switch, how long it lasts, and how long you can still retrieve the data afterwards is set out in Section 14 of the Terms of Service. We do not charge for switching.
7. Where the data is held
The data of the Service is stored on the infrastructure of DigitalOcean, LLC in Germany (Frankfurt / FRA1 region), under a contract that includes the EU Standard Contractual Clauses. The database storage is encrypted at rest by DigitalOcean, LLC at the level of the storage volume. Backup copies are stored with rsync.net, Inc. in the United States (Fremont, California); they are encrypted on our server before they are sent, with a passphrase that only we hold, so rsync.net stores only encrypted data. Data is encrypted in transit. Credentials you supply for external systems are additionally encrypted in the database with a key that we manage. Only named accounts of our personnel have access to the systems. Emails we send pass through Resend, Inc. (United States), and payments are handled by Paddle in the United Kingdom. Because DigitalOcean, LLC and rsync.net are incorporated in the United States, they may be subject to requests from US authorities; a request to rsync.net can disclose only the encrypted backup copies. The measures above reduce but do not exclude that possibility.
8. Files and fields in the archive
This section lists every file in the archive and the fields of each line in it. The files under organization/ hold the data described in Sections 2 and 3 and are in the Account Owner's archive only. The files under personal/ hold the data described in Section 4 and are in every archive. A field without a value is given as null.
manifest.json
The manifest. Unlike the other files, it holds a single JSON object.
| Field | Type | Meaning |
|---|---|---|
schemaVersion | text | The version of the archive format. |
exportedAt | date and time | When the export was made. |
tool | text | The name under which the Service identifies itself in the archive. |
username | text | The email address of the user who made the export. |
parts | list of text | The parts the archive holds: organization, personal, or both. |
entries | list of text | The data files in the archive. |
organization/members.ndjson
Users of the Account (Section 2), one line per user.
| Field | Type | Meaning |
|---|---|---|
email | text | The user's email address. |
role | text | OWNER for the Account Owner, MEMBER for an Authorised User. |
joinedAt | date and time | When the user joined the Account. |
organization/api-keys.ndjson
API Keys of the Account (Section 2), one line per key.
| Field | Type | Meaning |
|---|---|---|
keyPrefix | text | The visible prefix of the key. |
label | text | The label given to the key. |
active | true or false | Whether the key can be used. |
createdAt | date and time | When the key was created. |
revokedAt | date and time | When the key was revoked, if it was. |
lastUsedAt | date and time | When the key was last used, as shown by the API usage records. |
organization/subscriptions.ndjson
Subscriptions (Section 2), one line per Subscription.
| Field | Type | Meaning |
|---|---|---|
plan | text | The plan of the Subscription. |
status | text | The status of the Subscription, such as ACTIVE, PAST_DUE or CANCELED. |
createdAt | date and time | When the Subscription was recorded. |
currentPeriodStart | date and time | When the current billing period started. |
currentPeriodEnd | date and time | When the current billing period ends. |
pastDueSince | date and time | Since when a payment has been overdue, if one is. |
suspendedAt | date and time | When the Subscription was suspended, if it was. |
canceledAt | date and time | When the Subscription was cancelled, if it was. |
organization/api-usage.ndjson
API usage records (Section 2), one line per authenticated API request of the last 365 days.
| Field | Type | Meaning |
|---|---|---|
usedAt | date and time | When the request was made. |
keyPrefix | text | The visible prefix of the API Key used. |
ipAddress | text | The IP address the request came from. |
userAgent | text | The user agent sent with the request. |
organization/nuntio-sources.ndjson
Sources (Section 3), one line per source.
| Field | Type | Meaning |
|---|---|---|
id | number | The identifier of the source, used as sourceId in organization/nuntio-issue-groups.ndjson and organization/nuntio-reports.ndjson. |
slug | text | The slug of the source, as used in the address reports are sent to. A deleted source may share its slug with a later one; id tells them apart. |
displayName | text | The display name of the source. |
enabled | true or false | Whether the source is enabled. |
fingerprintFrameCount | number | The grouping setting: how many stack frames identify an error. |
deletedAt | date and time | When the source was deleted, if it was. |
organization/nuntio-connections.ndjson
Connections (Section 3), one line per connection. The credential is not included.
| Field | Type | Meaning |
|---|---|---|
displayName | text | The display name of the connection. |
kind | text | The kind of system it connects to. |
baseUrl | text | The address of that system. |
enabled | true or false | Whether the connection is enabled. |
deletedAt | date and time | When the connection was deleted, if it was. |
organization/nuntio-targets.ndjson
Destinations (Section 3), one line per destination.
| Field | Type | Meaning |
|---|---|---|
id | number | The identifier of the destination, used in organization/nuntio-deliveries.ndjson. |
displayName | text | The display name of the destination. |
kind | text | The kind of destination. |
enabled | true or false | Whether the destination is enabled. |
config | JSON object | The configuration of the destination. |
lastVerifiedAt | date and time | When the destination was last verified. |
deletedAt | date and time | When the destination was deleted, if it was. |
organization/nuntio-issue-groups.ndjson
Issue groups (Section 3), one line per group.
| Field | Type | Meaning |
|---|---|---|
sourceId | number | The id of the source of the group in organization/nuntio-sources.ndjson. |
source | text | The slug of the source of the group. A deleted source may share its slug with a later one; sourceId tells them apart. |
fingerprint | text | The grouping fingerprint. |
title | text | The title of the group. |
severity | text | The severity of the last report in the group. |
status | text | The status of the group. |
occurrenceCount | number | How many reports the group holds. |
firstSeenAt | date and time | When the first report was seen. |
lastSeenAt | date and time | When the last report was seen. |
organization/nuntio-reports.ndjson
Error reports (Section 3), one line per report.
| Field | Type | Meaning |
|---|---|---|
id | number | The identifier of the report, used in organization/nuntio-deliveries.ndjson. |
sourceId | number | The id of the source of the report in organization/nuntio-sources.ndjson. |
source | text | The slug of the source of the report. A deleted source may share its slug with a later one; sourceId tells them apart. |
fingerprint | text | The grouping fingerprint. |
title | text | The title of the report. |
severity | text | The severity of the report. |
exceptionType | text | The exception type. |
environment | text | The environment you tagged the report with. |
releaseName | text | The release you tagged the report with. |
occurredAt | date and time | When the error occurred. |
receivedAt | date and time | When the report was received. |
payload | JSON object | The content of the report, or null once it is no longer held (see the Privacy Supplement). |
ipAddress | text | The IP address the report was sent from, for 365 days; null after that or when there was none. |
organization/nuntio-recipients.ndjson
Recipients (Section 3), one line per email address you nominated.
| Field | Type | Meaning |
|---|---|---|
email | text | The email address. |
status | text | CONFIRMED if the recipient confirmed it, DECLINED if the address no longer receives notifications, or PENDING if the recipient has not answered yet. |
organization/nuntio-deliveries.ndjson
Deliveries (Section 3), one line per report and destination.
| Field | Type | Meaning |
|---|---|---|
reportId | number | The id of the report in organization/nuntio-reports.ndjson. |
targetId | number | The id of the destination in organization/nuntio-targets.ndjson. |
outcome | text | DELIVERED, FAILED, SUPPRESSED (not sent, because of throttling or muting), or PENDING (not settled yet). |
deliveredAt | date and time | When the report was delivered, if it was. |
personal/account.ndjson
Your account details (Section 4), one line.
| Field | Type | Meaning |
|---|---|---|
username | text | Your email address. |
role | text | Your role in the Account: OWNER or MEMBER. |
accountCreatedAt | date and time | When your user account was created. |
emailVerifiedAt | date and time | When your email address was verified. |
personal/legal-acceptances.ndjson
Your records of accepting legal documents (Section 4), one line per accepted version.
| Field | Type | Meaning |
|---|---|---|
document | text | The document you accepted. |
version | text | The version you accepted. |
acceptedAt | date and time | When you accepted it. |
method | text | How you accepted it: SIGNUP when you created your user account, EXPLICIT_UPDATE on the acceptance page, or IMPLICIT_MIGRATION when it was recorded for a user account that existed before the document was first published. |
locale | text | The language the document was shown in. |
personal/api-keys.ndjson
The API Keys you created (Section 4), one line per key.
| Field | Type | Meaning |
|---|---|---|
keyPrefix | text | The visible prefix of the key. |
label | text | The label given to the key. |
active | true or false | Whether the key can be used. |
createdAt | date and time | When the key was created. |
revokedAt | date and time | When the key was revoked, if it was. |
lastUsedAt | date and time | When the key was last used, as shown by the API usage records. |
personal/activity.ndjson
This file is always empty: the Service does not record which user performed an action (Section 4).