Terms of use

Section 1 Scope and contracting party

(1) These Terms govern the use of miphu: the apps for iPhone, iPad and Mac and the services SwiftLabs operates for them, including the interface for AI apps.

(2) The provider and contracting party is

SwiftLabs UG (haftungsbeschränkt)Schanzenstraße 19, 90478 Nürnberg, GermanyCommercial register: Amtsgericht Nürnberg, HRB 46502represented by its managing director Felix StraubPhone: +49 911 49529681 · Email: hello@miphu.com
("SwiftLabs")

(3) These Terms have three parts. Part A applies to everyone. Part B governs the contract with the Customer. Part C governs the licence for the apps and the terms Apple requires for distribution through the App Store; it applies to every user of the apps. Annex 1 (exportable data) and the data processing agreement form part of these Terms. The information under Art. 26 of Regulation (EU) 2023/2854 (Data Act) is on the page named in section 11(7).

(4) The Customer's own general terms and conditions do not apply, even if SwiftLabs does not expressly object to them.

(5) For companies with more than 50 accesses, SwiftLabs concludes a separate contract. Where it deviates from these Terms, it prevails.

Section 2 Definitions

• Customer: the company for which a company account exists in miphu.
• Owner: the person who purchases the Subscription for the Customer and holds the company account as owner.
• Administration: Users to whom the Customer has given the role "Verwaltung" (Administration) in miphu.
• User: every natural person with an access to miphu, including the Owner.
• Access: a User's personal sign-in to a company account.
• Customer Data: all content that the Customer or its Users enter into, upload to or create with miphu, for example customers, contacts, quotes, invoices, receipts, personnel data, shift plans and working times.
• Subscription: the auto-renewable subscription for miphu purchased on Apple's App Store, including a free trial under section 6.
• Data Export: the archive of all exportable Customer Data under section 11(1).
• Apple: Apple Inc. and its affiliates that operate the App Store.

Section 3 Businesses only

(1) miphu is offered exclusively to businesses (Unternehmer within the meaning of section 14 of the German Civil Code, BGB), legal entities under public law and special funds under public law. Outside Germany, this applies correspondingly to persons acting in the course of their trade, business or profession when entering into the contract. Consumers cannot enter into a contract for miphu.

(2) Whoever purchases the Subscription for a company confirms that they act for a business and are authorised to represent it in entering into this contract.

(3) SwiftLabs may at any time request proof of business status, for example a register extract, a trade registration or a VAT identification number. If it is not provided within 14 days, SwiftLabs may terminate the contract under section 20(3).

(4) Rights that Apple grants purchasers on the App Store under its own terms remain unaffected (section 7(2)).

Section 4 Services

(1) SwiftLabs provides miphu to the Customer as software for use over the internet. The scope of functions follows from the description in the app and on miphu.com/features current at the time the contract is concluded.

(2) miphu is not accounting software, not payroll and not legal or tax advice. Functions such as electronic invoicing, the export in DATEV format, time recording and hints on working-time limits are tools. They do not replace review by the Customer or its advisers (section 13). Hints shown by miphu are not complete and are not a legal assessment.

(3) miphu requires an internet connection and a supported Apple device running a supported operating system version.

(4) SwiftLabs develops miphu further and may change, add or replace functions, provided the functions essential to the contract are preserved and the change is reasonable for the Customer. If a function essential to the contract is removed, SwiftLabs announces this in text form at least 30 days in advance.

Section 5 Account, company account and accesses

(1) Every User needs their own Access. The information given at sign-up must be accurate.

(2) An account belongs to exactly one company.

(3) The Owner and Users authorised by the Customer create Accesses, assign roles and rights and deactivate Accesses. A User's title, rank and department grant no rights.

(4) The Customer decides who receives an Access and keeps Accesses up to date, in particular when employees leave. Credentials must be kept secret and must not be shared. The Customer ensures that its Users comply with these Terms.

