Privacy policy (GDPR)
In brief
Sigmoney is for managing and getting an overview of personal finances.
Each user’s financial data is kept separate from other users’ data and access to it is technically restricted. Sigmoney does not sell data, does not show advertising and does not use personal data to track users across apps or websites for advertising purposes.
Some features require our technical service providers to process data; they are described below.
Sigmoney is not designed or promoted specifically for children and does not provide financial, investment, tax or legal advice.
Who is responsible for the data
The operator of the service and controller of personal data is:
Hugo Hudačin, Via Sent 2, CH-7500 St. Moritz
Sigmoney is governed mainly by the Swiss Federal Act on Data Protection (FADP). Where the GDPR applies to a user’s processing, the relevant provisions of the GDPR apply as well.
What data we process
Account: email address, user identifier and data needed for authentication. We do not store the password in readable form; the authentication system keeps a cryptographically protected form of it.
Financial data: accounts, transactions, balances and their history, income, expenses, investment positions and portfolios, budgets, categorisation rules, recurring payments, goals, debts, assets, financial contracts and other data the user enters or that is taken from files they upload.
Uploaded files: bank and broker statements, PDF, CSV, XLSX, photos and contract documents.
Sigmoney is not designed to process data about health, political or religious opinions, sex life, genetic or biometric data or other special categories of personal data. Users should not upload such data to Sigmoney unless it is necessary and they are entitled to do so.
Broker connection: if the user voluntarily connects a supported broker, Sigmoney processes the API key and any API secret needed for synchronisation. After saving, the client app cannot read them back; the Sigmoney server uses them to run the synchronisation. The user should create a key with the minimum necessary permissions, ideally read-only, and can revoke it at any time directly with the broker.
Crypto: if the user adds a public crypto wallet address (or a Bitcoin xpub/ypub/zpub), we store it privately against their account and read balances from the blockchain. The address is public, but its balance and history can be seen on the blockchain, so we protect it as personal data; an xpub/zpub public key reveals all addresses of one wallet. We never ask for or store a seed phrase or a wallet’s private key. For an exchange (Binance, Kraken, Coinbase, Bybit, OKX, KuCoin) the same applies as for a broker: the key should be read-only; a key that can trade or withdraw is rejected and deleted by the server.
Device and usage data, if allowed: device model, operating system and its version, app version and runtime/update versions, language, time zone, the user’s email, a random identifier created by the app, the date of last activity and the days on which the app was active. We use this data for compatibility, updates, troubleshooting and basic statistics on app usage.
Feedback and support: if the user sends feedback or contacts support, we process the data they send us, for example email, name, subject, message text and technical information needed to solve the problem. Messages sent by email or web form may also be stored in the systems used for email communication, not only in the app’s database.
Proof of consent: we store the version of the Terms of use the user confirmed and the date of confirmation, as well as the date optional consents were granted or withdrawn.
For what purposes and on what legal basis we use data
Where the GDPR applies to a user, the main legal bases are as follows:
We process the account, financial data, documents and main Sigmoney functions because this is necessary to provide the service the user requests, that is, to perform a contract under Art. 6(1)(b) GDPR.
If the user allows optional processing of unknown documents by external AI systems, we process data on the basis of their consent under Art. 6(1)(a) GDPR. Consent can be withdrawn at any time in Settings → Privacy. Withdrawal does not affect the lawfulness of processing carried out before it was withdrawn.
We process optional device and activity data on the basis of the user’s consent. Once it is turned off, we stop collecting new data of this kind.
Security measures, prevention of abuse, solving technical problems, protecting our rights and reasonable handling of feedback or support may be based on our legitimate interest under Art. 6(1)(f) GDPR.
We may also process data where the law requires it under Art. 6(1)(c) GDPR.
Automated analysis
Sigmoney automatically categorises and analyses financial data to create overviews, budgets, trends, estimates and other user features.
Such processing may include automated evaluation of aspects of the user’s financial situation. However, Sigmoney does not use these analyses to make decisions that would have legal effects on the user or similarly significantly affect them.
For example, Sigmoney does not decide on granting a loan, insurance, an investment, a job or any other third-party service.
Where data is stored
Sigmoney’s primary database, authentication and storage are operated through Supabase in the West EU – Ireland region.
Data transferred between the app and our main services is protected by an encrypted connection. Supabase infrastructure uses encryption of stored data and backups.
However, the location of the main database in the EU does not mean that all data always stays exclusively in the EU. When some features are used, data may be processed by providers outside the EU or Switzerland.
Users’ access to data is restricted by database rules including Row Level Security. Files are stored in private storage and may be made available to the user through time-limited links.
Some operational or support processing by the provider may also take place outside the selected region.
Service providers and recipients of data
Supabase – database, authentication, server functions and storage.
Anthropic and/or OpenAI – if the user allows the relevant feature, they may process the text or image of a document that could not be processed by the regular parser, or a document intended for AI analysis. For their commercial/API products, under current rules content is by default not used to train models unless the customer explicitly allows it. Standard retention of API data may be limited in time and depends on the specific configuration and provider.
OCR.space – text recognition in supported features that use images.
Expo – technical infrastructure used to distribute and update the app; it may process technical data needed to deliver the service.
Cloudflare – infrastructure and protection of web services; it may process the IP address, browser information and other technical data necessary to transmit web content and protect the service.
Trading 212 – only if the user voluntarily connects their account. Through the API Sigmoney obtains the data the user has allowed to be shared.
Crypto exchanges (Binance, Kraken, Coinbase, Bybit, OKX, KuCoin) – only if the user voluntarily connects their account with a read-only key. The Sigmoney server sends them signed requests and receives balances.
Blockchain data providers (for example mempool.space, Blockstream, BlockCypher, PublicNode, Solana RPC, TronGrid, XRPL, Stellar Horizon, Koios and other public nodes) – only if the user adds a public wallet address. We send them that address (derived addresses for an xpub), not the user’s email or other data. Requests are sent by the Sigmoney server, so the providers do not see the user’s IP address.
Yahoo Finance, CoinGecko and frankfurter.dev – obtaining asset prices and exchange rates. Under the current architecture we send them mainly the asset identifier, ticker or currency code, not the user’s whole financial profile.
Cloudflare Turnstile – protection of public forms against automated abuse.
Resend and email service providers – delivery of email messages, especially support; they may process the email address, message content and technical delivery data.
Apple, Google or another distribution platform may separately process data related to downloading the app and using their store under their own terms and privacy policies.
We do not sell personal data.
We may disclose data where required by law, a binding decision of a court or competent authority, or where reasonably necessary to protect users, the service or our rights.
Transfers abroad
Some providers may process personal data in the USA or in other countries outside Switzerland and the EEA.
Where the law requires a special cross-border transfer mechanism, we rely on the relevant adequacy decision, the recipient’s participation in the relevant Data Privacy Framework, or standard contractual clauses and other appropriate safeguards under the GDPR and/or the Swiss FADP.
Who may have technical access
Other Sigmoney users have no access to another user’s financial data.
Sigmoney’s administrator interface is designed so that in normal operation it does not show users’ transactions, balances or investment positions.
However, authorised server processes, infrastructure providers and, in necessary cases, authorised persons may have the technical ability to access certain data where needed for operation, security, solving a serious problem, restoring the service or complying with a legal obligation.
We limit such access to what is necessary.
How long we keep data
We keep the data needed to provide Sigmoney for as long as the user account exists or until the user deletes it earlier.
Documents, transactions, accounts, investments and other user data are deleted using the deletion functions available in the app.
After optional consent is withdrawn, we stop collecting the relevant data. Data for which there is no other legal reason for further retention is deleted or anonymised.
We keep support communication and feedback for the period needed to handle the request and afterwards only for as long as is reasonably necessary for security, resolving disputes or complying with legal obligations.
Data may remain in technical backups for some time and is then removed in the normal overwrite cycle.
Some external providers may keep data for their own limited retention period under their contractual rules.
Deleting your account
The user can delete their account in Settings → Profile → Delete account.
By deleting the account we delete active user data and files linked to the account, except data we must keep temporarily because of a legal obligation, security, proving compliance with legal obligations or legitimate protection of legal claims.
Email communication with support may not technically be part of the Sigmoney account and may follow a separate retention period; the user may also ask for it to be deleted unless its further retention is needed for a legal reason.
Security
We use appropriate technical and organisational measures to protect personal data.
Sigmoney supports an app lock using a code and the system’s biometric authentication. Sigmoney does not receive or store a biometric template of your face or fingerprint; verification is performed by the device’s operating system.
The app PIN is not stored in readable form. The login session is kept using the operating system’s security mechanisms.
Database access is restricted using access policies and sensitive server keys are not part of the client code.
However, no internet system can be considered absolutely secure.
Security incident
If a personal data breach occurs, we will proceed according to the laws that apply to the incident.
Where the GDPR applies and the incident is likely to pose a risk to the rights and freedoms of natural persons, we will notify the competent supervisory authority without undue delay and, where possible, within 72 hours of becoming aware of it.
Where the Swiss FADP applies and the incident is likely to pose a high risk to the personality or fundamental rights of the persons concerned, we will notify the FDPIC as soon as possible.
We will inform affected users where applicable law requires it or where it is necessary to protect them.
Your rights
Depending on the laws that apply to the user, they may in particular have the right of access to data, rectification of inaccurate data, erasure, restriction of processing, data portability, objection to processing and withdrawal of consent.
Withdrawal of consent does not affect the lawfulness of processing carried out before it was withdrawn.
Many operations can be carried out directly in the app, including editing, exporting or deleting data and the account.
For other requests the user can contact us at kontakt@sigmoney.com.
We will respond to a request within the period set by the applicable law; under the GDPR this is generally one month and under Swiss rules information is generally provided within 30 days.
The user also has the right to lodge a complaint with the competent supervisory authority, in particular in the country of their habitual residence, place of work or the alleged infringement.
In Switzerland the supervisory authority is the Federal Data Protection and Information Commissioner (FDPIC/EDÖB).
Minor users
Sigmoney is not designed or promoted specifically for children.
A user who under the law of their country cannot independently enter into a contract to use Sigmoney may use the service only with the consent or assistance of a parent or legal guardian, where the law requires it.
Where a particular processing is based on consent and the law requires the consent of the person holding parental responsibility for a minor user, the relevant authorisation must be obtained before such processing.
If we find that personal data was processed without the necessary authorisation, we will take reasonable measures, including ending that processing or deleting the data.
Changes to this Privacy policy
We may update this Privacy policy when the way Sigmoney works, the technologies used, providers or legal requirements change.
We will always publish the current version and the date of the last update in the app and on the website.
In case of a significant change we will inform users in a reasonable way. If a change requires new consent, we will ask for it before starting the relevant processing.