Skip to content
All policies

Legal document

Privacy Policy

What personal information NovakOS handles, why, how long it is kept, who it is shared with, and the choices people have.

Version 5.1Effective October 13, 2026Acceptance required

Privacy Policy

Version 5.1 | Effective October 12, 2026

Overview

Michael Novak, carrying on business as NovakOS in British Columbia, Canada, provides field-service business software. This Policy explains the personal information handled through our website, applications and connected features, why it is handled, the recipients, retention and available choices. Our Privacy Officer is the owner and operator of NovakOS. Contact the Privacy Officer, or send any support, billing, security or legal question, at support@novakos.org.

1 Our role and the subscribing business

For its own account administration, subscription billing, support, necessary security and legal records, NovakOS is responsible for its handling of personal information. A subscribing business normally determines the purposes for information about its customers, workers and suppliers and instructs NovakOS to process that information for the enabled service. Our customer-processing obligations are set out in Schedule A of the Terms of Service.

A business using NovakOS must give appropriate notices and have lawful authority for its records and instructions. NovakOS remains responsible for its own obligations and the providers it uses on its behalf. We are an independent application provider; we do not process QuickBooks information on Intuit's behalf. Intuit, Stripe, mailbox operators, identity providers and other independently operated services may have their own responsibilities and privacy notices for their processing.

2 Information we handle and its sources

We receive information from account holders and people using the Services; businesses and their authorized workers; documents, devices and actions submitted through enabled features; and services that an authorized user connects. Not every category is used for every account.

Account and business details: names, work contact details, company identity, ownership and role information, profile image, preferences, authentication identifiers and subscription information.

Customer and supplier records: names, addresses, contact details, properties, equipment, service history, jobs, estimates, invoices, expenses, inventory and related notes, forms, media, documents and signatures.

Workforce records: employee identifiers, assignments, time and leave records, pay rates, commission or piecework configuration, payroll summaries, reward and performance metrics and enabled work-location information.

Payments: transaction, refund, payout, dispute and reconciliation data; processor identifiers and tokens; card brand, last digits and expiry where supported; and authorization, consent and signature evidence. Approved payment entry sends raw card details to Stripe. NovakOS's payment workflow is not designed to store full card numbers or security codes. Users must not put them in other fields or uploads.

Communications: sender and recipient details, selected message content and attachments, delivery events, tracking events where enabled, complaints, consents, opt-outs, mailbox identity, grant identifiers and enabled integration metadata.

QuickBooks integration data: authorized company and connection identifiers, account and tax references, customer or vendor details, enabled invoices, payments, refunds or credits, payout and fee records, expenses, bills, products or services, selected attachments and sync or reconciliation records.

Device and technical information: IP address, browser or operating system, app version, device or notification identifiers, timestamps, session and authentication events, diagnostics, security events and audit records. Contract and policy actions can record the exact version, statement, user, company and time, with associated technical evidence.

Optional AI extraction: the image or PDF submitted for receipt reading, file metadata, supplied job-matching context and returned extracted fields. Job context may contain customer names, addresses or other identifying details.

Please minimize unrelated sensitive information. The ordinary upload and notes features are not an authorization to submit passwords, raw card credentials, unnecessary government identifiers, biometric identifiers or medical records.

3 Why we handle information

We handle information to create and administer accounts; deliver the features selected by the business; synchronize authorized records; process our billing and enabled payments; send requested or authorized communications; provide support; protect accounts and investigate abuse; keep necessary consent and legal evidence; and meet applicable obligations. We may use limited operational metrics to maintain reliability and capacity where law and provider rules permit it.

We do not sell personal information or use Customer Data for unrelated advertising. NovakOS does not use identifiable Customer Data to train a general-purpose AI model. Google API data and QuickBooks-derived data remain subject to their particular restrictions, including where derived or aggregated information is covered. A general service-improvement purpose does not override those restrictions.

4 Authority consent and optional features

We rely on consent or another authority available under the applicable law for the particular processing. Customer-directed processing follows the business's lawful instructions. Some employment processing may lawfully use notice and a reasonable employment purpose rather than employee consent; the business must determine the rule that applies. An in-app acknowledgement documents that a notice was presented and is not a substitute for consent when consent is required.

Users can decline optional integrations or AI scans and manage relevant device permissions. Withdrawing optional permission may make the related feature unavailable. Withdrawal does not invalidate completed lawful activity or require destruction of records that must lawfully be retained. We will not treat acceptance of this Policy as blanket consent for marketing, off-duty tracking, an unrelated transfer or a materially new purpose.

