Privacy and data

Privacy Notice

This notice explains what Diftiva records, why it is used, and the choices available to you. Diftiva doesn’t connect to your bank or move money.

Information you provide

  • Account details such as your email address, language, time zone, and base currency.
  • Planned and actual amounts, goals, goal assignments, amounts you mark as moved, corrections, notes, and receipts that you choose to add.
  • Information included in a data-access, correction, export, or deletion request.

Service and security information

Diftiva records an operational trace identifier, request method and path (without the query string), response status and duration, coarse signed-in/anonymous state, and a strictly limited set of browser and transport headers needed to operate, protect, and troubleshoot the service. Request bodies, cookies, authorization credentials, CSRF tokens, and URL query values are excluded from this structured request log.

A client IP address may be written only to a separate restricted operations log for abuse prevention and incident diagnosis; that log is configured for no more than seven days of retention. When a request is verifiably delivered by Cloudflare, its two-letter network country may be used to suggest an account region. A suggestion is not saved until you confirm it, and private-network requests receive no country suggestion.

When you sign out, a necessary browser marker may remain for up to 24 hours so an analytics identity can be cleared if the service is opened again on a shared browser. This marker is not used for advertising.

How the information is used

  • To provide planned-versus-actual tracking, goal assignment, and self-reported movement status.
  • To provide account, export, correction, and deletion-request features.
  • To protect the service, prevent misuse, investigate errors, and maintain reliability.
  • To improve product flows when you have separately chosen to allow optional analytics.

Diftiva does not sell your personal information.

Optional product analytics

Product analytics is off unless you opt in. When enabled, Diftiva creates random browser and session identifiers. It may record page views, navigation and primary-button actions, coarse scroll-depth milestones (25%, 50%, 75%, and 90%), and broad engagement-time ranges that help us understand whether a feature works. The same identifier may be used across the desktop and mobile sites so one action is not counted twice. If you are signed in, an event may also be linked to your Diftiva account.

These identifiers do not contain your name or email by themselves, but they are stable and can be account-linked. Diftiva therefore treats this data as pseudonymous rather than anonymous. Events must not contain spending amounts, merchant names, notes, email addresses, passwords, verification codes, uploaded images, or authentication tokens.

Analytics events are kept while needed to evaluate product flows, investigate reliability, handle a data request, or meet a legal or security obligation. Choosing “Use necessary cookies only” stops future optional events from this browser and rotates its analytics identifier; it does not by itself erase events already stored. Signed-in users can use the Data & Account controls for export or deletion requests.

You can change your choice through the cookie controls without losing access to core tracking features.

If you turn analytics off in your account, that choice overrides an “Allow product analytics” cookie in your browser. Browser events also require permission in that browser, so allowing analytics in your account does not bypass the cookie controls on a new browser.

Your data choices

  • Download a structured JSON copy of your Diftiva data after signing in.
  • Request correction of account information that cannot be edited directly.
  • Request account deletion and receive a reference number for the review process.

A deletion request is reviewed to confirm account ownership and scope before records are removed. Some limited records may be retained where reasonably necessary for security, fraud prevention, dispute handling, or legal obligations.

Sign in to manage data

Protect sensitive information

Do not put passwords, verification codes, full payment-card details, bank credentials, or information about another person in notes, receipts, or support requests.

Questions about privacy

A public support email has not yet been configured. The support channel is being prepared; see the Contact page for the current status.

Effective date: August 25, 2026