Safe {Pro} Service Descriptions

These Service Descriptions explain, in plain language, what each Safe Pro service is and how it behaves. They are the Service Descriptions referenced in the Safe Pro Terms. They are descriptive only; the binding terms and disclaimers are set out in the Terms.

How these relate to the full commercial package

• Plan selection in the App, or your Order Form, sets the actual plan, price, limits and dates you accept.

• Terms cover the licence, liability, warranty, intellectual property and service disclaimers, and refer to each Service Description below.

• Service Descriptions describe what each feature is and how it behaves.

• Availability and support: availability is governed by the Uptime Target shown at plan selection, under the Terms. Support is described in the Professional support section below.

• Data Processing Agreement (DPA) covers data protection.

1. Safe accounts: setup, transactions & history

Summary. The baseline services for working with a self-custodial Safe Account through the Safe{Wallet} App: preparing and deploying an account, managing its configuration, assembling and coordinating transactions, and reading its onchain state and history. You hold your own keys and assets. Signing and basic execution do not depend on a subscription.

What it is

Safe Accounts are self-custodial smart-contract wallets. The Safe Account smart contracts are open-source software (LGPL-3.0) deployed on public blockchains and are not provided by Safe Labs. You provide and control the wallet or wallets used to sign transactions. Safe Labs does not hold your Recovery Phrase, Private Keys or Tokens, and cannot move or freeze your assets. These baseline services help you create and operate a Safe Account. They do not take custody of it.

How it works

• Account preconfiguration and deployment. The Safe{Wallet} App assembles the deployment transaction for a new Safe Account with the parameters you choose, such as the initial signer set and the signature threshold. You sign and broadcast the deployment transaction yourself from your wallet. Safe Labs does not deploy on your behalf. Creating a Safe Account does not require a plan and is not counted against Plan Limits.

• Configuration management. You can assemble transactions that add or remove Signer Wallets, change the signature threshold, and enable, disable or interact with Modules and Guards. These changes take effect once you execute them onchain and reflect the onchain state of your Safe Account.

• Transaction preparation and signature coordination. The app builds single and batched transactions, holds transactions offchain while the signatures required by your account's threshold are collected, and propagates collected signatures between signers. A transaction takes effect only once it meets your account's threshold and is executed onchain.

• Onchain indexing and history. The app reads the onchain state of the Safe Accounts you access and presents their executed transaction history, sourced from the Blockchain.

Non-custodial by design

• You do not depend on these services to reach your Safe Accounts. A Safe Account can also be used through third-party wallet providers with your Recovery Phrase and Private Keys.

• Signing and basic execution of transactions do not require a subscription. Every Safe Account is fully operable standalone through its signers' own wallets, without a Workspace or plan.

• On termination or expiry of any plan, and during any lock of a Workspace, you keep full access to your Safe Accounts and any Tokens on the relevant Blockchain using your Recovery Phrase and Private Keys. What ends is access to the paid services, never control of your accounts or assets.

• Offchain Workspace data is a separate matter from onchain access. Where a plan ends, the Safe Pro Terms set out the period during which you can still export that data.

Coverage & limitations

• All transactions are signed by you. Safe Labs does not monitor authorised transactions and does not check the correctness or completeness of a transaction before you authorise it.

• Transactions on a Blockchain are irreversible once executed.

• Safe Labs does not recover Safe Accounts and does not hold a back-up of your Recovery Phrase or Private Keys.

2. Workspaces & the organisational layer

Summary. A Workspace is the organisational layer that lets a team administer multiple Safe Accounts, Members and shared organisational data in one place. It is the layer that plans and Plan Limits attach to. Workspace features govern access to organisational data within the Safe{Wallet} App and do not change the onchain permissions of any Safe Account.

A Workspace is not part of the standalone Safe Account experience. A standalone Safe Account is always fully operable without one.

How it works

