Privacy Policy

Operator and privacy contact

Digital Magnet Corporation operates SecurityFuse, with its registered address at 196 McIntyre Drive, Kitchener, Ontario, Canada N2R 1H4.

For privacy inquiries and requests, contact Mazen Bakhbakhi, Managing Director, at hello@securityfuse.com.

Information and purposes

We currently process sign-in and account information, residence and admission records, and correspondence you provide. Policy-acceptance records are collected when agreements are accepted. Hosted scanning is not currently enabled; submitted targets, target-authorization records, scoped evidence and scan metadata will be processed only when the relevant assessment is enabled and authorized.

After sign-in, we record your country of residence, applicable Canadian province or territory, and admission decision against your sign-in identity. Eligible answers can activate invitation access automatically. The residence question does not collect an adult-eligibility attestation or accept agreements.

If repository assessment is offered, it may temporarily process selected source files under separate grants and processing rules. Repository code is not executed by the assessment.

We use information to administer accounts, respond to support and privacy requests, troubleshoot the service, investigate incidents, abuse and authorization disputes, and meet legal obligations. Scan-related processing applies only when the relevant assessment is enabled and authorized.

The current public-site application sets no cookies and the current website and app use no analytics. Browsers may still retain legacy parent-domain _ga and _ga_* cookies from the retired site until they expire or are cleared; we do not use those cookies.

System follows your device’s appearance; an explicit Light or Dark choice is remembered in localStorage under the single key sf-theme.

Our hosting providers may process connection and diagnostic information separately from the website itself.

People under 18

SecurityFuse is not directed to people under 18.

If we discover that we collected personal information from someone under 18, we delete it subject to applicable legal requirements.

Providers and selected deployment

Cloudflare provides DNS and Email Routing, forwarding messages addressed to hello@securityfuse.com and security@securityfuse.com.

Google Gmail receives and stores the forwarded correspondence in the owner’s mailbox.

Clerk is the selected authentication provider for the invitation beta.

Cloudflare R2 has a private bucket provisioned for planned backups, with a 30-day deletion rule. The bucket is empty and no database backup job is operational. R2 is not currently an operational scan-evidence store or database-backup service.

Contabo hosts the application in the United States and provides the United States server we intend to use for scanning. Hosted scanning is not enabled.

IONOS hosts the public website in the United States. Our hosting providers may process connection and diagnostic information.

Resend sends email composed manually by the owner, including Gmail send mail as through Resend SMTP, and Clerk’s automated sign-up and authentication messages. Resend email logs and events are retained for 30 days on the current plan. Resend sending is limited to the securityfuse.com domain. No separate application-generated service-notice pipeline is represented here.

Legal bases by purpose

Where a legal basis is required, we process account information and run authorized scans because it is necessary to provide the service under our Terms (contract).

We process information for security, abuse prevention and authorization disputes based on our legitimate interests in protecting the service, scan targets and users.

We process support and privacy correspondence based on our legitimate interests in answering requests, and to meet legal obligations where a request exercises a privacy right.

We keep required records, such as privacy-breach records, to comply with legal obligations.

Optional or changed processing, including any future AI processing, happens only with your consent, which you can withdraw.

International processing and transfers

The application host and allocated scanner host are in the United States. Our selected Clerk, Resend, Cloudflare and Google services process information in the United States, and IONOS hosts the public website there. Information may therefore be processed outside Canada; no narrower processing location is represented here.

We use these providers under the standard service terms accepted at sign-up and remain responsible for our handling of personal information under applicable law. We do not represent that separately negotiated data-processing agreements are in place.

We do not admit EU/EEA or UK residents to beta until the applicable EU and separate UK representative requirements are assessed and any required representatives appointed.

How we protect information

We use HTTPS/TLS to protect personal information in transit.

No database backup or restore process is operating at present. Before we rely on backups stored separately from the main database, we must check their encryption, expiry and restoration, including that deleted data cannot reappear.

Internal administrative access to account information, correspondence and scan evidence is restricted to the owner and necessary service, support, privacy, security and legal tasks.

Supported redaction is applied to scan evidence before it is retained.

These safeguards do not promise that every secret or vulnerability is detected or that an incident cannot occur.

Data use, AI and confidentiality

We do not sell customer data, use it for advertising or train AI models with it.

Optional AI processing stays disabled for the initial invitation beta.

The default deterministic website-scanner path leaves model analysis unassessed and contains no model invocation.

Enabling optional AI processing requires separate review of providers, permitted data and excerpts, approvals, retention/training terms, transfers and fallback rules, with any required disclosure and permission.

Non-public scan findings remain confidential; public use of findings or aggregate research requires a separately reviewed approach and any required permissions, and internal approval is not customer permission.

Privacy breaches

The owner personally handles security incidents and privacy requests and will notify affected individuals and regulators of a privacy breach where required by applicable law.