(5) The app does not provide for a change of Owner.

Section 6 Trial period

(1) A Subscription may start with a free trial of 30 days that Apple grants as an introductory offer on the App Store. Whether the trial is offered and who receives it follows the rules of the App Store; the App Store shows it before purchase. SwiftLabs grants no trial of its own.

(2) The trial is part of the Subscription. Unless the Subscription is cancelled in time before the trial ends, in the subscription settings of the Apple Account, it converts into the paid Subscription under the rules of the App Store.

(3) Customer Data entered during the trial is real data. The contract and the data processing agreement apply from the creation of the company account (section 20(1)). If the Subscription ends during the trial, section 8 applies.

Section 7 Subscription and payment through Apple

(1) Use requires a Subscription that the Owner purchases in the app through the App Store before the company account is created (section 20(1)). There is no company account without a Subscription. Packages are available for 1, 5, 10, 25 and 50 Accesses. Each Subscription period lasts one month; there is no annual term. The price shown by the App Store in local currency before purchase applies.

(2) Apple handles purchase, payment, invoicing, renewal, cancellation and refund of the Subscription under the Apple Media Services Terms and Conditions. SwiftLabs receives no payment data and can neither cancel nor refund subscriptions. Refunds are requested from Apple, which decides on them.

(3) The Subscription renews every month until it is cancelled in the subscription settings of the Apple Account. Cancellation takes effect at the end of the current billing period; miphu remains usable until then. Deleting the company account or the app does not cancel the Subscription.

(4) Every active Access counts, including the Owner's. Deactivated Accesses do not count. A new Access requires a free place in the package. Employees purchase nothing and need no access to the Owner's Apple Account.

(5) The package can be changed in the app or in the subscription settings of the Apple Account. When a change takes effect follows the rules of the App Store. If, after a change, the Customer has more active Accesses than places, nobody is deleted and no data is lost. Until surplus Accesses are deactivated or a larger package is purchased, all Users can read data but not change it.

(6) Price changes for existing subscriptions are handled through the App Store. Apple informs about an increase and obtains consent where this is required.

(7) If Apple cannot bill a renewal, miphu remains usable during a grace period granted through Apple.

Section 8 End of paid use and lock

(1) If the Subscription ends, including during the trial, for example through cancellation, an unresolved billing problem after a grace period granted through Apple, a refund or a revocation by Apple, the company account is locked. Users other than the Owner, including the Administration, can then no longer use miphu, not even to read or clock in; connected AI apps receive no more data. These Users see a notice that the Subscription has expired and can sign out and delete their own account (section 12(1)).

(2) During the lock, the Owner can still sign in and exclusively

1. purchase a package or restore an existing Subscription,
2. create and download a Data Export (section 11(1)), and
3. delete their account and with it the company account (section 12(2)).

The Owner cannot work with the Customer Data.

(3) After the Subscription ends, Customer Data is retained for 90 calendar days, but at least for 30 calendar days after the email under sentence 2, and can be exported under subsection 2 during that time. SwiftLabs informs the Owner by email that the Subscription has ended and reminds the Owner by email again before this period expires, the last time 7 days before. When the period expires, the company account is locked for all Users and kept for 30 calendar days as after a deletion by the Owner (section 12(3)); the Customer Data is then deleted under section 12(4) and (5). The Owner's account remains.

(4) If the Owner purchases a package before the period ends, the lock is lifted and the Customer Data is available unchanged.

Section 9 Availability, maintenance and support

(1) SwiftLabs operates miphu with the care of a prudent businessperson. SwiftLabs does not commit to a specific availability unless separately agreed.

(2) SwiftLabs schedules planned maintenance for periods of low use where possible. Urgent security measures may be taken without notice.

(3) SwiftLabs is not responsible for disruptions caused outside its sphere of control, in particular on the internet outside the data centres used by SwiftLabs, at Apple, at connected AI apps or on the Customer's devices.

(4) Support is available by email to hello@miphu.com in German and English.

