Security and data protection
netclariq stores sensitive information about your finances. Here are, in detail and without empty promises, the measures we use to protect it.
Encryption in transit and at rest
All communication with netclariq travels over HTTPS, and data is stored encrypted on disk by our database provider.
Hosted in the European Union
The database and backups are hosted in European Union data centers, subject to GDPR.
Isolation by space
Each space is isolated through database-level access rules: a query only ever returns data from the spaces you belong to, with the role you've been assigned.
Server-verified access
Operations are validated on the server against your session: permissions never depend on what happens in the browser, and paid modules are also checked in the backend.
No connection to your bank
netclariq never asks for or stores bank credentials. You log transactions manually or import them from a file, so there's no access to your real accounts.
Payments outside our servers
Payments are processed by Paddle as our authorized reseller. Your card details never pass through netclariq: we only store the subscription status.
Your data is yours
You can export your transactions, balances, assets, and investments to CSV directly from the app, at any time and at no cost.
You can request deletion of your account and of any spaces you own by writing to info@dizabyte.es. Deletion is permanent.
We don't sell or share your financial data with third parties, and we never use it for advertising. The product is funded exclusively through subscriptions.
Who processes your data
| Provider | Purpose | Data |
|---|---|---|
| Supabase | Database, authentication, and backups | Account and financial data for the space |
| Paddle | Subscription billing and invoicing | Billing and payment data |
| Optional sign-in with a Google account | Email address and name |
The full detail, with legal bases and retention periods, is in the privacy policy.
Report a security issue
If you find a vulnerability, write to info@dizabyte.es with the steps to reproduce it. We'll respond and keep you updated on the fix. Please don't disclose it publicly until it's resolved.