We keep a record of each privacy breach for at least 24 months after the day we determine the breach occurred, or longer where applicable law requires it.

Retention and owner-handled deletion

Scan evidence is subject to a 30-day retention limit after completion, failure or cancellation. Hosted scanning is currently disabled. When such records exist, the owner handles deletion manually until automated cleanup is operational; access-expiry controls are not a claim that physical deletion runs automatically.

No database backups currently exist. The provisioned R2 bucket has a rolling 30-day deletion rule for planned backup objects; a lifecycle rule alone does not create a backup.

Scan metadata is subject to a 90-day retention limit after completion, failure or cancellation. The owner handles deletion manually; automatic cleanup is not operating.

If backups are enabled later, their copy-retention and deletion handling will be disclosed before they are used. We do not claim an additional backup-copy retention window is operating today.

For supported repository processing, temporary source is removed on completion or failure. The cleanup limit for leftovers is 24 hours; the owner handles any required cleanup manually until automatic cleanup has been checked and enabled. Temporary source is not designated for backup.

Routine support and security email is subject to a retention limit of 12 months after the matter closes. The owner handles deletion manually and removes sensitive attachments sooner when they are no longer needed.

Our website host keeps standard access logs (IP address, requested page, browser details and time) for up to 30 days. The app does not keep visitor access logs on our servers. Server logs are kept for up to 30 days; some service logs rotate by size, and the owner deletes them manually when no longer needed.

Privacy-breach records are retained for at least 24 months after the day we determine the breach occurred, or longer where applicable law requires it.

Minimal policy-acceptance records are subject to a retention limit of 12 months after supersession by a newer acceptance or account closure. Scan-authorization records follow the 90-day scan-metadata limit. The owner handles deletion manually; no automated acceptance-record expiry job is operating.

Residence answers and admission decisions are kept while access is active and are subject to deletion within one calendar month after access ends. Rejected or held records are subject to deletion within one calendar month of the decision. The owner handles deletion manually until automated cleanup is operating.

Account information is held for active account administration and follows the account-closure and deletion process below.

Future restore safeguards, stalled scans and retained metadata

We do not yet have separate deletion records and checks to prevent deleted data from reappearing when a backup is restored. Existing cleanup records do not provide that guarantee.

Before backups can be restored, we must put in place and check records of deletions that contain no deleted content, and a process that prevents deleted data from reappearing. Those records must remain until every backup capable of restoring the deleted data has expired, then be deleted within a further 30 days. This is a requirement for a future process, not a safeguard operating now.

A scan that has not completed, failed or been cancelled within 24 hours is subject to failure handling. Hosted scanning and automatic cleanup are not enabled; the owner handles any required intervention manually.

For a stalled scan, retention clocks use creation time plus 24 hours, not the later time at which an owner or cleanup process detects it.

After evidence expiry, findings and scores are unavailable through expired-evidence views. Until the 90-day metadata limit, records can also include authorization actor, idempotency and payload-hash fields, parent or deployment relationships and accounting metadata, in addition to scan ID, target, profile, state and timestamps. We do not claim that storage contains only those five fields.

Deletion, restore and account closure

Viewing, downloading or linking a report does not restart retention of service-held evidence or metadata, and each new scan has its own period.

Retention limits apply to service-controlled derived records, links, exports and retained review snapshots. The owner handles required deletion manually until automation is operational. Copies downloaded and controlled by a user are distinct.

Request closure or deletion at hello@securityfuse.com. The owner personally verifies identity proportionately and handles deletion from live stores without undue delay, normally within one calendar month, subject to applicable law. This is an owner-operated process, not an automated deletion service.

We explain legally justified exceptions and shared-workspace records that must remain; a shared record is not automatically exempt from deletion.

We may close an account after 12 months without sign-in or authorized scanning, with 30 calendar days’ email notice and an opportunity to keep it open by signing in.

Privacy requests and complaints

Contact hello@securityfuse.com for access, correction, deletion or other applicable privacy rights, which may include restriction, objection or portability depending on the law and processing involved.

Requests through another legally valid channel remain valid, and only information reasonably needed to verify identity is requested.

We respond without undue delay, normally within one calendar month and subject to applicable deadlines, explaining refusals or lawful extensions and available complaint routes.

A normal response target does not automatically permit an extension, override a shorter legal deadline or end when an account is suspended or terminated.

Changes to this policy

We aim to give seven calendar days’ email notice of material policy changes, subject to necessary security, abuse, legal and urgent-operational exceptions and mandatory legal requirements.

A notice update or acceptance of Terms is not blanket consent to new processing, and separately required consent remains distinct.

Appearance preference

This display preference uses no cookie, is not transmitted to a server and is cleared by choosing System or clearing site data.

This functional, local-only appearance preference is used only to remember appearance.