Forgevera Labs · support@forgeveralabs.tech · Version 1.0 · Effective 2026-10-14
Forgevera Labs is the public brand of an individual / sole proprietor based in Indonesia (the “Operator”). The Operator is not a PT, CV, or other incorporated entity. Personal identity documents required for official verification are handled privately with payment, banking, tax, or government authorities and are not published here without the Operator’s approval.
This policy explains what the ForgeGuard SaaS web application processes at forgeveralabs.tech/forgeguard. The data controller is the individual Operator trading under the Forgevera Labs brand. It covers customer accounts and the monitoring data the software processes on your behalf. Privacy requests can be sent to support@forgeveralabs.tech.
Account data includes name, email, a hashed password, locale, status and timestamps. Monitoring configuration includes authorised website URLs, expected selectors/text, journey steps, interval and client label. Monitoring output includes status, timing, safe errors, incidents, resource usage, and screenshots for confirmed failures and recovery proof. Configured WooCommerce integrations send signed event type/status, site URL and plugin versions. We do not store full card numbers or CVV.
ForgeGuard is not designed to collect your customers’ personal data. Browser journeys block password, card and purchase selectors; screenshots mask inputs and configured private areas; healthy checks do not retain screenshots. Signed integrations do not send customer identity, order contents or card data. We do not store page response bodies or form submissions, and do not run advertising trackers inside the application.
To provide and operate monitoring; to authenticate you and keep your account secure; to send incident/recovery alerts you enable; to manage subscriptions and entitlements; to prevent abuse and fraud; and to comply with legal obligations.
Performance of our contract with you (the service), our legitimate interests in securing and improving the service, your consent where required (for example optional alert channels), and compliance with legal obligations.
We use a hosting infrastructure provider to operate the service, and a transactional email provider to deliver account and alert emails. If recurring billing is enabled, an approved payment provider processes payment and its processor acts as an independent controller for payment data. Secrets and third-party credentials are stored outside the public web root and are never exposed.
The ForgeGuard application uses a functional session cookie to keep you signed in. With your consent, Google Analytics 4 may also measure privacy-safe funnel events such as trial registration, first website setup, first monitoring setup, and verified paid conversion. See the Cookie & Analytics Notice.
Passwords are hashed with Argon2id. Sessions are regenerated on sign-in and protected with secure, HTTP-only cookies. Tenant data is isolated server-side. Access to production systems is restricted.
Account data is retained while your account is active. Monitoring history and private evidence follow your plan’s history window and evidence allowance, then are removed automatically. Expiring report links default to 7 days. On account closure, we delete or anonymise personal data within a reasonable period, except where legal, tax, or security retention is required.
Subject to applicable law (including the GDPR where it applies), you may request access to, correction of, or deletion of your personal data, object to or restrict certain processing, and request portability. Contact support@forgeveralabs.tech and we will respond within the time required by law.
You can request account closure via support@forgeveralabs.tech. We will confirm and process deletion as described in section 9.
Privacy requests: support@forgeveralabs.tech.
This document is self-authored and provided for transparency; it is not legal advice and has not been reviewed by external counsel.