• A Workspace groups Safe Accounts, Members and shared organisational data such as the Shared Address Book and roles. A Workspace is normally set up for one organisation.

• Safe Seats are slots for Safe Accounts on a plan. A Workspace can hold more Safe Accounts than it has seats; accounts beyond the seat count move to an over-seat state (below). A seat is a slot for a Safe Account. Seats do not count people. A Safe Account deployed at the same address on several Blockchains counts as one Safe Account against your seats, regardless of how many networks it is deployed on.

• Members are people with app access to a Workspace. A Member is not necessarily an onchain signer. Signers are not counted against seats and are not charged. A signer can sign a Safe Account from its standalone view without being a Member of the Workspace.

• Supporting Workspace features include role assignment (such as proposer), nested Safe support, Workspace 2FA, and the Shared Address Book.

Seats and over-seat behaviour

• Creating a Safe Account is not blocked at the seat limit. At the seat limit, the app offers an upgrade path or the option to create the account outside the Workspace.

• In the over-seat state (for example after a downgrade, or where Plan Limits are introduced or lowered and a grandfathering period ends), the Safe Accounts above the seat count move to a free standalone state. They leave the Workspace layer and its organisational features, such as the Security Hub, and continue to work as standalone Safe Accounts. The rest of the Workspace is unaffected and keeps working normally. The Workspace returns to normal when it is back within its seat limit, either by moving to a plan with more seats or by removing Safe Accounts from the Workspace.

• Your Safe Accounts are not affected in substance. Every Safe Account continues to show its name, address and balance, and stays fully usable in its standalone view with the same signers and threshold. Removing a Safe Account from a Workspace does not touch the Safe Account itself. Neither the account nor its onchain state is deleted.

• Exceeding a limit does not create a payment obligation by itself. Additional fees arise only where a fee is displayed to you and you confirm it.

Introduction or lowering of limits; temporary grandfathering

• In this section, your free period is the period during which your Workspace is not yet on a paid plan, and the snapshot is the point at which new or lowered limits take effect. Where Plan Limits are introduced or lowered, an existing Workspace already above the new limits is frozen rather than stripped for the duration of that Workspace's free period only: the Safe Accounts, Members and features already in use at the snapshot are retained during the free period, and only new additions are subject to the new limits during that time.

• This grandfathering is temporary. When the Workspace's free period ends, the Plan Limits of the plan chosen by the customer apply in full, and the over-seat behaviour described above applies to anything then above those limits. No Safe Account is deleted, and every Safe Account remains fully operable standalone.

What it is not

• The Workspace layer controls access to organisational data within the Safe{Wallet} App only. It does not change the signers, threshold or onchain permissions of any Safe Account. Onchain control of each Safe Account remains with its signers.

• No lock, pause or expiry of a Workspace ever affects funds, signing rights or onchain access to any Safe Account.

3. Transaction risk indicators (Safe Shield)

Summary. Safe Shield provides informational, pre-execution indicators that give a team context on a transaction before it is signed: risk flags, recipient and contract context, and transaction simulation. The indicators are descriptive decision-support indicators, not a guarantee of safety.

How it works

• Safe Shield surfaces pre-execution indicators in the transaction flow: recipient context, context on any change the transaction would make to your Safe Account configuration (such as the mastercopy, signer set, threshold or enabled Modules), and contract context, including, where available, whether a contract's source code is verified on a public source.

• Risk scans provide the risk-scan component:

  • Basic threat analysis provides a risk flag, severity and a pass or fail result. It is available on every plan and outside any plan, including to users without a subscription.

  • Advanced components, such as contract checks, recipient checks and transaction simulation, are included where the plan you select in the App includes them.

• Some indicators rely on data and services provided by third parties, including data providers and public sources. Their availability and accuracy depend on those third parties. A third-party data source may be unavailable, delayed or withdrawn, in which case the indicators that depend on it are not shown.

Coverage & limitations

