CustCom Logo

Privacy policy

As of 16 November 2026

1. Controller and scope

Controller within the meaning of the GDPR:

CustCom UG (haftungsbeschränkt)
Sandstraße 17

49080 Osnabrück

Germany

Email: [email protected]
Phone: +49 541 97736626

Represented by: Luis Wagener
Amtsgericht Osnabrück, HRB 223774

VAT identification number pursuant to Section 27a of the German VAT Act (UStG): DE466365678

This privacy policy applies to the processing of personal data in connection with:

  • the website custcom.io (marketing and information; apex domain; www.custcom.io is not currently set up),
  • the SaaS application app.custcom.io (dashboard / auth shell),
  • the customer portal portal.custcom.io,
  • the platform services reachable through those surfaces,
  • audience measurement at analytics.custcom.io, where embedded.

It is addressed to website visitors and to users and contacts of customer organisations (B2B). Where CustCom processes personal data on behalf of customers (customer data in the platform), the respective customer is the controller. The data processing agreement (DPA) at /en/legal/dsgvo applies.

2. Overview: categories, purposes, legal bases

2.1 Types of data processed

  • Master data (for example name, company name, address, customer or organisation ID)
  • Contact data (email, phone)
  • Contract and billing data (plan, term, invoices, payment status; payments via Stripe)
  • Content and business data (tasks, time tracking, invoices, receipts, customer communication, notes — depending on use of the platform)
  • Usage and metadata (page views, device and browser information, timestamps, referrer)
  • Log data (access, authentication, errors)
  • Authentication data (session and refresh tokens, magic-link tokens, device binding for the portal)
  • AI inputs and outputs (when the AI assistant or enrichment is used)
  • Email content and attachments (outbound sending and inbound receipts and emails)

2.2 Categories of data subjects

Website visitors; registered users and organisation members; contacts at customers; end customers and contacts of the customer organisation (where the customer stores them in the platform); communication partners.

2.3 Purposes

Providing and operating the website and SaaS; registration and authentication; performance of the contract and billing; support and communication; security (including bot protection); error analysis; audience measurement (cookieless); AI features; receipt and email processing; enforcement of rights and legal obligations.

2.4 Legal bases

  • Art. 6 (1) (b) GDPR — performance of a contract or steps prior to a contract (account, SaaS use, billing, support within the contractual relationship)
  • Art. 6 (1) (f) GDPR — legitimate interests (security, stability, abuse prevention, product improvement through aggregated error and usage data, enforcement of claims)
  • Art. 6 (1) (c) GDPR — legal obligation (in particular commercial and tax retention)
  • Art. 6 (1) (a) GDPR — consent (only where we base optional processing on consent, for example a newsletter, if offered)

National rules also apply (in particular the German Federal Data Protection Act, BDSG) and, for processing on behalf of a controller, Art. 28 GDPR.

3. Hosting, infrastructure, and logs

The CustCom applications (website, dashboard, customer portal, and the services reachable through them) are operated in Germany.

For storage and email we use Amazon Web Services. That processing takes place in data centres in Germany.

Server and application logs may contain IP address, timestamp, request metadata, user agent, and error information. Purpose: operation, security, abuse prevention, and error diagnosis. Legal basis: Art. 6 (1) (f) GDPR. We keep sign-in records (time, IP address, device) for 90 days to detect attacks and account takeovers and delete them automatically afterwards; expired sessions are deleted immediately.

TLS/HTTPS and edge protection are provided in part by Cloudflare (see section 10 / recipients).

If an unexpected error occurs on our servers, we send a technical error report (affected service, path without parameters, error text, and stack trace) to an internal channel at Slack (Slack Technologies Limited, Ireland, and Slack Technologies, LLC, USA). We do not send request contents, headers, cookies, or IP addresses; error texts may nevertheless contain personal data in individual cases. Purpose: error diagnosis and stable operation. Legal basis: Art. 6 (1) (f) GDPR. Transfer to third countries: possible (USA); safeguards: DPA and EU SCCs.

4. Registration, account, and authentication

Use of app.custcom.io generally requires registration. We process in particular email address, name, company or organisation details, a password hash or other authentication secrets, and verification status.

Email verification and transactional auth emails are sent via Amazon Web Services.

Essential auth cookies / storage (app):

Name / typePurposeStorage period (guidance)
__Host-custcom.access_tokenSession access (HttpOnly, Secure, host prefix)short-lived / session as configured
__Host-custcom.refresh_tokenSession renewallonger, according to the refresh policy
Theme / locale / UI preferences (for example theme, CUSTCOM_LOCALE, sidebar state, table filters and sort)Display / languageup to several months, or until deletion

