These terms apply in addition to the Master Subscription Agreement ("MSA") when the Customer uses the modules and features described below. Terms defined in the MSA have the same meaning here.
1. Finance and accounting
1.1 The Finance module supports the following tasks:
- bookkeeping;
- invoicing, including Swiss QR-bill;
- VAT;
- bank reconciliation;
- year-end processes.
The module applies the rules configured by the Customer, such as tax rates, accounts and rounding.
1.2 The Customer is responsible for the correctness of its accounting, tax returns and financial statements. The Customer shall have the results checked by qualified persons where required. The Service does not provide tax, accounting or legal advice.
1.3 Imported bank statements and payment files are processed as supplied. The Customer shall check proposed matches before confirming them.
2. Human resources and payroll
2.1 The HR module supports the following tasks:
- employee records;
- working time;
- absences;
- documents;
- payroll calculations based on the rules configured by the Customer.
2.2 The Customer is responsible for the correctness of payslips and payroll-related declarations, and for compliance with employment, social-security and tax law. Unless expressly stated in the Order Form, the Service does not file declarations with authorities or social-insurance institutions.
2.3 Employee data is subject to the Sensitive Data Terms.
3. Files and retention archive
3.1 The Files module stores documents of the Customer. Documents moved to the retention archive (for example under the Swiss Ordinance on the Keeping of Accounts, GeBüV) are stored on write-protected storage for the retention period configured. During this period they cannot be changed or deleted by the Customer or its Users. relyd deletes archived documents before the end of the retention period only on the Customer's written request (section 3.4).
3.2 The archive supports the Customer's retention obligations. The Customer remains responsible for deciding which documents must be kept, for how long and in which form.
3.3 After the end of the subscription, the Customer chooses one of the following:
- (a) export and deletion: the Customer exports the archive during the deletion period of thirty (30) days (MSA section 9.6), after which relyd deletes it together with the other Customer Data, free of charge; or
- (b) continued retention: relyd continues to keep the archive on write-protected storage under the archive-only plan set out in the price list, for the remaining retention period.
If the Customer makes no choice, relyd keeps the archive, the archive tables and the company record needed to identify it, and deletes all other Customer Data after the deletion period.
3.4 The Customer may at any time request in writing (to privacy@relyd.co) that relyd delete a retained archive before the end of the retention period. relyd verifies the request, deletes the archive free of charge and confirms the deletion in writing. The Customer is responsible for ensuring that the deletion is compatible with its own retention obligations.
4. E-mail, chat and communication
4.1 If the Customer connects e-mail accounts, for example via IMAP/SMTP, Google or Microsoft, the Service retrieves and sends e-mails on its behalf. Copies of the messages are stored in the Service so that they can be displayed and searched.
4.2 The Customer shall ensure that it is entitled to connect the mailboxes concerned and that the persons concerned are informed. This applies in particular to personal mailboxes of employees.
4.3 Chat, direct messages and whiteboards are available only to the members of the Workspace.
5. Artificial-intelligence features
5.1 Optional AI features include the following:
- summaries and drafting assistance;
- extraction of data from documents, for example incoming invoices;
- assistant and automation features such as the AI Steward.
The providers used are listed as subprocessors. Only the content needed for the specific request is transmitted. Under relyd's contracts with the providers, the content is not used to train AI models.
5.2 AI results can be incomplete or wrong. The Customer shall review them before relying on them, in particular before booking, paying, sending or deciding.
5.3 Automations. Where the Customer allows AI or rule-based automations to carry out actions automatically, such as creating tasks, sending messages or changing records, the Customer is responsible for the rules it configures. The Service shows which actions were carried out automatically and allows them to be undone where technically possible.
5.4 AI features are charged against the prepaid AI credit (Terms of Sale section 6). The Customer may use its own API key with an AI provider instead; in that case the Customer contracts with that provider directly.
6. Support portal, help centre and public links
The Customer can publish content to external persons through the support portal, help centre, support widget, customer portal and public links, for example proposal, contract or signature links. The Customer decides what it publishes and who receives links. Anyone who has a public link can open it. The Customer shall share such links only with the intended recipients.
7. APIs, webhooks and integrations
7.1 The Customer can create API keys and webhooks. The Customer shall:
- keep API keys confidential;
- give them only the permissions needed;
- revoke keys that are no longer used.
Actions carried out with a key are attributed to the Customer.
7.2 Webhooks send data to addresses specified by the Customer. The Customer is responsible for the security of the receiving systems and for their compliance with data protection law.
7.3 relyd may change APIs with reasonable notice. Changes that break compatibility will be announced at least ninety (90) days in advance, unless they are required for security reasons.
8. Mobile application
The mobile application (mobile.relyd.co) gives access to selected functions of the Service. It is subject to the same terms as the Service. Push notifications can be switched off in the device settings.
9. Beta modules
Modules and features marked "beta" (currently, for example, the Quality module) are provided for evaluation (MSA section 4.3). Data entered in beta modules is protected in the same way as other Customer Data.
10. Data import
The Customer is responsible for the content and legality of imported data and for checking the result of an import. Imports can overwrite existing data, depending on the options selected.