5 Work location

Where enabled, location functions can process device coordinates, accuracy and timestamps for dispatch and legitimate work records. Periodic background tracking is controlled by the company policy, acknowledged notices, active work or clock state, device permissions and operating-system restrictions. Separate event snapshots can record location at an authorized work action, including a clock-in or clock-out. An operating-system background permission does not authorize unrestricted off-duty use.

Businesses must explain the types of location collected, the work purposes, collection periods, relevant recipients, retention and contact for questions before collection begins, and obtain any required authorization. Company permissions restrict access to location functions. Businesses must not use them for covert surveillance, stalking or unrelated sensitive inferences. Users can check the app's available tracking controls and revoke device permissions; doing so can affect dispatch and work-location features.

Ordinary location-history points and work-event location records are scheduled for purge under the supported short retention setting, currently up to approximately 28 days. Exported evidence and service-site addresses in ordinary business records are distinct from that operational history and can have separate lawful retention purposes. Lawful evidence preservation or an active hold can require longer retention of particular records. Company access to location history is subject to the relevant permissions and audit controls. These functions do not guarantee a person's real-time position or provide emergency monitoring.

6 QuickBooks access use and disconnection

The authorized user chooses the QuickBooks company and grants the accounting permission presented by Intuit. We use that authorization for the visible accounting features enabled by the business. We exchange and retain the categories described above to map records, support approved or configured exports, display permitted imported records and status, and reconcile discrepancies. NovakOS does not receive the user's Intuit login password.

Data is sent to the connected QuickBooks company, and may be processed by the infrastructure and support providers needed to operate the authorized feature under appropriate restrictions. We do not sell QuickBooks data, use it for unrelated profiling or advertising, or disclose it for a recipient's independent business purposes. An attachment is shared only through the relevant authorized workflow. The business should review mapping, review mode and automatic-sync settings before use.

Use the QuickBooks connection settings to disconnect, or revoke permission through Intuit's connected-app controls. Disconnection stops future accounting access and sync. An encrypted minimum credential may remain temporarily to complete revocation, without authority to resume accounting requests. Previous records already sent to Intuit remain subject to Intuit's controls; an ordinary NovakOS business record is not erased merely because its accounting connection ends.

Request access, correction or deletion of information we hold, including imported integration information, at support@novakos.org. We distinguish information needed for lawful bookkeeping, consent or security evidence from unnecessary copies or caches, and apply applicable purpose and deletion restrictions. We do not continue unrelated use of disconnected integration data. Intuit describes its own handling at https://www.intuit.com/privacy/statement/.

For information obtained solely through a QuickBooks authorization, revocation or disconnection immediately stops new Intuit access and processing for the withdrawn purpose, subject to narrowly necessary revocation cleanup and legal recordkeeping. An authorized request to securely delete that information is assessed and fulfilled under applicable Intuit requirements rather than automatically waiting through the ordinary 30-day company-recovery window. If law requires retention of a particular record, use and access are restricted to that legal purpose until deletion is permitted. An independently created NovakOS business record is distinguished from an imported Intuit copy, and Intuit controls records retained in its own service. Contact support@novakos.org for a QuickBooks-data request even when the NovakOS workspace remains active.

7 Connected business mailboxes and Google API data

An authorized business can connect a supported mailbox through Nylas. The Google connection requests account identity and Gmail sending permissions, rather than general inbox-reading or modification permissions. NovakOS uses the mailbox identity, authorization and selected outgoing message data to send business communications requested through the app and retain necessary delivery and consent records. Our current Microsoft connection can request identity, offline access, mail read/write and mail sending permissions because of the provider's sending requirements. That broader permission screen does not mean NovakOS indiscriminately reads the inbox.

Nylas and the mailbox operator may process authorization information and communications under the enabled connection and their applicable terms. Other supported providers can include Apple iCloud, Yahoo and authorized IMAP or SMTP operators. Review the actual permission screen and avoid attaching information unrelated to the intended communication.

NovakOS follows the Google API Services User Data Policy, including its Limited Use requirements, for information received from Google APIs. That information is used for the prominent user-facing features authorized by the user. Permitted transfers are limited to operating those features with the necessary consent, necessary security purposes, legal compliance, or a qualifying business transfer with the required prior consent. Human access is limited to specifically authorized assistance, necessary security or legal purposes, or other access expressly permitted by that policy. We do not use it for advertising, data brokerage, creditworthiness decisions or general-purpose model training, and do not expand rights by deriving or aggregating the data.

