Privacy

What FennoraDesk handles

This page describes FennoraDesk product behavior. Railway hosts the production data volume and Auth0 handles sign-in. These providers and optional Stripe may process their own connection and account metadata. Provider processing regions have not been verified. The configured backups and retention are described on the data handling page.

Publisher: EMIRKAN BOLUKBAS LLC
Support: hello@getblaster.co

Inputs you submit

JSON, CSV, and XLSX inputs are held in memory while the requested analysis runs, then discarded. FennoraDesk does not connect to stores, banks, ad accounts, or external data feeds. The local synthetic demo accepts only fixed invented examples.

Sign-in and sessions

Production sign-in uses a configured OIDC provider. The application verifies the access token and keeps it in a server-side memory session for up to eight hours or until the access token expires, whichever comes first. Logging out or restarting the service clears the session. The browser receives only an opaque, secure session cookie. Sign-in does not collect a profile, email address, or password through FennoraDesk.

Source Memory

Source Memory saves facts only after an explicit save request. Each account is isolated. Fact text and its source, date, and evidence are encrypted in the configured database. Account and record lookup values remain in the database in hashed form. You can search, export all pages and revision history, or confirm deletion.

If you use a ChatGPT or Codex plugin, request inputs and tool results also pass through that platform under its own data controls and policy.

Optional payments

Billing actions are currently disabled. Existing billing records, if any, are not automatically deleted when billing is disabled. Deleting Source Memory facts does not delete billing or provider records.

Retention and deletion

Uploaded files are not retained by this application. Source Memory remains until you delete a record or all records for your account. Deleting Source Memory facts does not delete billing or provider records. Account memory has a published storage and revision limit on the data handling page. Hosting, OIDC, and payment providers may retain their own records under their terms.