• The indicators are descriptive, not protective. No scanning, simulation or risk system detects every malicious, fraudulent, deceptive or otherwise harmful transaction, address, token, contract or counterparty.

• The absence of a flag or warning does not mean a transaction, address or contract is safe, legitimate or the one you intended. This includes address poisoning, address spoofing, look-alike addresses and impersonation.

• The indicators do not verify the off-chain identity, legitimacy, solvency or trustworthiness of any counterparty, and do not predict the onchain outcome of a transaction. A transaction simulation reflects a simulated state, not the state of the Blockchain at execution.

• You are responsible for checking any transaction, address, contract, signature request or counterparty you interact with, and for the decision to authorise or decline a transaction. The indicators support, and do not replace, your own review and diligence.

4. Security Hub

Summary. The Security Hub is a consolidated Workspace surface that shows a team's security posture across the Safe Accounts it operates.

How it works

• Presents security-posture information for supported accounts from one place within the Workspace.

• The Security Hub surfaces posture signals such as the signer set and threshold of each covered Safe Account, whether its mastercopy is current, which Modules and Guards are enabled, and whether contracts it interacts with are verified on a public source.

• Available in a Workspace. How much the Security Hub covers depends on the plan you select in the App.

• Requires a Workspace. It is not part of the standalone Safe Account experience. A Safe Account that has moved to the free standalone state because the Workspace is over its seat limit is not covered by the Security Hub while it is outside the Workspace.

Coverage & limitations

• The Security Hub is a posture-visibility surface, not a monitoring or incident-prevention service, and it does not guarantee prevention of any incident. It reflects the data available for supported accounts and networks.

• Basic safety indicators on individual transactions (risk flag, severity, pass or fail) are provided by Safe Shield and remain available to everyone regardless of plan; the Security Hub does not gate them.

• The Security Hub does not change the signers, threshold or onchain permissions of any Safe Account, and its unavailability never affects funds, signing rights or onchain access.

5. Enhanced execution: transaction relay

Availability. Enhanced Execution, including Transaction Relay, is available from its general release. Until then, transactions are executed by paying network gas from the signer's own wallet.

Summary. Transaction Relay broadcasts a transaction you have already signed and settles the network gas against the Safe Account itself, so individual signers do not each need to hold gas in their own wallets. Relay does not make a transaction free of gas. Relay is part of Enhanced Execution, is included only on plans that expressly include it (not on every paid plan), and is provided on a best-efforts basis.

How it works

• Basic execution means signing a transaction and submitting it from the signer's own wallet, paying network gas from that wallet. Basic execution is always available, does not depend on a subscription, and carries no Safe Labs per-transaction fee.

• Transaction Relay takes a transaction that has been validly signed to your Safe Account's threshold, broadcasts it to the Blockchain, and settles the network gas against the Safe Account rather than against the wallet of the signer who executes it. The relay broadcasts the transaction as signed. It cannot change what your signers approved: any change would invalidate the signatures and the transaction would be rejected onchain.

• Relay changes who pays the network gas, not whether it is paid. For transactions where no gas is charged to you at all, see Gas sponsoring (section 6); Gas Sponsoring is a separate service with its own quota and meter.

• Relay is part of Enhanced Execution and is included only where the customer's plan expressly includes it; it is not included on all plans and not on all paid plans. Where a plan includes relay, it covers the Safe Accounts covered by the plan and is not billed separately.

• Where a plan does not include relay, transactions are executed by paying gas from the signer's wallet. Once Enhanced Execution becomes generally available, plans that do not include relay are expected to be able to use it against a per-transaction Enhanced Execution Fee. Any such fee is displayed to you before you confirm the transaction and is charged only where you confirm it; basic execution does not carry it.

• The Enhanced Execution Fee is owed by the Customer. Where a Member confirms a transaction carrying the fee, the fee is owed by the Customer and never by that individual. The fee may be payable in cryptocurrency and collected by the relay provider that submits the transaction.