The policy is available at https://developers.google.com/terms/api-services-user-data-policy. These restrictions apply to our personnel and relevant onward processing. They take priority over broader operational, analytics or business-transfer wording elsewhere in our documents.

Disconnect a mailbox through the connection controls and, where appropriate, revoke the app's permission with the mailbox operator. Future sending through that grant stops. Sent messages, lawful business communication records and provider-retained copies are not automatically recalled or erased. Contact support@novakos.org for help with our retained integration information or a failed disconnection.

8 Receipt reading and generative AI

Receipt reading is an optional user-initiated feature. It sends the selected image or PDF and any supplied job-matching context through Lovable's AI gateway to an OpenAI model and returns suggested expense fields for human review. It does not automatically access a connected mailbox or call QuickBooks to collect documents for scanning. Ordinary manual expense entry is an alternative.

The whole submitted document can contain more information than the extracted fields. Redact unrelated personal information and do not submit raw card credentials, prohibited sensitive data or restricted integration information for which that AI transfer is not permitted. Review the file and disclosed context before initiating the scan. Offline scans queued by the user may be transmitted when connectivity returns; remove a pending scan if you no longer want it processed.

A user-initiated receipt scan does not automatically retrieve QuickBooks information. A document or job context obtained through QuickBooks or another restricted integration must not be sent to Lovable, OpenAI or another AI provider unless the particular transfer is both permitted by the source provider's rules and lawfully authorized, and any required written onward-processing safeguards have been verified. Accepting the AI-scan notice does not override those restrictions. NovakOS will not enable a new restricted-integration-to-AI flow without the necessary data-use permissions, transparent disclosure and provider agreements.

NovakOS requests that generated responses not be stored by the response service. This is not a promise of zero gateway or provider retention: security, abuse and operational handling depends on the applicable service contracts and configurations, and processing can occur outside Canada. We do not represent that every provider account has a special zero-retention arrangement. Our own no-training commitment does not change a third party's independent contract. Applicable provider terms and data safeguards must be satisfied before a business submits information it is not authorized to transfer.

Lovable's information is at https://lovable.dev/privacy and https://lovable.dev/terms; OpenAI's is at https://openai.com/policies/privacy-policy/. Contact support for available details relevant to a particular processing restriction. AI output can be inaccurate and must be checked against the original before financial use. The feature does not autonomously make an employment, credit or other legally significant decision.

9 Service providers and other recipients

Only providers relevant to the enabled features receive the information needed for their function. Provider roles can differ: infrastructure may process on our behalf, while a business's connected financial or mailbox account may be operated independently under its own agreement. We require applicable safeguards for processing on our behalf and remain responsible for our duties; listing a provider does not itself prove that every account configuration or contractual requirement is satisfied.

Lovable and its applicable cloud or connector infrastructure: application operation and connector routing. Requests for enabled email, mapping or AI services can pass through Lovable as well as the destination provider. Relevant data includes request content, authentication or integration metadata and necessary operational details.

Supabase and its infrastructure: database, authentication and file storage for application records and authorized uploads. Project-region and service operations can involve processing outside Canada.

Cloudflare: application delivery and security infrastructure, including network, request and edge metadata. Processing can use global infrastructure.

Stripe: NovakOS billing and enabled Connected Account payments, verification, fraud handling, payment methods and transaction reporting. Stripe also has independent financial and legal duties.

Resend: outbound email content, recipients, attachments and delivery or suppression events through supported platform sending.

Twilio and applicable carriers: phone numbers, inbound and outbound messaging content and attachments, delivery events, registration and opt-out records.

Nylas and the authorized mailbox operator: mailbox identity, grants, selected outgoing message content and attachments, sending and connection status. Nylas regions depend on the configured service; the mailbox operator controls its own storage.

Google Maps Platform: address searches, geocoding, coordinates, map use and associated technical information. Google processes information under its mapping terms and privacy policy.

Intuit and QuickBooks Online: authorized accounting data and attachments exchanged with the selected company, as described above.

Lovable's AI gateway and OpenAI: selected receipt/PDF content, supplied job context and extracted output for user-requested receipt reading.

Apple and Google push and distribution services: notification routing tokens, platform identifiers and notification payloads where enabled, and independent app distribution or sign-in data. Google Firebase Cloud Messaging and Apple Push Notification service support the relevant push delivery.

A payroll or other business provider chosen by the business: the data the business elects to export or transmit through an available supported function. Downloading a Payworks-format file does not automatically send it to Payworks; the business controls its separate upload.

