Easypeasy Regnskap AS
Subprocessors
This page provides an overview of key subprocessors and other service providers Easypeasy uses to deliver the service.
Last updated: 10 September 2026
The list below describes the supplier, main purpose and categories of data that may be processed. The list may be updated when Easypeasy changes or adds relevant service providers.
| Supplier | Purpose | Data categories |
|---|---|---|
| Clerk | Authentication and user and organisation administration | User identity, authentication metadata, email address and organisational affiliation |
| PostHog | Product analytics | Event data, user IDs, organisation IDs and usage metadata |
| Stripe | Payments, subscriptions and billing administration | Customer identifiers, subscription information and payment metadata |
| Resend | Transactional email and contact communication | Recipient email address, message content and contact metadata |
| LINK Mobility | Sending SMS invitations when the feature is used | Recipient phone number, message content including invitation link and business name, and delivery metadata |
| Photon / Spectrum | Receiving and sending iMessage messages when the Customer activates the integration | Phone numbers, message content, attachments and conversation metadata |
| Slack | Internal handling of customer enquiries | User and organisation information, message content and any screenshots sent to customer support |
| Cloudflare R2 | File upload, storage and download | Uploaded receipts, invoices, attachments, generated documents and file metadata |
| Google Workspace / Gmail API | Inbox connection and synchronisation of email and attachments when the Customer activates the integration | Email metadata, sender and recipient information and attachment files |
| Google Maps Platform | Address lookup, autocomplete and distance calculation in the mileage log | Address queries, selected address details, and start and destination addresses for trips |
| Mapbox | Map display and mileage log demonstration on the website | IP address, browser and request metadata when maps and demonstration routes load |
| Logo.dev | Lookup of business logos and company information | Business names, domains and search queries relating to contacts and suppliers |
| Trigger.dev | Background jobs and orchestration | Task payloads that may contain organisation IDs, integration metadata and operational processing data |
| Neonomics | Bank connection and transaction synchronisation | Bank account IDs, transaction data, and connection and session metadata |
| Qvalia | EHF and electronic invoice delivery | Invoice data, company information and recipient routing |
| Mistral AI | Optical character recognition (OCR) for documents that require it | Receipts, invoices, attachments, and text and information extracted from the documents |
| OpenRouter | AI inference, model routing and text representations for search | Document text, accounting context, message content, prompts and business information processed by AI features and forwarded to model providers |
| Google Gemini | AI-based information lookup and document and accounting processing, directly and through OpenRouter | Search queries, document content, accounting context, message content and prompts sent to the service |
| Vercel | Hosting and delivery of client-facing or web-related services | Technical logs, request metadata and any data processed through the hosting environment |
| Render.com | Hosting and operation of server components, APIs and background processes | Technical logs, request metadata and operational data relating to service delivery |
| PlanetScale | Database infrastructure and storage where used | Data the Customer stores in the System, including accounting information and associated metadata |
Questions about subprocessors can be sent to support@easypeasy.no .