Back to homepage

Data Processing Agreement

pursuant to Art. 28 GDPR

Last updated: 15 November 2026

This translation is provided for information purposes only. Only the German version is legally binding. Go to the German version

Our principles

Even as our products evolve, our principles stay the same: we do not sell your data, RIKE remains ad-free, and the data you enter is not used to train AI models.

RIKE is funded exclusively through customer subscription fees — not through advertising or the sale of data. Fair pricing of our products covers our operating costs and safeguards the platform's independence and commitment to privacy.

Preamble

This Data Processing Agreement (hereinafter “DPA”) specifies the data protection obligations of the contracting parties arising from the usage agreement concluded between them concerning the RIKE platform (hereinafter the “Main Agreement”). It applies to all activities in which Vegvísir GmbH (hereinafter the “Processor”) processes personal data of the customer (hereinafter the “Client” or “Controller”) on the Client's behalf.

§ 1 Subject Matter and Duration of the Data Processing

(1) The subject matter of the data processing is the provision of the cloud-based SaaS platform RIKE for the management of members, events, documents, communication, invoices, dues, and incoming payments as well as other group-related processes in accordance with the Main Agreement.

(2) The duration of the data processing corresponds to the term of the Main Agreement. It begins with the provision of the platform and ends upon termination of the contract, but no later than upon the final deletion of all Client data pursuant to § 10 of this DPA.

(3) This agreement applies insofar as the Client is the controller for data protection purposes with respect to the processing of the personal data entered into the platform (e.g. an association, club, or entrepreneur processing member and participant data). If a natural person uses the platform exclusively for personal or household purposes without any association or business connection, the household exemption under Art. 2 Abs. 2 lit. c DSGVO may apply; in that case, this agreement is without effect, and Vegvísir GmbH may be its own controller in accordance with the privacy policy.

§ 2 Nature and Purpose of the Processing, Types of Data, Data Subjects

Nature of the processing: Collection, storage, structuring, adaptation, retrieval, alignment and combination (e.g. of incoming payments with invoices), transmission (e.g. sending invoices, payment reminders, and payment confirmations on behalf of the Client), erasure, restriction, and other operations associated with the provision of the platform.

Purpose of the processing: Enabling the Client's contractual use of the RIKE platform for the organization and management of its group, including creating and sending invoices, payment reminders, and payment confirmations, managing dues, generating SEPA direct debit files which the Client submits to its bank itself, reconciling incoming payments with open claims, and keeping a cash book. In doing so, the Processor does not process any payments, does not accept any funds, and has no access to bank accounts of the Client or of payers. In addition, the Processor measures individual steps of getting started with the platform in aggregated form (e.g. “tour started”) in order to improve onboarding; only the area (administration or members), the booked plan and whether it is a demo are transmitted, together with the IP address and browser identifier solely to form a daily changing checksum that Plausible does not store (sub-processor: Plausible, § 6).

Types of personal data:

  • Master data (name, address, date of birth)
  • Contact data (email, phone number)
  • Access and authentication data
  • Profile and role assignments within the group
  • Vehicle data (motorcycle details, images)
  • Event and attendance data
  • Documents and file uploads posted by the Client
  • Communication and usage logs within the platform
  • Payment and billing information insofar as managed by the Client, in particular bank details (IBAN, BIC, account holder) and SEPA direct debit mandates (mandate reference, date of signature)
  • Invoice, dues, and reminder data (recipients, line items, amounts, due dates, payment status including recorded partial payments, records of dispatch and reminders)
  • Incoming payments from bank statements uploaded by the Client (booking date, amount, name of the payer, payment reference)
  • Cash book entries and supporting documents
  • Access data for a mailbox of its own set up by the Client (server, user name, password stored in encrypted form, sender address)

Categories of data subjects:

  • Members of the Client's group
  • Guests and participants at events
  • Administrators and other users of the platform
  • Prospects and contact persons
  • Invoice recipients without their own account on the platform (e.g. contacts, sponsors, business partners)
  • Payers whose incoming payments are contained in bank statements uploaded by the Client
  • Persons named in cash book supporting documents (e.g. suppliers, recipients of reimbursements)

Special categories of personal data within the meaning of Art. 9 GDPR are not the subject of the data processing. The Client is obliged not to enter such data into the platform without prior coordination and additional technical safeguards.

Payment reconciliation: The Processor evaluates bank statements that the Client uploads for reconciliation exclusively in working memory; the file itself is not stored. Only information about the import (file name, period, number of entries, and a checksum of the file that prevents duplicate evaluation) and the credits contained in the file, with booking date, amount, name of the payer, and payment reference, are stored. Debits and the payers' IBANs are not stored. Credits that the Client does not match to an invoice are automatically deleted 30 days after import; matched credits remain stored as proof of payment until deletion pursuant to § 10.

§ 3 Obligations of the Processor

(1) The Processor processes personal data exclusively within the scope of the agreements made and in accordance with the documented instructions of the Client, unless it is required by law to carry out other processing. In such a case, the Processor shall inform the Client of these legal requirements prior to the processing, unless the law in question prohibits such notification on important grounds of public interest.

