Your money is personal. We treat it that way.

Email/account identifiers; the income, commitments, savings goals, balances and spending you choose to enter; subscription status; Community ideas, votes and participation; support requests and feedback; and limited technical/security data needed to operate the service. LeftAfter does not intentionally ask you to provide special-category personal data such as health, religion or political opinions in budgeting free-text fields, so avoid entering sensitive information that is not needed for your plan.

If you choose Google or Apple sign-in, that provider authenticates you and sends LeftAfter the account information needed to create or identify your LeftAfter account, such as a provider account identifier, email address and basic profile information depending on your provider choices. LeftAfter does not receive your Google or Apple password. Apple may provide a private relay email address if you choose Hide My Email.

LeftAfter can assign a generated alias and keep Community participation anonymous so your login email, phone number or provider profile does not become your public identity. You can change these controls in Privacy & Data. Privacy mode is pseudonymisation, not complete anonymity: LeftAfter and its necessary service providers still process the private account identifier needed for authentication, security, support and legal obligations.

If phone authentication is offered, you may choose a phone number instead of an email address for passwordless SMS verification. The number is treated as private account data and is not displayed as your Community identity. Phone authentication depends on a configured messaging provider and remains unavailable until that provider has been tested. You can continue to use other available sign-in methods instead.

LeftAfter may use Cloudflare Turnstile on signup, login or account-recovery forms to reduce automated abuse. When enabled, the browser runs a security challenge and sends the resulting short-lived verification token through Supabase Auth. The control stays disabled until both the public widget configuration and server-side verification secret are configured and tested.

If you choose to connect LeftAfter to ChatGPT through the LeftAfter plugin, OpenAI and ChatGPT process the requests you send and the LeftAfter tool responses needed to answer them under OpenAI's applicable terms and privacy controls. The connection uses OAuth, so ChatGPT does not receive your LeftAfter password. Connected tools may read your saved plan, upcoming payments and savings progress, run affordability checks, and may record an everyday spend only when you explicitly ask to record it. LeftAfter's row-level access controls limit account data to the authenticated user. You can disconnect the integration in ChatGPT to stop future access; disconnecting does not automatically delete information already processed by OpenAI under its applicable policies.

Tell LeftAfter uses LeftAfter's own server-side rules for straightforward calculations and supported edits. When the AI reasoning layer is enabled and a message needs deeper language understanding, LeftAfter may send the message, recent Tell LeftAfter conversation turns and a minimised copy of the relevant plan context through the configured AI gateway (currently Netlify AI Gateway in production) to the configured model provider so the request can be understood. The reasoning layer is not given unrestricted database access and does not receive your login password or bank-login credentials from LeftAfter.

If you choose the microphone in Tell LeftAfter, the browser, operating system or app WebView speech-recognition service may process microphone audio to produce a transcript. LeftAfter does not intentionally upload or store the raw microphone recording in its application database. The resulting transcript is placed into the Tell LeftAfter text field so you can review or edit it before sending. Microphone and speech-recognition access require device permission and can be disabled in your browser or device settings. Processing performed by the device or browser speech service is also subject to that platform provider's applicable terms and privacy controls.

LeftAfter does not intentionally send your entire account record to the model. The reasoning request is built from budgeting fields needed to understand the message, such as relevant balances, income, bills, savings or business-plan items. The service also attempts to redact obvious card-like numbers, IBAN-style account identifiers and password/PIN-style text before an AI request. Automated redaction cannot be guaranteed to catch every secret, so do not enter passwords, PINs, card details, bank-login credentials, government identifiers or other secrets into Tell LeftAfter.

The AI model cannot directly change your plan. If it interprets a requested edit, its output is converted back into LeftAfter's restricted command format, passed through the existing server-side parser and allow-list, and shown to you for review. A change is saved only after you confirm it, and the confirmation endpoint validates the allowed action again before updating your own plan.

