What vatnode Logs About Your Account, and How Long
16 Nov 2026

vatnode records account creation, every sign-in, every use of ‘Sign out other devices’, the creation of a live API key and the revocation of a key, and shows the latest 20 of those events on your Security page. For sign-ins recorded with an IP address, the IP and user agent are removed after 30 days, and the rows are deleted after one year.
What vatnode records about account activity
Two logs feed the activity view: a security events log for account creation, sign-ins and signing out other devices, and an audit log for API key changes.
| Event | Stored fields |
|---|---|
| Account created | Time only. No IP address, no user agent. |
| Sign-in (every new session) | Time, IP address, user agent. |
| Other devices signed out | Time, IP address, user agent. |
| Live API key created | Time, key label, IP address. No user agent. |
| API key revoked | Time, IP address. No label, no user agent. |
The audit log also records account deletion, billing events such as a cancellation, and changes vatnode support makes on your behalf. Those entries are kept on the same schedule but do not appear in the activity card.
A sign-in is logged the same way whether you used Google, GitHub or an emailed sign-in link or code.
What it does not record
- Logouts.
- Failed sign-ins.
- Requests for a sign-in link or code.
- Regenerating the test key. It writes no log row and sends no email.
API calls are not sign-ins either: a VAT check made with an API key creates no security event. The check stores the client user agent and no IP address.
Who can see it
You can, on the Security page of the dashboard, in the ‘Recent activity’ card. It lists the latest 20 events, newest first, with the user agent shortened to something like ‘Chrome 120 on Mac’. It is not the full history.
The card is backed by GET /v1/me/security-events, which accepts only a dashboard session cookie. An API key does not work on it. The response looks like this (fictitious values):
{
"events": [
{
"id": "7c1e5b0a-3f64-4d0e-9a52-1b8f6e2d4c90",
"category": "api_key",
"label": "API key created: \"checkout-prod\"",
"ip": "198.51.100.24",
"userAgent": null,
"createdAt": "2026-11-12T09:41:07.000Z"
},
{
"id": "e04a9d27-81c3-4b5f-a6d0-52f7c3b19e68",
"category": "auth",
"label": "Sign-in",
"ip": "203.0.113.58",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 Chrome/120.0.0.0 Safari/537.36",
"createdAt": "2026-11-12T09:38:52.000Z"
},
{
"id": "2b96f3c8-d715-4e0a-8c41-9a07d5e6b123",
"category": "auth",
"label": "Account created",
"ip": null,
"userAgent": null,
"createdAt": "2026-11-03T14:05:19.000Z"
}
]
}
category is auth or api_key, and ip is null when no address was captured. The dashboard shows that case as ‘IP unknown’.
vatnode support can also read a user’s security events through admin tooling. Access to production systems is limited to authorised personnel, as the privacy policy describes.
How long it is kept
| Log | IP address and user agent | Rows |
|---|---|---|
| Security events | Removed after 30 days | Deleted after one year |
| Audit log | IP removed after 30 days | Deleted after one year |
For security events, the 30-day removal applies to sign-ins recorded with an IP address. A daily job at 03:00 UTC applies both periods. They cover these two logs only; they are not a general statement about every IP address vatnode ever sees. If you delete your account, the security events and audit entries are de-linked from it when the account record is purged. That happens 30 days after the deletion request, or later if a payment still has to be reconciled first.
The legal basis is legitimate interests under Art. 6(1)(f) GDPR: account security, fraud prevention, and enabling customers to demonstrate compliance in their own audit trails. The privacy policy is the authoritative text. The DPA and the subprocessor list cover the processing side, and rights requests go to [email protected].
Which emails vatnode sends
The new sign-in email has the subject ‘New sign-in to your vatnode account’. It goes out when a sign-in comes from an IP address that does not appear in your account’s sign-ins over the previous 30 days. The lookback matches the retention, so the comparison runs against the addresses vatnode still holds. It is not sent when no earlier sign-in is on record, such as your very first sign-in, where the welcome email goes out instead. The email shows the time in UTC, the IP address and the raw device and browser string, with a button to your API keys.
Creating a live key or revoking a key also sends an email, with the key’s label, its last four characters and the IP address. That email is covered in structuring vatnode API keys across teams.
What to do about an unexpected event
vatnode has no passwords. Whoever controls your email inbox, or your Google or GitHub account, can sign in as you, so start there.
- Secure the inbox and the Google or GitHub account you sign in with.
- On the Security page, press ‘Sign out other devices’. It ends every other session and keeps the one you are using, whereas signing out normally ends only the browser you are in. Then write to [email protected] with the event you saw.
- Open API keys and revoke any live key you did not create. Live keys are stored as hashes and shown in full only once, at creation, so keys you created earlier cannot be read back from the dashboard.
- List your webhooks with
GET /v1/webhooks, using one of your own live keys (test keys are not accepted there), and delete any you did not add, or whose URL you did not set, withDELETE /v1/webhooks/{id}. The VAT monitoring page shows only one webhook, so one added later does not appear there. - Check your VAT monitoring subscriptions and the alert email address there.
- Check the requester VAT in Account details, and your plan and billing details.
- Regenerate the test key.
Using this in a vendor review
| Reviewer question | Answer |
|---|---|
| Are sign-ins and key changes logged? | Yes, see the first table. |
| Are failed sign-ins and logouts logged? | No. Neither are requests for a sign-in link or code. |
| Can the customer see the log? | Yes, the latest 20 events on the Security page. vatnode support can read it too. |
| Can the log be exported or scripted? | Not through the API. The endpoint accepts a dashboard session only, and API keys do not work on it. A copy of your personal data, including these logs, can be requested from [email protected]. |
| Is the customer alerted? | Yes, by email for a sign-in from an IP address not seen in the previous 30 days, for a new live key and for a revoked key. |
| How long are IP addresses kept? | In these two logs, 30 days; rows are deleted after one year. |
| What happens on account deletion? | Security events and audit entries are de-linked when the account record is purged, 30 days after the request or later if a payment is still being reconciled. |
| Passwords? | None. Sign-in is Google, GitHub or an emailed link or code, so account security rests on those. |
| Legal basis and processors? | Privacy policy, DPA, subprocessors |
| Where is VAT check evidence? | Exporting VAT check history for audit, VAT audit trail |
For how check data is stored, see GDPR and VAT data storage. Every vatnode account has the Security page, Free included. After you register, the ‘Recent activity’ card shows your account creation and first sign-in straight away. How keys are issued and sent is in the authentication docs, and pricing lists how many keys each plan allows.
FAQ
What does vatnode log about my account activity?
Account creation, every sign-in, every use of ‘Sign out other devices’, the creation of a live API key and the revocation of a key. Sign-ins and sign-outs of other devices store the time, IP address and user agent. Key events store the IP address, and a creation also stores the key label. Logouts, failed sign-ins and requests for a sign-in link or code are not recorded.
How long do vatnode’s account activity logs keep IP addresses and user agents?
For sign-ins recorded with an IP address, the IP and user agent are removed after 30 days, and the event row itself is deleted after one year. In the audit log that holds API key changes, the IP is removed after 30 days and the rows are deleted after one year. These periods apply to those two logs only.
Does vatnode send an email when someone signs in from a new device?
It sends one when a sign-in comes from an IP address that has not appeared in your account sign-ins during the previous 30 days. The trigger is the IP address, not the device, so the same browser on a new network triggers it and a new browser on a known network does not. It is not sent when no earlier sign-in is on record, such as your very first sign-in.
What should I do if I see a sign-in I don’t recognise?
Secure the email inbox and the Google or GitHub account you sign in with, because vatnode has no passwords, then press ‘Sign out other devices’ on the Security page and write to [email protected]. Revoke any live API key you did not create, delete webhooks you did not add or whose URL you did not set, check monitoring subscriptions and the alert email address, the requester VAT and your plan and billing details, and regenerate the test key.