• Safe Labs may use subcontractors to provide the relay service.

Coverage & limitations

• Relay is best-efforts. There is no assurance that a transaction will be included in any specific block, within any specific time, or will succeed onchain once submitted. The onchain outcome depends on the state of the Blockchain at execution, including gas pricing, network congestion, maximal extractable value (MEV) and any reverts caused by the contracts the transaction calls.

• Network gas consumed by a transaction that reverts onchain is non-recoverable.

• Exceeding a fair-use or plan limit for relay never creates a payment obligation by itself; the sole consequence is that further relay may be declined for the remainder of the billing period.

• Relay does not change your ability to execute a transaction yourself at any time by submitting it from your own wallet and paying the network gas.

6. Gas sponsoring

Summary. Gas Sponsoring covers the network gas for eligible transactions, so a transaction can be executed without gas being charged to the Safe Account or to any signer. It is a metered feature with its own quota and spend controls. It is separate from Transaction Relay and is not part of Enhanced Execution.

How it works

• Where a plan includes Gas Sponsoring, eligible transactions are executed with the network gas covered, up to the monthly quota that applies under the plan. Some plans include sponsoring without a monthly quota.

• The quota applies to the Workspace as a whole, not per Safe Account and not per Member. The quota is a monthly quota. It resets at the start of each calendar month of your subscription term, on the same day of the month as your subscription start date; unused quota does not carry over.

• Sponsoring may also be subject to spend controls, such as a limit on the gas covered for any single transaction.

• When the quota is exhausted, or a transaction exceeds an applicable spend control, the transaction falls through to Transaction Relay (where the plan includes relay) or to paying gas from the signer's wallet. Where sponsoring is not applied, the app shows the fall-back route rather than failing the transaction silently. Exhausting the quota does not create a payment obligation by itself; additional sponsored capacity is available only where you order it and confirm the fee displayed to you.

• Remaining quota is shown to the customer in the app.

• Safe Labs may decline sponsoring for transactions that are abusive, automated at scale, or inconsistent with normal use of a Safe Account.

Coverage & limitations

• Gas Sponsoring covers network gas only. It does not cover separately priced third-party or partner services.

• Gas Sponsoring is distinct from Transaction Relay. Relay moves the network gas from the wallet of the signer to the Safe Account; sponsoring covers the gas so that neither pays it. Sponsoring runs on its own meter, separate from any relay limits. Sponsoring does not change the onchain outcome of a transaction.

• Eligibility can depend on the network and on the transaction. Where a transaction is not eligible, it remains executable by Transaction Relay (where included in the plan) or by paying gas from the signer's wallet; basic execution is always available.

7. Shared address book

Summary. The Shared Address Book lets a team maintain one organisation-managed list of counterparty addresses and names, visible across the Workspace, so that every Member transacts against the same, centrally maintained entries instead of each keeping a private list.

How it works

• Authorised Members maintain named entries (a label and a Blockchain address) at the Workspace level; entries are then available to Members across the Workspace when preparing transactions. Members with an administrator role can add, edit and delete entries; other Members can use them.

• Shared address-book entries are not counted against Plan Limits.

• The Shared Address Book can be exported by the customer at any time. Export remains available when a Workspace is locked, for the period set out in the Safe Pro Terms, so the customer keeps its counterparty list even where Workspace access has ended.

• Shared address-book entries are offchain Workspace data stored by the service.

• Address-book entries you create may include personal data of your counterparties. Where we process that data on your behalf, our Data Processing Agreement applies; it is available for signature at any time.

What it is not

• An address-book entry is a label created by your team. Safe Labs does not verify that an entry's address actually belongs to the named counterparty, and the Shared Address Book is not a screening, identity-verification or sanctions-checking service. The customer remains responsible for verifying counterparty addresses before transacting; Transactions on a Blockchain are irreversible once executed.

