Privacy Policy

1. Who is responsible

Fluxus is operated by an individual developer; there is no company behind it yet. For anything in this policy you can reach the project via GitHub (public; do not include personal data in issues) or by email at legal@fluxuspay.app.

2. Data that stays on your device

Most of what Fluxus remembers lives only in your browser's local storage, under keys prefixed fluxus-. This includes your wallet address, local transaction history, contacts, merchant and split settings, subscription schedules, AI-assistant chat history, theme choice, and session preferences. This data never reaches our servers. You can delete it at any time by clearing site data for fluxuspay.app in your browser; the app keeps working, you simply start with an empty local state.

3. Passkeys

Your wallet key is a passkey created and stored by your device's own platform authenticator (Face ID, Touch ID, Windows Hello, or a security key). The private key never leaves your device. The server component only sees the public credential needed to verify your signatures and derive your wallet address.

4. Public blockchain data

When you send a payment, the transaction (sender address, recipient address, token, amount, and any memo text) is written to the public Tempo blockchain. This data is replicated across the network, visible to anyone in a block explorer, and permanent. It cannot be edited or deleted by Fluxus or anyone else. This is a hard technical limit on the right to erasure: we can delete data we hold, but nobody can delete data from the chain. Memos are stored in cleartext; treat them as public.

5. Analytics

If analytics is enabled for a deployment, Fluxus uses PostHog to count product events, for example that a payment was sent from a given screen, with which token symbol. These events do not include wallet addresses, amounts, memo text, or chat content. Analytics is skipped entirely when your browser sends the Do Not Track signal, and the app does not currently identify users to PostHog. PostHog is a third-party processor; events are stored on its servers ( {{POSTHOG_REGION}}; region depends on deployment configuration). Retention of analytics events follows PostHog project settings ( {{DATA_RETENTION_ANALYTICS}}).

6. Data we store server-side

The server keeps two narrow kinds of data:

• Push subscriptions. If you enable notifications, your browser's push endpoint is stored in a Redis database (Upstash), keyed by your wallet address. It is deleted when you unsubscribe or when delivery permanently fails.
• Rate-limit counters. Short-lived counters keyed by IP address or wallet address protect the fee sponsor and the API from abuse. They expire automatically.

Fluxus is hosted on Vercel, which processes standard request logs (including IP addresses) to serve the site. Upstash and Vercel are third-party processors.

7. AI assistant

Messages you type to the AI assistant are sent to a third-party language-model provider to generate a reply: currently Groq first, then Google (Gemini) or OpenRouter as fallbacks, depending on availability. Do not put sensitive personal information in assistant messages. Fluxus does not store your chat on the server; the conversation history you see is kept in your browser only.

8. Legal bases and purposes

Where the GDPR applies, Fluxus processes data to provide the service you request (performance of a contract: executing payments, sending notifications you enabled), and in its legitimate interest to keep the service secure and un-abused (rate limiting, request logs). Analytics, where enabled, relies on {{ANALYTICS_LEGAL_BASIS}}; this must be settled in legal review, since no consent banner exists today.

9. Your rights

Under the GDPR you can ask for access to, correction of, or deletion of data we hold about you, object to processing, and lodge a complaint with a supervisory authority. In practice: local data you delete yourself in the browser; push subscriptions are removed by unsubscribing or on request; analytics deletion requests are forwarded to PostHog. On-chain data cannot be deleted by anyone (see section 4). Requests: legal@fluxuspay.app.

10. Changes

This policy will change as the product evolves, and this draft will be replaced by a lawyer-reviewed version. The date above identifies the current text.