Technical Privacy Policy

Privacy Policy for Freaklog (Android)

This document explains what data Freaklog processes, where that data is stored, and when network communication can happen. Freaklog is designed from the ground up as an offline-first journaling application with zero default network transmission.

Last updated: 2026-10-14 Scope: Freaklog Android Client License: GNU GPL-3.0

1. Core Privacy Architecture

  • Local Storage Only: All journal data, entries, doses, notes, and custom substances you create are stored exclusively in a sandboxed local SQLite database on your Android device.
  • No User Account: Freaklog does not require registration, login, phone numbers, or email addresses. There is no remote account database.
  • No Remote Cloud Sync by Default: Your data is never uploaded, synced, or backed up to any Freaklog server. If your device has no internet access, all core features work without degradation.

2. Data Stored Locally on Device

Depending on how you use Freaklog, local device storage holds:

  • Experience entries, ingestions, exact timestamps, administration routes, doses, ratings, and subjective journal notes.
  • Custom user-defined substances, substance categories, reminders, pacing intervals, and daily/weekly intake limits.
  • Local encrypted or plaintext export files that you explicitly generate.

This data is used solely to render your timeline, calculate active dosage curves, and trigger local notification reminders.

3. Optional Network Features

The core application contains zero background network polling. However, three optional user-initiated features involve network communication:

  • Discord / Webhook Dispatch: If you explicitly configure a webhook endpoint URL in settings or via the FreakQuery engine, event payloads are sent directly to that URL.
  • BYOK Gemini Assistant: If you provide your own Google Gemini API key to query contextual insights, relevant context from your journal is transmitted directly to Google's Gemini API endpoints using your personal key.
  • External Reference Updates: If you choose to refresh PsychonautWiki or TripSit reference datasets, a read-only fetch is made to download the latest static dataset.

If you do not configure or trigger these features, no network traffic is generated.

4. Health Connect and Biometrics (Optional)

Freaklog can optionally query Android Health Connect to overlay physiological context (such as resting heart rate, sleep duration, and blood pressure) alongside your timeline. This integration requires explicit runtime permissions in Android system settings, remains 100% on-device, and can be revoked at any time.

5. Encrypted Backups and Data Portability

  • You can export your complete database at any time in raw JSON or encrypted SQLite formats.
  • Encrypted exports use passphrase-derived keys (PBKDF2/AES-256) so only you can decrypt the contents.
  • You retain total authority over where backup files are saved (e.g. SD card, local folder, Syncthing directory).
  • You can delete all application data instantaneously using standard Android App Info > Clear Storage.

6. Third-Party Services

Freaklog does not embed advertising SDKs, Firebase Analytics, Google Crashlytics, or user-tracking beacons. If you choose to enable optional third-party integrations (such as Google Gemini APIs or Discord webhooks), data sent to those endpoints is governed by their respective privacy policies.

7. Controller & Contact

Responsible entity:

Emil Brücher-Herpel Hosting
Alicenstraße 18
64293 Darmstadt, Germany

Direct inquiries: [email protected]

8. Policy Revisions

Any revisions to this document will be reflected with an updated timestamp on this page. Because Freaklog does not collect contact information, users are encouraged to review this page or the open-source repository commit history.