Section 10 Customer Data

(1) Customer Data belongs to the Customer. SwiftLabs acquires no rights to it beyond what is necessary to provide miphu. SwiftLabs does not use Customer Data for its own purposes, does not sell it and does not use it to train AI models.

(2) SwiftLabs processes personal data contained in Customer Data on the Customer's behalf under the data processing agreement (binding German version at miphu.com/de/avv). The Owner concludes it for the Customer together with this contract (section 20(1)).

(3) The Customer is responsible for being permitted to process the Customer Data in miphu, in particular for the legal basis and for informing the data subjects, such as its customers, contacts and employees.

(4) SwiftLabs backs up the database continuously in order to restore the service after an incident. Backups are deleted after no more than 90 days (section 12(5)). The backups are not intended for recovering individual entries the Customer has deleted or changed.

Section 11 Export, switching and retention

(1) The Customer can download all exportable data listed in Annex 1 at any time, itself and free of charge, using the app's Data Export, in a structured, commonly used and machine-readable format (Art. 30(5) Data Act). The following applies:

1. Content and format. The Data Export is a ZIP archive. It contains every dataset under Annex 1 Part 1 as JSON and as CSV, the associated files, such as issued PDF and XML files, receipts, profile photos and DATEV files, a JSON Schema per dataset and a manifest with the SHA-256 checksum of every entry and the list of what is excluded (Annex 1 Part 2). The format is described in the register under subsection 7.
2. Who may export. The Data Export can be created and downloaded by the Owner, including during a lock under section 8, and, while the Subscription runs, by Users of the Administration who also hold the sales and finance rights. A Data Export created by a User of the Administration does not contain the Subscription data. Other Users and connected AI apps cannot create a Data Export.
3. Provision. The Data Export is created in the background. When it is ready, the User who started it receives an email with a link into the app; the email contains no Customer Data and no file. The finished Data Export can be downloaded for seven days; SwiftLabs then deletes the file.
4. Repetition. As long as the Customer Data exists, a new Data Export can be created at any time, one at a time and no more than five per company account within 24 hours.
5. Other exports. The individual export functions of the app remain available, for example issued invoices as PDF and XML and the export in DATEV format.

If the Data Export cannot be used in the app, for example because an archive exceeds the technical size limit, SwiftLabs provides the exportable data free of charge on request in text form by a secured route, not as an email attachment.

(2) The Customer may at any time request in text form to switch to another provider or to its own infrastructure, or to have its exportable data erased. There is no notice period for initiating the switch. When notifying a switch, the Customer names the new provider where necessary.

(3) After the request, a transitional period of no more than 30 calendar days applies. During it, SwiftLabs

1. provides reasonable assistance to the Customer and third parties authorised by it in the switching process and provides the relevant information,
2. continues to provide the contractual services with due care,
3. provides information on known risks to the continuity of the services, and
4. maintains a high level of security, including during the transfer of the data.

If the transitional period is technically unfeasible, SwiftLabs notifies the Customer within 14 working days of the request, gives reasons and indicates an alternative period of no more than seven months. The Customer may extend the transitional period once for a period of its choosing. The Data Export under subsection 1 remains available to the Owner during the transitional period and the retrieval period, even if the Subscription ends during that time.

(4) The transitional period is followed by a retrieval period of at least 30 calendar days during which the Customer can retrieve its exportable data.

(5) The contract is deemed terminated

1. upon successful completion of the switch, or
2. upon receipt of the request, if the Customer does not wish to switch but to have its data erased; section 12 then applies.

SwiftLabs notifies the Customer of the termination. In the case of item 1, after the retrieval period all exportable data and digital assets generated by the Customer or relating directly to it are fully erased under section 12(4) and (5).

(6) SwiftLabs charges no fees for switching.

(7) SwiftLabs describes the data formats, data structures and standards of the exportable data in an up-to-date online register at miphu.com/data-formats (Art. 26 Data Act).

