log.cam
Deutsch

Privacy Policy for log.cam

Last updated: 18 November 2026 · Applies to the log.cam app (iOS/Android), the web interface at ui.log.cam, log.cam server services and these public information pages.

This policy describes the features of the distributed log.cam system. Which optional AI, Microsoft, Firebase or payment services are actually enabled depends on the server configuration and on your use.

Google Analytics and Google Ads

On www.log.cam and ui.log.cam, optional Google Analytics 4 measures visits and Google Ads measures confirmed registrations and purchases. Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. Technical device information, page views, cookie identifiers and conversion events may be processed by Google, including in the USA. Recordings, transcripts, idea content, contact details and login tokens are excluded. Google Signals and advertising personalisation are disabled.

Statistics and advertising measurement are separate opt-in choices. No Google measurement tags load without permission. The necessary logcam_consent_v1 cookie stores your choice across log.cam subdomains for up to six months. Optional _ga cookies last up to six months; _gcl cookies support ad attribution. Analytics user and event data retention is two months. Use the permanent Privacy settings button to change or withdraw consent at any time. Withdrawal deletes accessible Google measurement cookies.

Legal bases: consent under Art. 6(1)(a) GDPR and Section 25(1) TDDDG; necessary choice storage under Section 25(2) TDDDG. See Google’s privacy policy. Transfers may rely on certified US recipients under the EU-US Data Privacy Framework or appropriate safeguards such as standard contractual clauses.

Open privacy settings

1. Controller

Controller:
coteki GmbH
Sandmoorweg 17a
22559 Hamburg
Germany

Email: post@coteki.de
App support: app@coteki.de
Phone: +49 40 32531330

2. Data we process

  • Account and sign-in data: email address, optional display name, language, role/plan information, sign-in and verification tokens, sessions and device labels.
  • User content: ideas, text, projects, categories, meetings, transcripts, summaries, decisions, tasks, tags and shares.
  • Audio, voice and media: voice notes, meeting recordings, optional voice profiles/voice segments, and photos, videos, files or documents selected by you.
  • Device and push data: platform, locale and push token/Firebase device identifier where push is enabled.
  • Technical and security data: IP address in security/audit logs, timestamps, actions, errors/job state and connection data.
  • Billing: plan, prepaid balance, billing ledger entries, invoice profile and, where used, PayPal transaction/subscription references.
  • Optional integrations: Microsoft account email, OAuth tokens and scopes for Microsoft 365/Exchange Online.

3. Purposes and legal bases

  • Providing, synchronising and securing your account and app functionality: Art. 6(1)(b) GDPR.
  • Voice, media, AI and integration functions you actively request: depending on the function Art. 6(1)(b) GDPR and, where consent is required, Art. 6(1)(a) GDPR.
  • Abuse prevention, IT security, diagnostics and accountability of security-relevant actions: Art. 6(1)(f) GDPR.
  • Accounting and tax obligations: Art. 6(1)(c) GDPR.

4. Microphone, camera, photos and Bluetooth

log.cam requests device permissions only for the relevant feature. The microphone is used for voice ideas and meetings; the camera for QR codes and optional photos; photo/file access for attachments selected by you; and Bluetooth for discovering/connecting additional meeting microphones. Denied permissions are not repurposed for tracking.

5. AI and speech recognition

For transcription, analysis, summaries or optional speech output, the log.cam server operator may configure one or more providers, including Google Gemini / Google Cloud Speech-to-Text, OpenAI, Anthropic or OpenAI-compatible services. Only when the relevant feature is used and such a provider is enabled are the required contents (for example audio, transcript or text) sent to that provider. API credentials are stored server-side in encrypted form. Providers outside the EEA may involve international transfers; the applicable safeguards of the provider/contracting setup apply.

6. Firebase push

If push notifications are enabled and Firebase is configured on the server, Google Firebase Cloud Messaging processes device/push identifiers and technical delivery data to deliver notifications. The native apps do not use advertising identifiers for personalised advertising. Optional web measurement is governed by the consent settings above.

7. Microsoft and PayPal

The Microsoft integration is optional. When connecting Microsoft 365/Exchange Online, OAuth tokens are stored encrypted and used only for calendar/task functions requested by you. PayPal is used only when you choose an offered PayPal payment/subscription flow; payment details are processed directly by PayPal while log.cam stores references and billing status.

8. Local storage and offline mode

The app stores selected account content, settings and a sync queue locally on the device for offline use and synchronisation. Session tokens are kept using secure device storage. In the browser, the Flutter web app uses browser storage technologies (for example IndexedDB/Local Storage through its local app store) where required for sign-in, settings and offline functionality. These technologies are not used for advertising.

9. Recipients and processors

We do not sell data for advertising. Recipients are limited to technical service providers or configured integration/AI providers necessary for a feature activated by you or the server operator. Where a company acts as a processor, appropriate data-protection obligations are applied.

10. Retention

  • Account content is generally retained until you delete it or the account is deleted.
  • Unverified accounts are automatically removed after the configured short period; the distributed build uses a minimum of 30 minutes.
  • Security/audit and change logs are normally retained for no more than 180 days in the distributed system.
  • Completed/failed background jobs are normally retained for no more than 45 days.
  • Expired magic-link, app-login and OAuth state records are removed after a technical grace period.
  • Business/accounting records that must legally be retained may be kept outside the operational app account for the legally required period.

11. Account deletion and withdrawal

You can initiate full account deletion in the app under Settings → Delete account permanently. A public deletion path is also available at www.log.cam/account-deletion.html. After successful confirmation, the account and associated ideas, projects, meetings, uploads and other account data are deleted; only technically or legally required residual data is retained where necessary.

You can withdraw consent for optional features for the future by revoking permissions, disconnecting integrations or no longer using the feature. See Privacy choices.

12. Your rights

Where the legal requirements are met, you may have rights of access, rectification, erasure, restriction, portability and objection, and you can withdraw consent for the future. You may also lodge a complaint with a competent data protection supervisory authority.

13. Children

log.cam is not specifically directed at children. Accounts should only be used by persons who can validly consent/contract under the rules applicable to them or whose use is otherwise appropriately authorised.

14. Security

log.cam uses measures including TLS-protected transport, hashed one-time/authentication tokens, encrypted server-side secrets, role-based access control and time-limited authentication flows. No technical system can guarantee absolute security.

15. Changes

We update this policy when features, providers or legal requirements change. The current version is published on this page.