Privacy Policy
1. Who we are
ifrCoworker is operated by SPOCONT Ltd. (SPOCONT Kft.), registered office: 51 Petőfi Street, 8112 Zichyújfalu, Hungary; EU VAT number: HU24243069. SPOCONT Ltd. is the controller of the personal data described in this policy.
Contact for every privacy question and request: hello@ifrcoworker.com.
2. What data we collect
2.1 Google Sign-In
You sign in to ifrCoworker with your Google account. We request only the openid, email and profile scopes, and we accept a sign-in only when Google reports the email address as verified. From Google we receive:
- your email address;
- your Google account identifier (the
subvalue); - your name, first name and profile picture link.
We do not request access to your Gmail, Google Drive, contacts, calendar or any other Google data, and we receive no Google access that outlives the sign-in. These values are placed in a signed session cookie on your device (see section 2.7). Your email address is the identifier of your ifrCoworker account: it is the only Google value we store in our database, attached to the records described below.
2.2 Payments and invoicing
When you buy a request pack, you enter invoice details: company name, VAT number (optional), billing address and country. Payment itself is made on the checkout page of Revolut, our payment provider; we never receive your card number. We store a payment record holding your email address, the pack bought (number of requests, validity), your invoice details, the Revolut order identifier, the amount, the currency and the order status Revolut reports. A VAT number is checked against the EU VIES service when the payment is confirmed, and the invoice details are emailed to our staff so that the invoice can be issued. A free trial or free access is recorded in the same way, without payment or invoice details.
2.3 Usage records (quota and billing)
Each charged request — a calculation or validation through the REST API, the MCP server or the A2A endpoint, or a workbook download — creates one usage record holding: your email address, the pack it is charged to, the standard and operation called, the channel (API, MCP or A2A), the name of the calling client application (the X-MCP-Client header or the browser or client User-Agent), the credits charged, the request's correlation identifier, the duration, the IP address of the request and the time. These records enforce your quota and are shown to you as your usage ledger on the access page.
2.4 API keys and connected apps
- API keys. When you create an API key we store a SHA-256 hash of it — never the key itself, which is shown to you once — with the name you gave it, its first characters (so that you can recognise it), your email address, and when it was created, last used (to the hour) and revoked.
- Connected apps. When you connect an AI agent to your account through OAuth, we store a grant: your email address, the client's identifier and name, its return address, the scope, a hash of the current refresh token and of the tokens it replaced, and when the grant was created, last used, expires and was revoked. Redeemed one-time authorisation codes are kept only as a hash, until the code would have expired.
2.5 Calculation inputs and outputs
The figures you send for calculation are processed to produce the answer and are not stored, with two exceptions:
- Workbook download. For 24 hours after a calculation that offers a workbook download, the request as received and its results (journal entries, statements, disclosure notes, workings), your email address and the reporting dates are kept so that you can download the workbook; they are then deleted automatically.
- Results you flag for review. When you (or your agent) flag a result as wrong, what the flag carries — the input, the output it refers to, the proposed answer, your reasoning and your email address — is kept for 90 days to investigate it, then deleted automatically.
The engine also keeps quality records of refused or incomplete calculations. They hold field names, codes and counts only — never your figures and never your email address.
2.6 Daily IFRS quiz
The daily quiz requires sign-in so that we can show the question set your pack entitles you to. Your answers are checked and the result is shown to you; your answers are not stored and not logged.
2.7 Cookies
We set only strictly necessary cookies, both HttpOnly, and no advertising or analytics cookies on ifrCoworker:
__session— your signed sign-in session (the Google values listed in section 2.1); it expires after 21 hours or when you sign out.__oauth_state— a random value that protects the sign-in against forgery, with the page to return to; it expires after 5 minutes and is deleted when the sign-in completes.
2.8 Messages you send us
When you use the contact form on the access page, your email address, your message and the page you sent it from are emailed to our support mailbox and a copy is stored in our database.
2.9 Technical logs
Our servers write operational logs. They record events such as a successful sign-in, a trial or purchase started, and an API key created or a connection revoked, with your email address. For the MCP server, a log line records only the protocol method, the protocol version and the names of the capabilities the client declares — never a token, a header value or a calculation argument. The IP address of each request is also used, transiently, for rate limiting and abuse protection.
The access page loads its fonts from Google Fonts, so your browser sends your IP address to Google when it loads that page.
3. Purposes and legal bases
We process personal data under Article 6(1) of the General Data Protection Regulation (GDPR):
- Performance of a contract — Art. 6(1)(b): signing you in; providing the calculations; enforcing your quota and showing your usage; API keys and connected apps; workbook downloads; the daily quiz; answering your messages.
- Legal obligation — Art. 6(1)(c): issuing invoices and keeping payment and invoicing records as accounting and tax law requires, including the VAT number check.
- Legitimate interests — Art. 6(1)(f): security, rate limiting and abuse prevention; operational logs; investigating results you flag and improving the accuracy of the engine.
4. Google user data
We use the data received from Google Sign-In (section 2.1) only to sign you in and to identify your ifrCoworker account — to attach your purchases, quota, usage, API keys and connected apps to you, and to reply when you write to us. We do not sell Google user data, we do not use it for advertising, and we do not transfer it to anyone except as necessary to provide the service (section 5) or as required by law. No person at SPOCONT Ltd. reads it except with your consent, for security purposes, or to comply with the law.
ifrCoworker's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Sharing and processors
We do not sell personal data and do not use it for marketing. We share it only with the providers that run the service for us, each for the purpose named:
- Clever Cloud — hosting of the application and its logs.
- Google — sign-in (Google Sign-In); the email delivery queue (Google Cloud Tasks, region europe-central2), through which contact-form and payment notification emails pass; web fonts on the access page.
- Zoho — sending email (EU mail server).
- Revolut — payment processing.
- The European Commission's VIES service — validation of a VAT number you enter.
We may disclose personal data where the law requires it, for example at the valid request of a court or public authority.
6. International transfers
Our servers are in the European Union. Google and Revolut are international groups and may process the data they handle for us outside the European Economic Area; where they do, the transfer relies on the safeguards those providers offer under Chapter V of the GDPR, such as an adequacy decision or the European Commission's standard contractual clauses.
7. How long we keep data
- Session cookie: 21 hours, or until you sign out. Sign-in state cookie: 5 minutes at most.
- Workbook downloads: 24 hours, then deleted automatically.
- Flagged results: 90 days, then deleted automatically.
- Connected apps: a grant stops working after 90 days without use or when you disconnect it on the access page; the grant record is kept until you ask us to delete it or your account is closed. Redeemed authorisation codes: deleted automatically once expired.
- API keys: until you revoke them; the revoked key's record (hash, name, dates) is kept until you ask us to delete it or your account is closed.
- Usage records: 12 months, then deleted automatically (sooner if you ask us to delete them or your account is closed).
- Contact messages: until you ask us to delete them or your account is closed.
- Payment and invoicing records: for as long as accounting and tax law requires us to keep them, even after an erasure request.
- Quiz answers: not stored.
8. Security
All traffic is encrypted in transit (HTTPS). The session cookie is signed and not readable by page scripts. API keys, refresh tokens and authorisation codes are stored only as hashes, so a copy of our database does not reveal them. No method of transmission or storage is completely secure, but we work to protect your data and will notify a personal data breach to the supervisory authority, and to you where it is likely to put you at high risk, as the GDPR requires.
9. Your rights
Under the GDPR you have the right to:
- access the personal data we hold about you and receive a copy;
- rectification of inaccurate data;
- erasure of your data, except what we must keep by law;
- restriction of processing;
- data portability — your data in a structured, machine-readable format;
- object to processing based on our legitimate interests;
- withdraw consent where processing is based on consent, without affecting earlier processing.
You also have the right to lodge a complaint with a supervisory authority. In Hungary this is the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság, NAIH), naih.hu; you may also complain to the authority of your EU country of residence.
10. How to ask for deletion or exercise your rights
Email hello@ifrcoworker.com from the email address of your ifrCoworker account and tell us what you are asking for. We answer within one month, as the GDPR requires. On an erasure request we delete your account data — usage records, API keys, connected apps, contact messages and any flagged results — except the payment and invoicing records the law requires us to keep. You can revoke an API key or disconnect a connected app yourself at any time on the access page, and you can remove ifrCoworker's sign-in access from your Google account at myaccount.google.com/permissions.
11. Children
ifrCoworker is a professional tool for financial reporting and is not directed at children. We do not knowingly collect personal data of anyone under 16; if you believe a child has given us personal data, contact us and we will delete it.
12. Changes to this policy
We may update this policy when the service or the law changes. The current version is always at ifrcoworker.app/privacy, with its effective date at the top. Where a change materially affects how we use your data, we will tell you before it takes effect.