Skip to content
All policies

Legal document

Security & Compliance

Plain-language explanation of how NovakOS protects customer data, plus how to report a security issue and reach support.

Version 3.0Effective October 13, 2026Acceptance required

This page describes NovakOS controls. It is not a certification or independent audit.

Security and Compliance

Version 3.0 | Effective October 12, 2026

Overview

NovakOS is operated by Michael Novak, carrying on business as NovakOS in British Columbia, Canada. This document describes our security approach, responsibilities and reporting process. Send security reports and all support, privacy, billing and legal questions to support@novakos.org.

1 Scope and assurance

NovakOS uses layered application and infrastructure safeguards to reduce unauthorized access, financial errors and data loss. Controls need correct deployment, configuration, maintenance and operation. This page is not an independent audit, a SOC 2 report, an ISO certification, a PCI validation or a guarantee that every vulnerability or loss will be prevented. A provider's certification does not automatically certify NovakOS.

The Terms of Service and their processing schedule govern our contractual obligations; the Privacy Policy explains personal-information handling. Neither a disclaimer nor a customer's responsibility to review work removes a security or privacy duty imposed on NovakOS by law.

2 Transport credentials and local information

Production connections are designed to use HTTPS and TLS. Infrastructure services provide their supported storage safeguards, and sensitive supported integration credentials are additionally encrypted with a separate application key. Secrets must remain in appropriately protected server or platform storage rather than client bundles, logs or exported documents.

Supported native offline outbox and record payloads use protected device keys and encryption. Some routing fields and other local metadata have different protections; browser storage is not equivalent to native protected storage. Sign-out invokes supported user-scoped cleanup. It does not remotely erase a disconnected device or remove files a user downloaded or copied elsewhere. A device lock, prompt synchronization, sensible sharing practices and appropriate offboarding remain necessary.

3 Company isolation and permissions

The application uses company-scoped database policies, server authorization and private-file access controls to restrict workspace information. Roles and specific permissions limit access to functions such as payroll, payments, refunds, card metadata, location and exports. Privileged server credentials require separate controls and must not be exposed to ordinary users.

NovakOS uses supported session, multi-factor, request and privileged-action controls where applicable. Their presence is not a claim that every account has the same security configuration. Owners must grant the least access needed, remove departed users, protect authentication recovery and promptly report suspected compromise. We must maintain protections for our own administrative access.

4 Payment controls

The supported card-entry flow uses Stripe components and processor tokenization. It does not intentionally store raw card numbers or card security codes in NovakOS payment records. Users are prohibited from putting those credentials in other fields, photographs or uploads.

Standalone staff-initiated charges require the current customer's signed authorization under the supported payment flow. Recurring membership charges depend on the separately recorded recurring agreement. Saved-card details available to users are restricted to the supported safe metadata. Payment, refund and payout status must be reconciled against the processor's confirmed events.

Using Stripe reduces some card-data exposure but does not remove every PCI, card-network, fraud or account requirement applicable to NovakOS or a connected business. This document does not assert that an unverified PCI assessment has been completed.

5 Integration security and permitted processing

QuickBooks and supported mailbox connections use their provider authorization flows and stored grant or token information. Integration access should be limited to the authorized visible functionality. NovakOS does not request an Intuit password. The supported QuickBooks design uses encrypted credentials, time-limited connection state, company-specific processing controls, verified webhook handling and separate queued accounting work.

Disconnection stops future integration activity locally and initiates provider revocation. A transient provider failure may leave only the minimum encrypted credential needed for revocation cleanup until that cleanup succeeds. It must not authorize resumed business-data access. Users may also revoke access in the provider's own controls and contact support about an incomplete revocation.

Restricted Google API and QuickBooks data must remain within the disclosed purpose and onward-transfer limits. An AI receipt scan is optional processing through Lovable and OpenAI, described in the Privacy Policy. A no-response-storage setting does not prove zero provider retention or contractual compliance. Provider and data-protection requirements must be verified for the enabled service.

