DECCF Privacy Policy
Effective date: 2026-10-05
Who is responsible
DECCF at deccf.app is operated by Per Wristel, Duvbergsvägen 65, 143 44 Vårby, Sweden. Contact deccf.app@outlook.com about your data. We are responsible for the account, security and service-administration processing described here. Where a business instructs us to process personal data in its calculations, our Data Processing Addendum also applies; that business remains responsible for its own purposes and lawful instructions.
Information we process and why
When you sign in with Google or Microsoft, Clerk processes your sign-in identity and the information supplied by that provider, such as your name, email address and profile picture. DECCF uses the authenticated identity to recognise your account and control access to your apps. We do not receive your Google or Microsoft password.
Your calculation content may include model code, inputs, uploaded text, assumptions, scenarios and results. You choose what to enter. We process this content to perform calculations and to save, restore or publish the work you request. It may contain personal data if you include information about identifiable people. Use only information you have the right to provide.
We also process permissions, connected-agent records, credit balances and service-usage records to provide requested features and administer the service. Technical connection information and request outcomes may be processed by us and our providers to operate the service, prevent abuse, diagnose faults and protect accounts. If you contact support, we use your message and contact details to respond.
Our legal basis for requested account and calculation services is performance of our agreement with you. Necessary security, abuse prevention, fault diagnosis and support administration rely on our legitimate interests in maintaining a reliable service and protecting users. We process records to meet legal obligations where applicable. We do not use a sign-in consent screen as blanket consent for unrelated purposes.
Calculating in a chat
Your chat provider processes your conversation under its own privacy terms. DECCF receives the model and inputs when an agent or widget calls DECCF to calculate or transfer the work. A temporary calculation without an account does not create an app on an account.
If your agent uses our local calculation module, execution takes place in the agent's environment. Its provider's handling of the conversation still applies. Opening a DECCF widget or choosing to save sends the required calculation information to DECCF. Save application transfers the model and current setup; after sign-in and confirmation, it becomes a private app on your account. Publishing is a separate action. Connected agents can use account data only within the permissions you grant, and you can revoke their connection.
Google and Microsoft information
These connections are used for sign-in and account identification. Google permissions cover identity, email and profile information. Microsoft sign-in also uses permission to read your profile and maintain sign-in access. Neither connection requests access to your mailbox contents.
We use provider account information only for sign-in and identifying your account, sharing it with Clerk as necessary to complete sign-in. We do not sell this information, use it for advertising or use it to train general-purpose AI models. Closing your DECCF account does not delete your independent Google or Microsoft account.
New public author labels and API addresses use an account alias rather than your sign-in name or email. Information you include in published app content remains part of that content.
Providers and international transfers
Clerk provides authentication, Vercel provides hosting and remote calculation infrastructure, and Neon provides database storage. They process information needed for these functions under the applicable service and data-processing agreements. They also handle some account, contact or service-generated information for their own purposes under their privacy notices. Chat providers and Google or Microsoft also have their own privacy terms.
The current Neon database is in AWS US East 1 (Northern Virginia, United States). Our providers and their subprocessors may process information in the United States and other countries where they operate. Their applicable agreements include safeguards such as the European Commission's Standard Contractual Clauses. Clerk's agreement provides for the EU–U.S. Data Privacy Framework where applicable, with contractual safeguards as an alternative. Contact us for further information or copies of applicable safeguards.
Provider details: Clerk data processing agreement, Clerk privacy notice, Vercel data processing agreement, Vercel privacy notice, Neon platform terms, Databricks data processing agreement and Databricks privacy notice.
Retention and account closure
Account data, private apps, saved cases, permissions, usage and credit records are kept while your account is active so we can provide the service and restore your work. You can use available controls to delete your own apps and cases. Account-bound agent operations retain outcome data to handle retries; results older than 24 hours are cleared when the next recovery check runs, while operation metadata remains until account closure. Necessary cookies and temporary browser storage support sign-in and calculation transfers.
Support messages are retained while handling your request and for necessary follow-up or legal claims. Minimal security and closure records are retained as needed to protect the service and prevent old credentials restoring a closed account. Other legally required records are retained for the applicable obligation. Contact us to request access, deletion or restriction of these records.
User settings → Close account removes private apps, saved cases, preferences, credit history, personal access tokens and agent connections from the active DECCF database. It revokes DECCF sign-in sessions and deletes your DECCF identity held by Clerk. If cleanup is interrupted, account activity is disabled and you can retry from the confirmation page.
At closure, unused published versions and private drafts are removed. Versions already required by other people's installations, saved cases or dependencies, together with their executable dependencies, are retained for reproducibility. They are hidden from Marketplace discovery, lose their published API endpoint and show Closed account as author. Retained content and other people's snapshots may contain information you provided. Their transaction records retain amounts, with the direct credit-owner reference replaced by Closed account. We do not promise automatic later removal of every archived version; contact support about personal data within retained material so we can assess deletion or restriction.
A minimal closure marker holds your opaque DECCF account identifier, closure status and timestamps. Pending cleanup also holds the verified sign-in subject and the hash of a closure-only retry cookie valid for 12 hours. Those retry fields are cleared when cleanup finishes; the cookie cannot access apps or perform agent operations.
The current Neon project has a six-hour database change-history window. This is not the lifetime of saved apps and does not establish how long every provider keeps separate logs or backups. Restorable history and providers' separate records follow their applicable retention rules. Deleted active data may remain temporarily in such records, with access restricted to their operational purpose.
Your rights
Where applicable, you may request access, correction, deletion, restriction or portability, or object to processing, particularly processing based on legitimate interests. If processing relies on consent, you may withdraw it without affecting earlier lawful processing. Contact deccf.app@outlook.com. We may need to verify your identity and will respond within applicable legal timeframes. An account-wide self-service export is not currently available; requests can be handled through support. The widget's Download calculation exports an available current own-model calculation, rather than all account data.
You may complain to the Swedish Authority for Privacy Protection, IMY, or another competent supervisory authority. For business-controlled calculation data, you can also contact the business responsible for that calculation.
Changes
We publish the current policy and effective date at this address. Material changes will be highlighted in the service or communicated through your account contact information as appropriate. Where a change requires a new choice or legal basis, we will address that before using information for the new purpose.