Legal basis: Art. 6 (1) (b) GDPR (use of the service) and Art. 6 (1) (f) GDPR (security of authentication).

5. Contract, billing, and Stripe

Subscriptions and payments are processed via Stripe Checkout / Stripe (Stripe Payments Europe, Ltd., Ireland, with the involvement of Stripe, Inc., USA). We store subscription status, the customer or organisation reference, and invoice metadata. Card numbers are processed by Stripe and are not stored on our servers.

Legal basis: Art. 6 (1) (b) and (c) GDPR. Stripe may transfer data to third countries. Safeguards: a DPA and EU standard contractual clauses (SCCs) where required. Details: Stripe’s privacy notices.

6. Communication and email (Amazon Web Services)

Outbound: Transactional and system emails (verification, password reset, notifications, invoices, support) via Amazon Web Services.

Inbound (customer receipts / business email): Incoming emails and attachments may be received and stored via Amazon Web Services and used for further processing (for example receipt recognition). The customer remains responsible for the lawfulness of forwarding and of the content.

Legal basis: Art. 6 (1) (b) GDPR (providing the feature) and, where relevant, Art. 6 (1) (f) GDPR (operation and security). Processing takes place in data centres in Germany.

7. AI features (Microsoft Azure OpenAI, Google Vertex AI)

Where the customer uses AI features (assistant, chat, vision, embeddings, enrichment), the inputs, context, and outputs required for that function are transmitted to Microsoft Azure OpenAI (EU/EEA regions according to the Microsoft configuration) in order to provide the function. Uploaded receipts (PDF, photo) without an e-invoice are read via Google Vertex AI in data centres in Germany; the receipt file and its file name are transmitted. E-invoices (ZUGFeRD, XRechnung) are read directly without AI.

  • Processing is for providing the booked function, not for CustCom’s own training purposes.
  • Whether and to what extent the cloud provider uses inputs for its own purposes depends on Microsoft’s terms and the Microsoft DPA. We do not make further training promises that we cannot verify.
  • The customer remains responsible for entering only lawful and necessary content (in particular no special categories of personal data without a legal basis).

Legal basis: Art. 6 (1) (b) GDPR; where we act as processor, Art. 28 GDPR together with the main contract and the DPA.

8. Customer portal and magic links

The portal (portal.custcom.io) gives end customers or authorised persons access to content that has been shared with them.

Magic-link flow (simplified):

  1. Request by email (sent via Amazon Web Services).
  2. A device-bound cookie is set and a one-time link (valid for about 15 minutes) is sent to /verify.
  3. The link must be opened in the same browser / on the same device. A scanner or another device generally does not consume the token.
  4. After successful verification, a portal session is set.

Portal cookies (essential): cookies with the prefix __Secure-custcom.portal_ and magic-link / device-binding cookies.

Legal basis: Art. 6 (1) (b) GDPR (portal access within the customer relationship) and Art. 6 (1) (f) GDPR (security and abuse prevention).

9. Audience measurement (own instance of Plausible Analytics)

For audience measurement on the website and in the sign-in interface (app.custcom.io), where embedded, we use a self-operated instance of the open-source software Plausible Analytics (analytics.custcom.io). It runs on the technical infrastructure we operate in Germany. Measurement data is processed by us alone and is not transferred to the software vendor or any other external recipient.

  • No cookies for analytics, no personal profiles, and no cross-site tracking profiles of the kind used by classic tracking tools.
  • Aggregated usage statistics are collected (for example page views, referrer, device type).
  • The IP address and browser identifier are used only briefly to generate a visitor identifier that changes daily and cannot be traced back, and they are not stored.

Legal basis: Art. 6 (1) (f) GDPR (interest in audience measurement and product improvement using a data-minimising method).

10. Cloudflare (CDN/DNS/security) and Turnstile

We use Cloudflare for DNS, CDN, TLS, and security functions. Request metadata and technical logs are generated.

Cloudflare Turnstile is used for bot and abuse protection (for example on forms and login). Turnstile may process technical data about the client.

Legal basis: Art. 6 (1) (f) GDPR. Transfer to a third country: possible. Safeguards: Cloudflare DPA / SCCs.

11. Contact and newsletter

When you contact us (form, email, or phone), we process the data you provide in order to handle the request. Legal basis: Art. 6 (1) (b) and/or (f) GDPR.

Newsletter / marketing email: Not a mandatory product feature at present. If offered, only with consent (Art. 6 (1) (a) GDPR) and an unsubscribe option. Transactional emails within the contractual relationship do not require marketing consent.

12. Cookies and similar technologies (overview)