(2) The Processor shall inform the Client without undue delay if it considers that an instruction infringes data protection provisions. The Processor is entitled to suspend the execution of the relevant instruction until it has been confirmed or amended by the Client.

(3) The Processor ensures that the persons authorized to carry out the processing have committed themselves to confidentiality or are subject to an appropriate statutory obligation of secrecy.

(4) The Processor implements the technical and organizational measures described in § 5 in accordance with Art. 32 GDPR and maintains them for the duration of the contract.

(5) The Processor supports the Client, within the scope of its capabilities, in fulfilling the requests and claims of data subjects pursuant to Chapter III of the GDPR and in complying with the obligations set out in Art. 32 to 36 GDPR.

(6) The Processor has appointed an external data protection officer where required by law. The contact details will be provided to the Client upon request.

§ 4 Obligations of the Client

(1) Within the scope of this agreement, the Client is solely responsible for compliance with the statutory provisions of data protection law, in particular for the lawfulness of the transfer of data to the Processor and for the lawfulness of the data processing (“controller” within the meaning of Art. 4(7) GDPR).

(2) The Client shall, as a rule, issue its instructions in writing or in text form (e.g. by email to support@rike.club). Verbal instructions must be confirmed in writing or in text form without undue delay.

(3) The Client shall notify the Processor of the persons authorized to issue instructions. In case of doubt, the users registered as administrators in the system are deemed authorized to issue instructions.

(4) The Client shall inform the Processor without undue delay if it detects errors or irregularities in connection with the processing of personal data by the Processor.

§ 5 Technical and Organizational Measures (TOMs)

In accordance with Art. 32 GDPR, the Processor ensures the security of the processing through appropriate technical and organizational measures. These include, in particular:

1. Confidentiality

  • Physical access control: hosting in certified data centers (ISO 27001) of the subcontractors Vercel and Supabase in the EU
  • System access control: multi-step authentication, strong password requirements (at least 10 characters, check against known password leaks), optional second factor for everyone who manages a group, notification when signing in on a new device, automatic session expiration, hashed password storage (bcrypt)
  • Data access control: role-based access control (RBAC), row-level security (RLS) in the database, multi-tenant separation per tenant
  • Separation control: logical tenant separation via tenant IDs and RLS policies; production, test, and development environments are kept separate
  • Pseudonymization and encryption of personal data where appropriate
  • Encrypted storage of the access data for a mailbox of its own set up by the Client (AES-256-GCM, key kept separate from the database); the password cannot be retrieved after saving

2. Integrity

  • Transfer control: transport encryption (TLS 1.2+) for all data transmissions; encryption of data at rest (AES-256) in the database and file storage
  • Input control: audit logs for security-relevant changes (granting of permissions, deletions, admin actions)
  • Sign-in log: logging of sign-ins and security-relevant account changes (time, sign-in method, IP address, device), automatic detection of unusual patterns, notification of the person concerned of account changes, deletion after 90 days

3. Availability and Resilience

  • Automated daily database backups with point-in-time recovery
  • Geo-redundant data storage within the EU
  • Monitoring and alerting at infrastructure and application level
  • DDoS protection and Web Application Firewall (WAF) provided by the hosting provider

4. Procedures for Regular Review, Assessment, and Evaluation

  • Regular security updates of operating systems and dependencies
  • Code reviews and automated security checks in the development process
  • Data protection impact assessment in the event of significant changes
  • Incident response process for data protection incidents

The current version of the TOMs will be made available to the Client in detailed form upon request. The Processor is entitled to adapt the TOMs in the course of technical development, provided that the level of protection agreed in this DPA is not reduced.

§ 6 Subprocessors

(1) The Client consents to the use of the following subprocessors:

NameRegistered officeService
Vercel Inc.USA (EU data centers in Frankfurt)Web hosting, edge delivery
Supabase Inc.Singapore (EU data centers in Frankfurt)Database, authentication, file storage
Stripe Payments Europe, Ltd.IrelandPayment processing for the Processor's platform fees (not for payments to the Client)
Resend, Inc.USATransactional emails
Anthropic PBCUSAAI assistant (Platin plan only)
Functional Software, Inc. (Sentry)USAError and incident monitoring (without names, email addresses or IP addresses)
ElevenLabs, Inc.USAVoice input and output of the AI assistant (only when the voice feature is used)
Plausible Insights OÜEstonia (EU)Audience measurement of individual onboarding steps in the platform (without cookies, names, email addresses or customer numbers)
Cloudflare, Inc.USAProtection against automated requests (Turnstile) when signing in with an SMS code and when joining a group

(2) The Processor has concluded agreements pursuant to Art. 28 GDPR with all subprocessors named above which ensure a level of protection comparable to this DPA. For transfers to third countries, Standard Contractual Clauses of the EU Commission pursuant to Art. 46 GDPR together with supplementary safeguards are in place.