(8) miphu is not an archive for the Customer's statutory retention obligations. Records the Customer must retain, for example under section 147 of the German Fiscal Code (AO), section 257 of the German Commercial Code (HGB), section 16(2) of the Working Hours Act (ArbZG) or section 17 of the Minimum Wage Act (MiLoG), are exported and stored by the Customer itself, at the latest before the contract ends or before deletion. After deletion, SwiftLabs does not keep Customer Data for the Customer.

(9) If a tax authority requests access under section 147(6) AO to Customer Data held by SwiftLabs, SwiftLabs supports the Customer.

Section 12 Deletion

(1) Every User can delete their account in the app, including during a lock under section 8. They confirm the deletion with their password. Their Access ends immediately: sessions, AI app connections and open sign-in links end, and their access to company accounts is deactivated. SwiftLabs confirms the deletion by email to the previous address and states the day of final deletion.

(2) If the Owner deletes their account, the company account is closed at the same time. The Owner additionally confirms this by entering the exact company name. The Access of all of the Customer's Users ends immediately, and all AI app connections are revoked. This does not end the Subscription with Apple; the app points this out and links to the subscription settings (section 7(3)). An Owner holding more than one company account deletes through hello@miphu.com. Before deletion, the Customer exports the Customer Data it needs (section 11(1) and (8), section 13(4)).

(3) After deletion, SwiftLabs keeps the account and, in the case of subsection 2, the Customer Data unchanged and locked for all Users for 30 calendar days. Within this period, the deletion can be reversed on request to hello@miphu.com. The User then signs in with their previous password; ended sessions and AI app connections stay ended. For the Owner, the company account and the Accesses the deletion deactivated are restored. SwiftLabs enables a Data Export within this period by reversing the deletion on request; the Owner can delete the account again afterwards.

(4) After the 30 days, SwiftLabs automatically deletes

1. in the case of subsection 2, all Customer Data of the company account, including invoices, quotes and receipts, and the company's name, address, tax and bank details, and
2. the account's email address, password and profile photo, and in the case of subsection 2 also its name.

What remains is an entry of the company account without these details, the account without the details under item 2 that entries the User created in other company accounts refer to, and the records under subsection 7.

(5) Backups are deleted after no more than 90 days. Data deleted under subsection 4 is therefore finally deleted no later than 90 days after the end of the 30-day period under subsection 3, that is no later than 120 days after the deletion in the app. Until then it is protected against access in the backups and used only to restore the service as a whole.

(6) If a User who is not the Owner deletes their account, entries they created for the Customer and data the Customer keeps about them, such as personnel data, shift plans, working times and entries in the change log, remain Customer Data of the Customer. They continue to carry the User's name after subsection 4 too.

(7) Records SwiftLabs keeps for its own purposes are not affected by deletion: the acceptances of these Terms and of the data processing agreement with version and time, the records of App Store subscriptions and payments for its own bookkeeping, and the record of the deletion with its final deletion date.

Section 13 Customer obligations

(1) The Customer checks invoices, quotes and exports for correct content and tax treatment before using them, in particular tax rates, exemptions and mandatory particulars. miphu validates electronic invoices against the technical validation rules, not the tax treatment.

(2) If the Customer uses shift planning or time recording, it is responsible as employer for compliance with working-time law, for involving a works council, for informing its employees about the processing of their data, and for whether and how it records absences such as sickness in miphu.

(3) The Customer keeps the devices, operating systems and apps its Users use for miphu up to date and protects them against unauthorised access.

(4) The Customer regularly exports the Customer Data it needs for its own purposes or retention obligations.

(5) The Customer notifies SwiftLabs without undue delay if it notices misuse of Accesses or a security vulnerability.

Section 14 Connecting AI apps

