← Back to NiktaFire
Privacy Policy
Terms →
NiktaFire only Last updated September 22, 2026

Privacy Policy

This policy explains how Niktasoft handles information for NiktaFire, including the app, related web pages, support, and QR/direct-mail access-request landing pages.

1. Scope

Where this policy applies

This Privacy Policy applies to NiktaFire interactions with Niktasoft, including the NiktaFire 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 products unless they link to this policy.

2. Information we collect

What NiktaFire 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
School or organization name, contact name, work email address, optional product-update choice, primary-user details, and limited campaign attribution submitted with the request.
Consent-based landing-page analytics
Campaign and UTM values, referring domain, landing-page path, and interactions such as demo, sample-report, pilot-button, and successful form-stage events. Names, school names, email addresses, and form contents are not sent to analytics.
3. How we use information

Purposes for collection and use

  • ✓Authenticate users, protect account access, and provision organization workspaces.
  • ✓Provide NiktaFire, 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.
4. Customer content

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 NiktaFire as a student information system.

5. Service providers

Who helps operate NiktaFire

Supabase
Authentication, database, protected file storage, and Edge Functions used by the NiktaFire 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.
Google Analytics
Optional landing-page campaign and interaction measurement. Google Analytics loads only after the visitor grants analytics consent, and advertising signals and personalization are disabled. The choice is saved in the browser and can be changed from the landing-page footer. Counts exclude visitors who decline, block analytics, or use privacy tools, so they are not an exact count of everyone who opened the page.
6. Processing outside Canada

Provider locations may vary

Niktasoft is based in Ontario, Canada. NiktaFire 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.

7. Retention

How long information is kept

  • ✓Organization records are retained while needed to provide NiktaFire, 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.
  • ✓Backup copies and deleted-account data may remain for a limited period as part of normal backup, security, and recovery processes before being removed or overwritten.
  • ✓Your organization remains responsible for retaining any fire-safety records it is required to keep outside NiktaFire.
8. Security

Safeguards and shared responsibility

Organization-scoped storage
NiktaFire 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.
9. Access and correction

Keeping information current

Users can update many organization and profile details inside NiktaFire. To request access, correction, or assistance with information that cannot be updated in the app, contact Niktasoft at admin@niktasoft.ca.

10. Marketing choices

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 NiktaFire 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.

11. Privacy Contact

Questions, requests, and complaints

Niktasoft has designated a Privacy Contact for questions and requests concerning NiktaFire'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.

12. Changes

Updates to this policy

Niktasoft may update this policy from time to time. The updated version will be posted in NiktaFire and will show the current Last Updated date.

13. Last updated

September 22, 2026

Questions about privacy or data handling? Email admin@niktasoft.ca

Open Support
← Back to NiktaFire