The visible conversation is kept in the current browser session so follow-up questions can work. When AI reasoning is used, the selected recent turns are included in that model request and may be processed by the configured AI gateway and model provider under their applicable data-processing terms. A confirmed edit becomes ordinary plan data and follows the same access, export, correction and deletion rules as the rest of your plan.

The assistant is intended for budgeting details, plan questions, balances, income, bills, subscriptions, payment dates, spending and savings. It is not a bank or financial adviser. Speech recognition and AI reasoning can improve ease of use but do not make a transcript or answer infallible. Review the transcript, proposed changes and important figures before relying on them.

We process data to create and secure your account, calculate and save your plan, provide membership features including Tell LeftAfter, operate Community voting, support you, prevent abuse, meet legal obligations and understand the service using privacy-conscious analytics where enabled.

Core account, planning and in-product assistant processing is used to provide the LeftAfter features you request. Some records may be kept where law requires it. Security and limited service-improvement processing may rely on legitimate interests. Where consent is legally required—such as optional analytics or advertising tracking—we ask first and let you withdraw it.

We use service providers such as hosting/database, authentication, email and payment providers. If you choose the ChatGPT connection, OpenAI also processes the plugin requests and LeftAfter tool responses needed to provide that connected experience. When Tell LeftAfter's AI reasoning layer is enabled, the configured AI gateway (currently Netlify AI Gateway in production) and model provider also process the minimised reasoning request described above. When you choose Google or Apple sign-in, the selected identity provider processes the authentication request under its own applicable terms and privacy controls. When you choose voice input, your device, browser or operating-system speech-recognition service may process the microphone audio needed to create the transcript. If optional Google Analytics, Google Ads or Meta Pixel measurement is configured, it is controlled by your tracking choice and remains off until the relevant consent is given. We do not sell your personal financial data.

Members may see aggregate vote counts and percentages, not a list of who voted for which idea. Community ideas are presented without the author’s account email, phone number or provider identity. If alias attribution is introduced later, your Community identity preference controls whether an alias may be shown. Do not post financial or personal information in idea text that you do not want shared with the Community.

Account and planning data is kept while your account is active and is deleted or anonymised when it is no longer needed for the service, security, disputes or another lawful purpose. Dutch tax and accounting records that form part of LeftAfter's business administration are generally retained for 7 years where required by Dutch tax law; certain records, including applicable One Stop Shop or real-estate records, can require 10 years. Records subject to a legal hold, dispute or other statutory duty may be kept for the period that duty requires. We review retention so ordinary personal data is not kept longer than necessary.

Depending on the processing, you may ask to access, correct, erase, restrict or receive your personal data, object to certain processing, and withdraw consent at any time where processing relies on consent. Where the GDPR applies, we respond to valid rights requests without undue delay and normally within one month, subject to the extensions and exceptions allowed by law. You may also complain to your local data-protection authority, including the Dutch Autoriteit Persoonsgegevens.

If a service provider processes data outside the European Economic Area, LeftAfter will use an appropriate legal transfer mechanism where required.

The Founder Member Support view is designed to show only account and service metadata needed for support, such as account status, verification, membership state and whether a plan exists. It does not return the contents of your Personal or Business plan, balances, bills, debts, savings goals or spending amounts. Hosting, database and other infrastructure providers may still technically process stored data as needed to operate the service and are covered by the safeguards and provider disclosures in this notice.

We use authentication, access controls, database protections, rate limits and server-side validation intended to keep member data separated. Tell LeftAfter has no unrestricted database write access and cannot save a supported financial edit without a separate confirmation request. No online service can promise absolute security, so we continually review safeguards as LeftAfter develops. If a personal-data breach occurs, LeftAfter will assess it, record it as required and notify the competent authority and affected people where applicable law requires that notification.

LeftAfter is registered in the Netherlands under KVK 42181765 and remains in pre-launch development. Paid subscriptions and public checkout will stay disabled until the remaining tax and payment details are in place and the customer-facing billing information is finalised.