(1) Users can connect AI apps of other providers, for example Claude or ChatGPT, to miphu. A connection only comes into existence through the User's express approval with their own Access. Through the connection, the AI app can only read what the User may see in miphu and selected when approving. It cannot change anything. The connection does not release personnel master data, files, credentials, bank details, payment methods or individual recorded payments.

(2) The Owner can switch off connections for the entire company. Every connection can be revoked in miphu at any time.

(3) What the AI app reads is received by its provider. The provider processes it under its own terms and according to the settings of the account the User holds with it, including whether content is used for training. The contract for the AI app exists between the User or Customer and that provider. SwiftLabs is not a party to it and is not responsible for the provider's processing, availability or results.

(4) The Customer decides whether its Users may connect AI apps. It is responsible for the lawfulness of the transfer to the AI app's provider, for the contracts with that provider and for informing the data subjects.

(5) Answers from an AI app may be wrong. The Customer checks them before relying on them.

(6) For each call, SwiftLabs logs time, duration, result, User, company, app, tool and the number of records transmitted, but not search terms or content, and deletes these logs after 90 days. The Data Export contains the existing logs (Annex 1).

Section 15 Usage rules

The Customer and its Users must not

1. use miphu for unlawful purposes or to process data without a legal basis,
2. use it to infringe third-party rights or to distribute malware,
3. probe it for vulnerabilities, load-test it, or circumvent security and rights systems, capacity limits or request limits, without SwiftLabs' prior consent in text form,
4. access it automatically by any means other than the apps and the interfaces provided by SwiftLabs,
5. make it available to or rent it to third parties outside their own company,
6. decompile or reverse-engineer it, except where mandatory law permits it, or
7. use it if the Customer or the User is subject to sanctions that preclude a business relationship with SwiftLabs.

Section 16 Suspension for violations

(1) SwiftLabs may temporarily suspend individual Accesses or all or part of the company account if

1. there are concrete indications of a material violation of section 15,
2. an Access poses a threat to the security of the service or of other customers, or
3. an authority or a court orders it or the law requires it.

(2) SwiftLabs chooses the least intrusive effective measure, informs the Owner without undue delay where permitted, and lifts the suspension as soon as its reason ceases to exist.

(3) Customer Data is retained. An export under section 11 remains possible unless a law or order prevents it. The right to terminate for cause remains unaffected.

Section 17 Rights in miphu

(1) All rights in miphu, its software, design and trademarks remain with SwiftLabs or its licensors.

(2) For the term of the contract, the Customer receives the simple, non-transferable and non-sublicensable right to use miphu within its package through its Users for the purposes of its business. The licence for the apps is governed by Part C.

(3) Open-source components contained in miphu are subject to their own licences.

Section 18 Defects

(1) Statutory law applies to defects, with the following deviations.

(2) No-fault liability for defects already existing when the contract is concluded (section 536a(1), first alternative, BGB) is excluded.

(3) The Customer reports defects without undue delay in text form with a comprehensible description.

(4) SwiftLabs gives no warranty for services of Apple, of providers of connected AI apps, or for hints under section 4(2).

Section 19 Liability

(1) SwiftLabs is liable without limitation for intent and gross negligence, for injury to life, body or health, under the German Product Liability Act, to the extent of any guarantee given, and for fraudulently concealed defects.

(2) In cases of simple negligence, SwiftLabs is liable only for breach of an essential contractual obligation. An obligation is essential if its fulfilment makes the proper performance of the contract possible in the first place and the Customer regularly relies and may rely on its fulfilment. Liability is then limited to the damage foreseeable and typical for the contract at the time of its conclusion.

(3) Subsections 1 and 2 apply to loss of data. If an export under section 13(4) would have prevented or reduced the damage, this is taken into account under section 254 BGB (contributory fault).

(4) Subsections 2 and 3 also apply to the personal liability of SwiftLabs' officers, employees and vicarious agents.

(5) Claims under subsection 2 become time-barred one year after the statutory limitation period begins.

(6) Claims of data subjects under Art. 82 GDPR remain unaffected.

Section 20 Term and termination