• The Shared Address Book does not restrict where a Safe Account can send funds. It is a convenience list, not an allowlist.

• The Shared Address Book is part of the Workspace layer. If the Workspace layer is paused, locked or terminated, access to the shared list through the Workspace ends (with the export option described above); funds, signing rights and onchain access to every Safe Account are never affected, and every Safe Account remains fully operable standalone. A personal address book remains available in the standalone Safe{Wallet} App experience, so you keep your own entries when the shared list goes.

8. Workspace 2FA

Summary. Two-factor authentication (2FA) on the Workspace adds a second verification step to a Member's login to the Workspace, so that access to the Workspace's organisational layer does not depend on a single credential. 2FA applies to access to the Workspace in the Safe{Wallet} App; it is separate from, and never replaces, the onchain signing security of a Safe Account.

How it works

• A Member enables 2FA for their Workspace login. From then on, signing in to the Workspace requires both the Member's login credential and a second factor. The supported second factors are an authenticator app (TOTP) and a passkey or hardware security key. SMS is not offered as a second factor.

• A Workspace administrator can require 2FA for all Members of the Workspace; otherwise each Member enables it individually.

• 2FA applies to Workspace access: the app-level login that gates the organisational layer (Members, the Shared Address Book and similar features). It does not apply to, and is not needed for, the onchain act of signing: signing a Transaction always requires the applicable Signer Wallets and the Safe Account's onchain threshold, with or without 2FA.

Coverage & limitations

• 2FA applies to the Workspace login. It does not protect, back up or recover Private Keys or Recovery Phrases, and it does not prevent transactions authorised by the required number of signers. A compromised Signer Wallet is not mitigated by Workspace 2FA.

• A second factor reduces, but does not eliminate, the risk of unauthorised access. Phishing, malware and compromise of the Member's device can defeat it.

• Members are responsible for keeping both their login credential and their second factor secure and available. If a Member loses their second factor, they can sign in using one of the recovery codes issued when 2FA was enabled. If no recovery code is available, a Workspace administrator can reset that Member's second factor. No recovery path touches Private Keys or Recovery Phrases, and no recovery path gives Safe Labs access to a Safe Account.

• Losing access to a second factor, or to the Workspace altogether, never affects funds, signing rights or onchain access to any Safe Account. Every Safe Account remains fully operable standalone through its signers' own keys.

9. Add-ons (partner products)

Summary. Add-Ons are third-party partner products offered from time to time that can be purchased on top of a plan and used with a Workspace. They are not part of any plan: each Add-On is bought separately through a sales-led process, at its own price and, where applicable, on the partner's own terms.

How it works

• Add-Ons are optional partner products integrated with the Workspace. They are supported only where the customer's plan supports Add-Ons.

• Add-Ons are sold on top of a plan. No Add-On, and no charge for one, ever arises without a separate, express order by the customer; nothing in a plan converts into an Add-On purchase automatically or by silence.

• Each Add-On has its own price and scope, stated in the order for that Add-On. Add-On fees are separate from plan Fees and from any Enhanced Execution Fee.

• Add-Ons are third-party products. The partner's own terms, service descriptions and privacy documentation govern the partner product.

• Safe Labs does not review, endorse, audit or warrant a partner product, and does not verify the results it produces.

• Using an Add-On requires making certain data available to the partner. Where you contract directly with the partner, the partner receives that data as an independent controller under its own terms and privacy notice, and not as our sub-processor; you decide whether to enable the integration.

Coverage & limitations

• The partner product is built and operated by the partner. Its functioning, availability, accuracy and results are those of a Third-Party Service; the contractual allocation of responsibility for Third-Party Services in the Safe Pro Terms applies.

• An Add-On (for example a monitoring or threat-detection product) does not guarantee the detection or prevention of any attack, loss or incident, and it does not change the signers, threshold or onchain permissions of any Safe Account.