CategoryExamplesRequired?Legal basis
Essential — app auth__Host-custcom.access_token, __Host-custcom.refresh_tokenYesArt. 6 (1) (b) / (f)
Essential — portalprefix __Secure-custcom.portal_, magic-link device cookieYesArt. 6 (1) (b) / (f)
Essential — preferenceTheme, locale, UI stateYes (functional)Art. 6 (1) (f)
SecurityCloudflare TurnstileYes (security)Art. 6 (1) (f)
AnalyticsPlausible (no analytics cookies)No / data-minimisingArt. 6 (1) (f)

We do not rely on non-essential third-party marketing or tracking cookies. A cookie banner for optional cookies is only required if optional technologies are added later.

13. Recipients and subprocessors

The CustCom applications are operated in Germany. Depending on the function, the following external recipients or processors may also be used (aligned with Annex 2 of the data processing agreement):

Provider / systemServiceLocation / note
Amazon Web ServicesStorage and emaildata centres in Germany
StripeCheckout, subscriptions, paymentsIreland / USA
Cloudflare, Inc.CDN, DNS, security, TurnstileEU / USA possible
Slack Technologies Limited / Slack Technologies, LLCInternal error reportsIreland / USA possible
Microsoft (Azure OpenAI)AI assistant / enrichmentEU/EEA
Google Cloud EMEA Ltd. (Vertex AI)Reading receiptsdata centres in Germany
650 Industries, Inc. (Expo)Push notifications of the mobile appUSA
Browser push services (Google, Mozilla, Apple)Web push notifications (content encrypted)EU / USA possible

We carry out audience measurement ourselves (section 9); no data is transferred to external recipients in that context.

Integrations a customer activates (Slack, Microsoft Teams, GitHub, Calendly) transmit the data required for the respective function to the chosen provider; its terms and privacy notices apply.

Current DPA and subprocessor list: https://custcom.io/en/legal/dsgvo.

14. Transfers to third countries

Transfers to third countries take place only where the requirements of Art. 44 et seq. GDPR are met, in particular by an adequacy decision and/or EU standard contractual clauses (SCCs) and supplementary measures of the providers (Stripe, Cloudflare, Slack, and AWS where applicable). Under our configuration, Azure OpenAI is operated in the EU/EEA. That is to be reflected in the DPA annex.

15. Storage periods

  • Account data: until the account is deleted. Profile, sign-in records and open tokens are deleted immediately; workspace memberships are pseudonymised and their personnel data deleted.
  • Workspace members: on removal, personnel data, absences and calendar connections are deleted; time entries and documents remain under a pseudonym.
  • Contacts: on deletion, master data, contact persons and addresses are deleted; documents already issued keep the recipient data recorded at issue (statutory retention).
  • Documents: invoices, credit notes, cancellations and incoming receipts 8 years, quotes and reminders 6 years, procedure documentation 10 years, each from the end of the calendar year (Section 147 of the German Fiscal Code, Section 257 of the German Commercial Code). A cancelled workspace is no longer accessible from cancellation and is deleted automatically once the last period has ended.
  • Logs: sign-in records 90 days (see section 3).
  • Received emails (receipt inbox): the original email 90 days; attachments are kept as receipts.
  • Text recognition of receipts: 30 days; the original file stays.
  • Read notifications and inactive push devices: 180 days.
  • Backups: overwrite or deletion in the regular backup cycle.
  • Portal magic-link tokens: short-lived (about 15 minutes) or until used or expired.
  • Proof of consent (if a newsletter is offered): up to three years after withdrawal, for the defence of legal claims.

16. Rights of data subjects (Art. 15–21 GDPR)

Subject to the statutory requirements, you have in particular the right to:

  • access (Art. 15),
  • rectification (Art. 16),
  • erasure (Art. 17),
  • restriction of processing (Art. 18),
  • data portability (Art. 20),
  • object to processing based on Art. 6 (1) (e) or (f) (Art. 21),
  • withdraw consent with effect for the future (Art. 7 (3)).

To exercise these rights: [email protected]. If the request concerns data we store only as a processor, we forward it — where it can be attributed — to the respective customer or handle it on that customer’s instructions.

Without prejudice to other remedies, you have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR).

17. Supervisory authority

Competent supervisory authority (the controller is established in Lower Saxony):

Die Landesbeauftragte für den Datenschutz Niedersachsen (LfD Niedersachsen)
Prinzenstraße 5

30159 Hannover, Germany

https://lfd.niedersachsen.de/

18. Changes

We update this privacy policy when processing, technology, or the law changes. The current version is available at https://custcom.io/en/privacy-policy. We will notify you separately of material changes that require action (for example a new consent).