(1) The Owner concludes the contract for the Customer in the app's purchase flow. Directly at the button with which the Owner purchases the Subscription, the app states in one line that by purchasing the Owner accepts these Terms and the data processing agreement, and links both texts in a form that can be stored. There is no separate checkbox. SwiftLabs stores the version of both texts and the time of acceptance. The contract begins as soon as SwiftLabs creates the company account after the confirmed purchase, and runs for an indefinite period. Use exists for as long as the Subscription runs.

(2) The Customer may terminate the contract at any time by the Owner deleting their account and with it the company account (section 12(2)) or by notifying SwiftLabs in text form. It additionally cancels the Subscription with Apple (section 7(3)).

(3) Each party's right to terminate for cause remains unaffected. Cause for SwiftLabs exists in particular if the Customer, despite a warning, repeatedly or materially violates section 15, is not a business contrary to section 3, or is subject to sanctions.

(4) After the contract ends, section 8(2) and (3), section 11(2) to (5) and section 12 apply.

Section 21 Changes to these Terms

(1) SwiftLabs may change these Terms with effect for the future. The new version is shown to the Owner in the app with a notice and a button; by pressing the button the Owner accepts, and SwiftLabs stores the version and time.

(2) Changes that are exclusively favourable to the Customer are communicated in text form; they apply without acceptance.

(3) Changes to the list of sub-processors follow the data processing agreement. Prices change under section 7(6).

Section 22 Confidentiality

Each party treats non-public information of the other party received under the contract as confidential and uses it only for the contract. This continues after the contract ends. Statutory disclosure obligations remain unaffected.

Section 23 Final provisions

(1) The laws of the Federal Republic of Germany apply, excluding the UN Convention on Contracts for the International Sale of Goods.

(2) If the Customer is a merchant, a legal entity under public law or a special fund under public law, or has no general place of jurisdiction in Germany, the exclusive place of jurisdiction is Nuremberg, Germany. SwiftLabs may also sue the Customer at its general place of jurisdiction.

(3) The German version is binding. The English version is for information.

(4) Notices under these Terms may be given in text form. SwiftLabs sends them to the Owner's email address.

(5) The Customer may transfer rights under this contract only with SwiftLabs' consent; section 354a HGB remains unaffected.

(6) If a provision is invalid, the remainder of the contract remains valid.

This Part contains the minimum terms Apple requires for a custom end-user licence agreement ("Instructions for Minimum Terms of Developer's End-User License Agreement", retrieved 15 September 2026). It applies to everyone who downloads or uses a miphu app from the App Store, including the Customer's employees.

C.1 Parties

This licence agreement is concluded between the User and SwiftLabs only, and not with Apple. SwiftLabs, not Apple, is solely responsible for the apps and their content. Usage rules in this agreement that conflict with the Apple Media Services Terms and Conditions do not apply.

C.2 Licence

SwiftLabs grants the User a non-transferable licence to use the apps on any Apple-branded products that the User owns or controls, as permitted by the Usage Rules set forth in the Apple Media Services Terms and Conditions. Other accounts associated with the purchaser via Family Sharing or volume purchasing may also use the apps. Working with miphu additionally requires an Access to a company account.

C.3 Maintenance and support

SwiftLabs is solely responsible for maintenance and support of the apps, to the extent set out in section 9 or required under applicable law. Apple has no obligation whatsoever to furnish any maintenance and support services with respect to the apps.

C.4 Warranty

SwiftLabs is solely responsible for any product warranties, whether express or implied by law, to the extent not effectively disclaimed. In the event of any failure of an app to conform to any applicable warranty, the User may notify Apple, and Apple will refund the purchase price for the app to the User. To the maximum extent permitted by applicable law, Apple has no other warranty obligation whatsoever with respect to the apps, and any other claims, losses, liabilities, damages, costs or expenses attributable to any failure to conform to any warranty are SwiftLabs' sole responsibility.