• Where an Add-On depends on the Workspace, ending the Workspace layer (pause, lock or termination) can end access to the Add-On through the Workspace. Funds, signing rights and onchain access to every Safe Account are never affected. Because the Add-On is contracted with the partner, what happens to prepaid Add-On fees on downgrade, lock or termination of your Safe Pro plan is governed by your agreement with the partner; the refund provisions of the Safe Pro Terms apply to plan Fees only.

• Discontinuation of a partner product by the partner is addressed in the Safe Pro Terms (including the associated termination and refund mechanics), not in these Service Descriptions.

10. Professional support

Summary. Professional Support is the human support Safe Labs provides to Safe Pro customers: a defined way to reach us, target times for a first response, and, on plans that include it, a named contact and an escalation path. Support helps you use Safe Pro. It does not review, approve or execute your transactions, and it never touches your keys.

How it works

• Channels. Support is reached in the app and by email. Plans that include it also provide a shared channel.

• Who can raise a request. Requests are raised by Members of the Workspace with the applicable role.

• Support hours. Support is staffed on business days, 09:00–18:00 CET, excluding public holidays in Germany. Requests received outside support hours are picked up on the next business day.

• Target response times. Where your plan shows a target response time, it refers to the first substantive reply from a person, not to resolution. Where a plan states no target, we aim to respond to P1 within one business day, P2 within two business days and P3 within five business days.

• Priority. Safe Labs assigns priority from the reported impact: P1: the Workspace layer is unavailable to all Members, or a paid feature is unusable across the Workspace; P2: a paid feature is degraded or unavailable for some Members; P3: everything else, including questions and feature requests.

• Escalation and named contact. Plans that include it provide a named contact and an escalation path.

• Language. Support is provided in English.

What support covers

• Setting up and operating the Workspace, Members and roles; understanding how a feature behaves; investigating a suspected fault in the service; billing and plan questions; assistance with exporting your data.

What support is not

• Support does not review, verify, approve, sign or execute transactions, and does not advise on whether a transaction, address, contract or counterparty is safe or correct. Safe Shield indicators are decision support; the decision is yours.

• Support is not legal, tax, accounting, financial or investment advice.

• Safe Labs does not hold your Recovery Phrase or Private Keys, cannot recover a Safe Account, and cannot reverse a transaction once it has been executed onchain.

• Support does not cover third-party products (including Add-Ons, wallets, RPC providers or the Blockchain itself) beyond identifying that the issue lies there.

• Support is not a monitoring service. Safe Labs does not watch your accounts for you.

Coverage & limitations

• Response targets are operational targets, measured from receipt of a complete request in the applicable channel during support hours. A target does not run while a request is waiting on information from you, and a response target is not an availability commitment. Where a plan includes an availability target, that target is shown when you select the plan in the App and is governed by the Terms.

• Support does not need access to your Safe Accounts. Safe Labs will never ask you for a Recovery Phrase, Private Key or seed phrase. Any request that appears to come from Safe Labs and asks for one is not genuine.

11. Guided Onboarding

Summary. Guided Onboarding is a time-boxed, hands-on setup session run by Safe Labs for customers whose plan or Order Form includes it. We work with your team to set up the Workspace and bring your Safe Accounts and Members into it. Safe Labs owes careful performance of the session, not a particular result, and never takes control of your keys or your accounts.

How it works

• Scope. To the extent scoped in your plan or Order Form, Guided Onboarding covers: setting up the Workspace; adding the Safe Accounts it covers; adding Members and assigning roles; configuring Workspace features such as the Shared Address Book and Workspace 2FA; and support with migrating existing Safe Accounts and address-book data into the Workspace.

• Format and effort. Delivered remotely in one or more scheduled sessions, up to the number of hours stated in your plan or Order Form.