Before a provider acting on NovakOS's behalf receives Intuit-derived information, NovakOS must verify an applicable written agreement with security and data-protection terms at least as restrictive as Intuit's applicable requirements and must enforce it. A public privacy notice, generic provider terms or a no-response-storage setting does not verify that a particular transfer route is approved. Restricted QuickBooks data must not enter an AI-processing route without permitted purpose, authority and these safeguards. Revocation and QuickBooks-specific deletion are not postponed merely by the ordinary company-recovery window; implementation must satisfy the stricter provider and lawful recordkeeping requirements.

6 Audit and operational evidence

Relevant sensitive and administrative workflows record supported evidence, including specified access, export, policy, permission, payment and integration events. An audit record of authorization does not prove that an operation completed successfully; status and completion evidence must be checked where material.

Support access must be necessary, authorized and appropriately recorded. We do not claim that every database read or direct infrastructure action appears in a customer-facing log. Customer-requested diagnostics should avoid unnecessary personal information. Do not send passwords, security codes or live customer records in an ordinary security report.

7 Backups recovery and deletion

Recovery depends on the infrastructure service and configured backup or recovery capabilities. This page does not promise point-in-time recovery, a successful restore test, a particular recovery time or zero data loss without the relevant verified service arrangement. Customer should maintain independent exports and statutory records needed for continuity.

Company deletion ordinarily disables access and provides a 30-day recovery window before purge is scheduled. Purge can depend on file cleanup, database dependencies, integration revocation and external-provider cooperation. Recovery is different from a disaster-recovery backup. Some restricted legal evidence or required records can remain, and backup copies can expire later under their schedule. The Privacy Policy gives the relevant qualifications.

We must preserve information subject to a valid legal duty or hold and apply appropriate deletion and suppression instructions after restoration. We do not claim that every physical copy is irretrievable on the 30th day or that we are Customer's permanent tax or payroll archive.

8 Security incidents and notifications

We will reasonably investigate suspected incidents, contain harm, preserve necessary evidence, remediate weaknesses and document the affected data, timeline, decisions and notifications. We will inform an affected business without undue delay when we become aware of a confirmed breach of its personal information under our responsibility and provide available updates. That notice does not wait for a final forensic report.

Notification to regulators and affected individuals follows applicable law. Where PIPEDA applies, a breach creating a real risk of significant harm requires the relevant regulator and individual notices as soon as feasible, and records of every breach of safeguards must be kept for at least 24 months. Other jurisdictions and contracts can impose different rules.

Our Intuit obligations are separate: a Security Incident covered by the applicable Intuit Developer Terms must be reported to Intuit without undue delay and no later than 24 hours after discovery, with available required details and follow-up. We must not wait for a significant-harm threshold before that provider notice. Required provider coordination and remediation do not remove independent legal notification duties or permit unlawful delay.

9 Reporting vulnerabilities

Email support@novakos.org with the affected feature or URL, a concise description, safe reproduction steps, approximate time and your contact information. Use synthetic data or an account you control. If evidence contains sensitive information, first ask for an appropriate transfer method and provide only what is necessary.

Do not access another business's data, extract personal information, run destructive tests, denial-of-service, spam, social engineering or tests against provider systems. Stop if unexpected third-party information becomes visible, preserve only minimal non-sensitive evidence and report it. Possessing an account is not unrestricted permission to scan production.

This page does not establish a bounty or waive a third party's rights. Seek written authorization before testing outside ordinary permitted use. We aim to acknowledge and assess useful reports, but do not promise a response or fix within a specific time without a separate agreement. Reporters may make disclosures required by law; any coordinated disclosure should consider the risk to affected people.

10 Compliance responsibilities and support

NovakOS must comply with the privacy, security, provider and other requirements that apply to its own role. Customers must lawfully configure their employee monitoring, messaging, payments and business records. A public policy cannot replace a provider review, signed processing instrument, appropriate deployment, internal incident procedure or legally required impact assessment.

For available information relevant to a security assessment, a restricted processing requirement, an incident or an account problem, contact support@novakos.org. Include the company name, relevant error code and what occurred. Never include account passwords, one-time codes or full card details.

NovakOS public legal documents | pected versus what happened.