(3) The Processor shall inform the Client in text form in good time before engaging or replacing a subprocessor (e.g. by email to the admin address on file or by notice within the platform). The Client may object to the change in text form within 14 days of receipt of the notification on important grounds relating to data protection law.

(4) If the Client objects on justified grounds, the Processor is entitled to terminate the contract with 30 days' notice if an amicable solution cannot be reached.

(5) Services which the Processor obtains from third parties as purely ancillary services (e.g. telecommunications services, postal and transport services, cleaning, maintenance staff) do not constitute subprocessing within the meaning of this provision.

(6) If the Client sets up a mailbox of its own (SMTP) for sending invoices, payment reminders, or payment confirmations, the Processor hands these emails over to the outgoing mail server of the provider chosen by the Client. That provider is not a subprocessor of the Processor; the contractual relationship with it is maintained solely by the Client. The Processor stores the access data for the mailbox in encrypted form (§ 5) and uses it exclusively for this dispatch.

§ 7 Rights of Data Subjects

(1) The Processor shall, where possible, support the Client with appropriate technical and organizational measures in fulfilling the rights of data subjects pursuant to Art. 12 to 22 GDPR (access, rectification, erasure, restriction, data portability, objection).

(2) If a data subject contacts the Processor directly to exercise their rights, the Processor shall forward this request to the Client without undue delay.

(3) The Client uses the access, rectification, and deletion functions provided in the platform administration on its own and uses them independently to handle data subject rights.

§ 8 Notification Obligations in the Event of Data Protection Incidents

(1) The Processor shall inform the Client without undue delay, but no later than within 48 hours of becoming aware, of any breaches of the protection of the Client's personal data (Art. 33 GDPR).

(2) The notification shall include at least:

  • A description of the nature of the breach
  • The category and approximate number of data subjects and data records concerned
  • The name and contact details of a contact person for further information
  • A description of the likely consequences
  • A description of the measures taken or proposed to remedy the breach and to contain any adverse effects

(3) The Processor supports the Client in fulfilling its notification obligations towards the supervisory authority (Art. 33 GDPR) and in notifying the data subjects (Art. 34 GDPR).

§ 9 Control and Audit Rights

(1) The Client has the right to satisfy itself of the Processor's compliance with the obligations under this DPA. For this purpose, the Processor shall provide the Client with the necessary information upon request, in particular:

  • The complete documentation of the TOMs pursuant to § 5
  • Certificates or attestations of the subcontractors (where available)
  • The current list of subprocessors pursuant to § 6

(2) If, in the Client's view, the submission of the aforementioned documents is not sufficient, the Client may, once a year or where there is specific cause, have an on-site inspection carried out by an expert third party designated by it. The third party must not be a competitor of the Processor and must be bound to confidentiality.

(3) Inspections must be announced in text form with at least 30 days' notice and must take place during normal business hours without disproportionately disrupting business operations.

(4) The Client bears the costs of the inspection. The Processor is entitled to charge a reasonable fee for its own expenses.

§ 10 Deletion and Return of Data

(1) Upon completion of the data processing – at the latest upon termination of the Main Agreement – the Processor shall make an export of the Client's data available to the Client via the platform for 30 days in a common, machine-readable format (e.g. JSON/CSV).

(2) After expiry of the export period, the Processor shall delete all personal data processed under the Main Agreement irrevocably and in compliance with data protection law, including any copies held by subprocessors, unless statutory retention obligations prevent deletion.

(3) Backup data is deleted as part of the regular backup rotation, but no later than within 90 days after the end of the contract.

(4) The deletion will be confirmed to the Client in writing or in text form upon request.

(5) During the term of the contract, the periods set out in § 2 (payment reconciliation) additionally apply to data from bank statements.

§ 11 Liability

The liability of the parties is governed by the provisions of the Main Agreement accordingly, unless otherwise provided in this DPA. Art. 82 GDPR remains unaffected.

§ 12 Final Provisions

(1) This DPA supplements the Main Agreement. Should individual provisions of this DPA be or become invalid, the validity of the remaining provisions shall remain unaffected. The invalid provision shall be deemed replaced by the valid provision that most closely reflects the meaning and purpose of the invalid provision.

(2) In the event of contradictions between this DPA and the Main Agreement, the provisions of this DPA shall prevail insofar as they concern data protection matters.

(3) The law of the Federal Republic of Germany applies. The exclusive place of jurisdiction is Hamburg.

Conclusion and Acceptance

This DPA automatically becomes part of the contract upon conclusion of the Main Agreement (ordering a paid plan via the rike.club platform). A separate signature is not required; the Client accepts this DPA implicitly by concluding the Main Agreement.

Upon request, the Processor will provide a separately signed version of this DPA. Please send requests to support@rike.club.

Processor

Vegvísir GmbH
Ballindamm 27
20095 Hamburg
Germany
Managing Director: Mark C. Reinold
HRB 178193, Local Court (Amtsgericht) of Hamburg
VAT ID: DE357182449