We may also disclose necessary information to the business and its authorized users, intended message recipients, professional advisers subject to appropriate confidentiality, or authorities where law requires or permits a justified disclosure. Business transfers require the applicable safeguards and notices; restricted Google API or other provider data requires any additional consent before transfer. We do not share SMS consent information with unrelated recipients for their marketing.

We will keep material provider disclosures current and give reasonable advance notice of a material new processing provider through the relevant app notice or this Policy. Ask at support@novakos.org for available information or advance email notices. Where law or provider rules require fresh consent, a published notice alone is insufficient.

10 Data location and transfers

NovakOS is operated from British Columbia. Cloud, communications, accounting, AI and support processing may take place outside the user's province or Canada, including the United States, European locations and other locations in a provider's infrastructure. We do not promise that all application data, backups or provider operations remain in Canada. Actual project and integration regions depend on their configured service.

Information handled in another jurisdiction may be accessible to that jurisdiction's courts, regulators or lawful authorities. We use applicable contractual, access and security safeguards for processing on our behalf. A business with localization or transfer restrictions should obtain available details before enabling the feature. Required privacy impact assessments and transfer agreements, including those that may apply to Quebec information, must be completed by the responsible party; an acknowledgement of this Policy does not replace them.

11 Cookies browser storage and local device data

The application uses authentication storage, local or session storage, IndexedDB and supported native device storage for sign-in, offline records and queued work, preferences and notice acknowledgements. Our application does not intentionally use advertising cookies or cross-site advertising profiles. A third-party embedded or connected service may receive technical information needed to operate under its own disclosed practices; this statement is not a promise that those services use no storage or telemetry.

Local offline work can contain personal information. Supported native offline records and outbox payloads use encryption, while routing metadata and some device or browser storage have different protections. Browser storage is not equivalent to native protected storage. Use device locks and appropriate shared-device precautions. Sign-out invokes cleanup of supported user-scoped local information, but cannot guarantee deletion of separately downloaded files, external copies, device backups or a device that is disconnected. Clearing local data can destroy unsynchronized work. Synchronize needed work before clearing it when it is safe to do so.

12 Retention and preservation

We retain information for its disclosed service purpose and the limited legal, consent, security or dispute needs that apply. Data should be removed or appropriately de-identified when those needs end. An active lawful hold or information needed to respond to an affected person's access rights can require preservation beyond a routine schedule. Such information must be limited, restricted and reviewed; a general possibility of a future dispute is not permission to keep every record indefinitely.

The ordinary schedules and relevant qualifications are:

Location-history points and work-event location records: the supported short operational window, currently up to approximately 28 days, followed by scheduled purge; particular lawful holds and information lawfully exported for evidence can be exceptions.

Company deletion: a usual 30-day recovery window before active-system purge is scheduled. Cleanup can require retries and provider cooperation; a deadline for scheduling is not proof that every copy has been erased.

Application email delivery logs, sent-message records and SMS records: retained for the business's enabled communication and recordkeeping needs and limited delivery, consent, security or legal purposes. They are subject to available deletion and company-purge processes. Provider copies and minimal suppression evidence can have different retention requirements.

Audit and sensitive-access records: retained for necessary accountability, security, investigation and legal evidence, with continuing need reviewed and deletion or limitation when that need ends. The presence of an audit record does not establish an indefinite right to keep its personal information.

Security and privacy incident evidence: at least the statutory minimum applicable to a breach, with longer restricted retention where justified for investigation, obligations or claims. Where PIPEDA applies, records of every breach of safeguards must be kept for at least 24 months.

QuickBooks OAuth, webhook, error and completed-revocation operational records: kept for the limited authorization, troubleshooting or security purpose and removed under the applicable cleanup schedule. Accounting records and mappings have distinct bookkeeping and integration purposes; request review or deletion of unnecessary imported copies through support. Secure-deletion duties for Intuit-sourced information are considered separately from the usual 30-day company-recovery period and are subject to applicable lawful recordkeeping exceptions.

Active business records and payroll information: kept while needed for the enabled business service, subject to the business's instructions, legal obligations and applicable deletion processes. Separate deletion and anonymization tools have limits where lawful records must be preserved.

NovakOS's own subscription, fee, tax and legal evidence: kept for applicable bookkeeping, dispute and regulatory periods. Customer's financial or employment recordkeeping obligation is not a promise that NovakOS retains its entire workspace after company deletion.

Consent and suppression records: a minimal record may be kept after an account or message is deleted to prove authorization or continue honouring an opt-out. It is not used to send new marketing.