• Scheduling. Sessions are scheduled by agreement with your team and should be booked within sixty (60) days of the start of the paid term. Hours not used within that window lapse and are not refunded or credited.

• Who does what. Your team performs every action that requires your keys. Safe Labs guides, demonstrates and, with your authorisation, configures what can be configured at app level. Safe Labs does not sign, execute or broadcast transactions on your behalf, and does not receive or hold your Recovery Phrase or Private Keys.

What it is not

• Careful performance, not a result. Safe Labs owes careful, professional delivery of the onboarding. It does not owe a particular outcome, completion of a migration by a particular date, or that any specific configuration will suit your organisation.

• Not advice or an audit. Guided Onboarding is not security, legal, tax, accounting or treasury advice, and it is not a security audit, review or assessment of your setup, signer arrangements or key management.

• Not custody or administration. Safe Labs does not become a signer, administrator or operator of your Safe Accounts. Decisions about signers, thresholds, Modules and Guards remain yours.

• Not a transfer of assets. Onboarding brings accounts and Workspace data into the Workspace. It does not move Tokens between accounts. Any onchain transaction is prepared and executed by your own signers.

Coverage & limitations

• Delivery depends on scheduling with your team; any indicative timing assumes your team's reasonable availability and cooperation.

• Where onboarding is included in a plan or an Order Form, it is delivered once per subscription term unless stated otherwise.

• Where a subscription ends early, onboarding hours that have not been delivered lapse and are not refunded or credited separately; any refund of Fees is governed by the Safe Pro Terms.

12. Data export & end of subscription

Summary. What happens to your data when a Safe Pro subscription ends, is suspended or is downgraded: what stays onchain and is unaffected, what counts as offchain Workspace data, how to export it, and for how long export stays available. Nothing in this section affects control of your Safe Accounts or your assets.

The two kinds of data

• Onchain data. Your Safe Accounts, their signers and thresholds, their balances and their executed transactions live on public blockchains. This data is not held by Safe Labs, is not affected by the end of a subscription, and remains fully usable with your own keys through any interface, including third-party wallet providers.

• Offchain Workspace data. The data the service stores for the Workspace layer: Members and their roles, the Shared Address Book, Workspace settings, and transactions that have been proposed and signed but not yet executed. This is the data the export described below concerns.

Exporting your data

• You can export offchain Workspace data while your subscription is active.

• After your subscription ends, you may export your data for ninety (90) days, free of charge, in a common machine-readable format. After that period we may delete it.

• Export also remains available while your access is suspended, for example during a payment dispute.

• A downgrade does not trigger the export window. Where a downgrade moves Safe Accounts out of the Workspace layer because the Workspace is over its seat limit, those accounts continue to work standalone and nothing is deleted; the Workspace's own data stays where it is.

What export does not cover

• Export covers the offchain data the service stores for your Workspace. It is not a backup service and is not a substitute for your own record-keeping, including any statutory retention obligations of your own.

• Safe Labs never holds your Recovery Phrase, Private Keys or Tokens, so there is nothing to export and nothing to recover. Your access to your Safe Accounts does not depend on any of this.

• Data held by a partner under an Add-On is held by that partner on its own terms. See Add-ons (section 9).

After the export window

• Once the ninety (90) days have passed, Safe Labs may delete offchain Workspace data. Deletion cannot be reversed, so export before the window closes if you need the data.

• Billing records are kept separately for the statutory retention periods under German commercial and tax law, regardless of the export window.

Switching to another provider

• The export is designed so that you can take your offchain Workspace data with you. Safe Labs does not require you to keep a subscription in order to retrieve it, and does not charge for the export during the period above.

These Service Descriptions are descriptive only and do not form part of the contract. The plan you hold, and the limits and inclusions that apply to it, are those shown when you select your plan in the Safe{Wallet} App, or those set out in your Order Form. Capitalised terms not defined here have the meaning given in the Safe Pro Terms and the Safe Pro User Terms.