Where this policy applies
This Privacy Policy applies to Fire Logbook interactions with Niktasoft, including the Fire Logbook application, public web pages, signup and login pages, support pages, QR/direct-mail landing pages, access-request forms, and customer support. It does not apply to unrelated Niktasoft websites or services unless they link to this policy.
What Fire Logbook may store or receive
Account and profile details
Email address, Supabase user identifier, name, job title, phone number, and owner/member role where provided.
Organization details
Organization name, address, city, province, postal code, phone, logo, settings, and inspection start month.
Inspection and recordkeeping data
Locations, monthly records, fire drills, optional module records, pass/fail results, notes, timestamps, and deficiencies.
Customer-uploaded content
Failure photos and Fire Safety Plan documents or metadata if your organization uses those features.
Support and diagnostic information
Support request details, support references, browser diagnostics you choose to send, and sanitized warning/error telemetry.
Landing-page access requests
Email address, optional product-update choice, and limited QR or campaign attribution such as src, campaign, code, utm_source, and utm_campaign values.
Purposes for collection and use
- Authenticate users, protect account access, and provision organization workspaces.
- Provide Fire Logbook, store organization records, manage deficiencies, and generate PDF recordkeeping reports from user-entered data.
- Respond to signup, access-request, support, and account questions.
- Operate, secure, troubleshoot, and improve the service using privacy-safe diagnostics and incident information.
- Understand the source and effectiveness of QR/direct-mail access requests, including values such as src, campaign, code, utm_source, and utm_campaign, without treating campaign values as personal profiles.
- Send optional product updates where Niktasoft has the consent required by applicable law.
Records, photos, notes, and documents
Inspection records, notes, photographs, documents, and organization information are customer-provided content. Customers control what they enter or upload. Notes and photos can contain personal information if a user chooses to include it, so users should avoid unnecessary personal details and should not use Fire Logbook as a student information system.
Who helps operate Fire Logbook
Supabase
Authentication, database, protected file storage, and Edge Functions used by the Fire Logbook application.
Cloudflare
Static hosting, CDN delivery, security headers, and caching for the public and authenticated frontend.
Resend
Support and service email delivery when the support Edge Function is configured to send email.
Sentry
Optional privacy-safe browser warning/error telemetry when telemetry is configured. The app sanitizes events before sending.
Formspree
Form processing for the separate QR/direct-mail access-request landing page only. It is not the application backend and does not process inspection records.
Provider locations may vary
Niktasoft is based in Ontario, Canada. Fire Logbook uses third-party providers that may process, store, or access information outside Canada depending on their systems, support processes, and service regions. Information handled outside Canada may be subject to the laws of those locations.
How long information is kept
- Organization records are retained while needed to provide Fire Logbook, support customer use, meet legal or operational needs, and preserve records the organization chooses to keep in the app.
- Support, security, diagnostic, and campaign-attribution records are retained only as long as needed for support, reliability, security, legal, or operational purposes.
- Your organization remains responsible for retaining any fire-safety records it is required to keep outside Fire Logbook.
Safeguards and shared responsibility
Organization-scoped storage
Fire Logbook uses application and database access controls so authorized users access records for their own organization.
Private files and signed access
Private photos and documents are stored in Supabase Storage and accessed through controlled application flows.
No absolute guarantee
No system can guarantee absolute security. Users must keep credentials secure and report suspected account misuse promptly.
Keeping information current
Users can update many organization and profile details inside Fire Logbook. To request access, correction, or assistance with information that cannot be updated in the app, contact Niktasoft at admin@niktasoft.ca.
Product updates are optional
The QR/direct-mail access-request landing page may include an optional product-update checkbox. Choosing product updates is separate from requesting access to Fire Logbook and is not required merely to request access. You can withdraw marketing consent by contacting admin@niktasoft.ca or using any unsubscribe option included in a message.
Questions, requests, and complaints
Niktasoft has designated a Privacy Contact for questions and requests concerning Fire Logbook's handling of personal information. Use admin@niktasoft.ca for privacy questions, access requests, correction requests, concerns or complaints, QR landing-page submission questions, and withdrawal of consent where applicable.
If you are not satisfied with Niktasoft's response and have the right to do so under applicable law, you may contact the appropriate Canadian privacy regulator, including the Office of the Privacy Commissioner of Canada.
Updates to this policy
Niktasoft may update this policy from time to time. The updated version will be posted in Fire Logbook and will show the current Last Updated date.
August 10, 2026
Questions about privacy or data handling? Email admin@niktasoft.ca.