Disaster-recovery backups: deleted records can remain until the applicable backup expires or rotates. Backups are restricted to recovery; relevant deletion and suppression instructions must be reapplied following a restore. Provider copies follow the lawful limits applicable to those providers.

Canadian tax records are generally required for six years from the end of the relevant tax year, with exceptions and sometimes longer requirements. Employment and decision records have their own rules. Customer must keep the required records independently before deleting them or closing its company. We do not represent a fixed seven-year clock from a transaction as the universal legal rule.

13 Deleting a company a user or a customer record

Verified company deletion is controlled by the owner or an appropriately verified successor. It disables workspace access and starts the ordinary recovery process. Request recovery promptly within the available window at support@novakos.org. Once a permanent purge has completed, it is not an ordinary recoverable deletion.

A person can request closure or deletion of their own sign-in, leave a workspace, or seek access to their personal information. Those actions do not authorize deletion of the business or its legally required records. Owner-account deletion may require transfer of ownership or coordinated company closure. We may verify identity and authority proportionately and escalate requests that cannot safely be completed automatically.

Deleting a customer record may be restricted where an invoice, payment or required business record depends on it. Appropriate correction, redaction or masking may be available, but masking is not a promise that every historical document has become anonymous. Account cancellation and deletion also do not automatically erase processor, recipient, mailbox or accounting-provider copies. We will identify applicable exceptions and assist with records within our control.

14 Access correction withdrawal portability and complaints

You may ask for access to personal information under our control and how it is used or disclosed, request correction or annotation, withdraw consent where applicable, and request deletion or a usable copy where the law provides that right. Depending on your jurisdiction, you may also have rights relating to sensitive information, profiling, automated decisions or portability.

For the business's customer or worker records, begin with that business if appropriate; it normally controls the purposes and the response. You may also contact support@novakos.org and we will explain our role, forward a request where appropriate and fulfil our own obligations. Loss of app access does not prevent a request.

We may request proportionate identity verification and details needed to locate the information, protect others' records or determine lawful exceptions. We respond within the time required by applicable law, commonly 30 days under BC PIPA or PIPEDA, with any lawful extension and required explanation. Where access or deletion is lawfully limited, we will explain the basis where permitted and provide available complaint or review routes.

In-product company or personal exports are useful tools but may require supplementation for a complete legal response. We do not require a paid subscription to exercise a mandatory individual right or charge an unlawful access fee. Contact the Privacy Officer if a tool does not provide what the request requires.

If a complaint is not resolved, you can contact the privacy regulator with jurisdiction, such as the Office of the Information and Privacy Commissioner for British Columbia, the Office of the Privacy Commissioner of Canada, or another applicable provincial regulator. A service agreement does not waive the right to complain.

15 Communications choices

Marketing email can be stopped through the applicable unsubscribe link or by contacting the sender or support. Text recipients can use STOP or another supported opt-out method. We and the sending business must honour valid withdrawals and provider suppression; a notice receipt does not authorize bypassing them. Use another permitted channel for necessary communications if the SMS channel is suppressed.

Necessary account, security or requested service communications may continue through an appropriate lawful channel, subject to applicable law and provider rules. We do not assume every job-related message is exempt from consent or identification requirements. Businesses must act on requests received outside the automated controls as well.

16 Safeguards and incident notices

We maintain reasonable safeguards appropriate to the data and risks, including supported authentication and authorization, company isolation controls, protected transport, encryption of supported integration secrets, limited access and relevant audit and response processes. The Security and Compliance page describes the approach. It is not a statement of an independent certification, zero vulnerabilities or zero data loss.

When a breach affects personal information under our responsibility, we investigate, document and meet the notification duties that apply. A subscribing business is informed without undue delay of a confirmed Customer-data breach so it can assess its own obligations. Regulatory and individual notices are made as required by law; applicable provider notices, including Intuit security-incident notices, may have different or earlier thresholds and deadlines. We do not wait for a significant-harm conclusion before meeting an independent provider notice duty.

17 Young users and changes

NovakOS is business software and is not directed to children. A business giving a younger worker access must have lawful authority and appropriate protections. We do not authorize use of children's information for unrelated profiling or marketing. Contact support if children's information has been submitted inappropriately.

We will publish material updates with their version and effective date and provide additional notice or consent where required. New permissions or materially different personal-information purposes require the applicable lawful process before use. Merely updating this page does not retroactively authorize an undisclosed purpose or alter an earlier consent.

18 Contact

Privacy Officer and all NovakOS support, billing, security and legal questions: support@novakos.org.

NovakOS public legal documents |