C.5 Product claims

SwiftLabs, not Apple, is responsible for addressing any claims of the User or any third party relating to the apps or the User's possession and/or use of the apps, including, but not limited to: (i) product liability claims; (ii) any claim that an app fails to conform to any applicable legal or regulatory requirement; and (iii) claims arising under consumer protection, privacy or similar legislation. This agreement does not limit SwiftLabs' liability to the User beyond what is permitted by applicable law.

C.6 Intellectual property rights

In the event of any third-party claim that an app or the User's possession and use of an app infringes that third party's intellectual property rights, SwiftLabs, not Apple, is solely responsible for the investigation, defence, settlement and discharge of any such claim.

C.7 Legal compliance

The User represents and warrants that (i) they are not located in a country that is subject to a U.S. Government embargo, or that has been designated by the U.S. Government as a "terrorist supporting" country; and (ii) they are not listed on any U.S. Government list of prohibited or restricted parties.

C.8 Contact

Questions, complaints or claims with respect to the apps are directed to: SwiftLabs UG (haftungsbeschränkt), Schanzenstraße 19, 90478 Nürnberg, Germany, phone +49 911 49529681, email hello@miphu.com.

C.9 Third-party terms

When using the apps, the User complies with applicable third-party terms, for example their mobile data contract and the terms of the providers of AI apps they connect to miphu.

C.10 Apple as third-party beneficiary

The User and SwiftLabs acknowledge and agree that Apple, and Apple's subsidiaries, are third-party beneficiaries of this licence agreement, and that, upon the User's acceptance of this agreement, Apple will have the right (and will be deemed to have accepted the right) to enforce this agreement against the User as a third-party beneficiary thereof.

C.11 Users who are not the Customer

Towards Users who are not themselves the Customer, in particular the Customer's employees, SwiftLabs is liable in accordance with statutory law. The usage rules in section 15 also apply to them.

Under Art. 25(2)(e) and (f) of Regulation (EU) 2023/2854 (Data Act). Format and provision: section 11(1). Which datasets, columns and files belong to which category is stated in the register under section 11(7) (format version 1).

Part 1 - Categories that can be exported

For all categories:

• Deleted and archived entries are included and flagged as such.
• Request records belong to their category: the records of the requests with which Users created, changed, archived or deleted entries, with the User, the request key, the content or a checksum of the content, the result and the time, where stored.
• Settings and rights the Customer has set in miphu are included; they are the Customer's digital assets in miphu.
• Insights have no data of their own; they are computed from the exported payments and expenses.

Part 2 - Excluded data

This list is exhaustive. Which tables and columns fall under which group is stated in the register under section 11(7) and in the manifest of every Data Export. The exclusions do not impede or delay switching: the business facts behind groups 3 and 4 are contained in Part 1.

1. Access and security data. Password hashes and credential counters, session, access and refresh tokens, one-time codes and consent handles of AI apps, binding tokens for the App Store and other cryptographic keys. Disclosing them would endanger the security and integrity of the service (recital 82, Art. 30(6) Data Act).
2. Rate limiting and abuse prevention. Internal counters and budgets with which miphu limits requests and prevents abuse. Reason as in item 1.
3. Server, processing and error logs of the service. Logs and queues of processing notifications from the App Store and payment providers, logs of deletion runs and the full technical reports of the validation tools for electronic invoices (KoSIT, veraPDF), which contain internal server paths. The reported facts themselves and the validation receipt of every invoice are exported (Part 1). Reason as in item 1.
4. SwiftLabs' own records of billing and operation. Records with which SwiftLabs evidences which changes to Subscription and seats it applied, which access it granted by hand without a purchase, and when it deleted and will finally delete an account or company account. This data is not generated by the Customer's use of the service but arises as SwiftLabs' records for its own bookkeeping and for evidencing its own obligations (Art. 2(38) Data Act, section 12(7)). The state of the Subscription and of granted access itself is contained in Part 1.