Privacy policy
This policy describes how Shawn Kennedy, operating as Bicc Software in Ontario, Canada ("Bicc", "we"), handles personal information for the website, software licensing, purchases, support and hosted report/agreement features. For privacy questions or requests, contact biccsoftware@gmail.com, attention: Privacy.
Information used to provide Bicc
- Purchases: checkout contact and billing information, order and payment references, amounts, tax, refund information and checkout terms acceptance. Stripe processes payment-card information on its checkout; our purchase service receives payment results and order details, not your full card number or security code.
- Licensing: licence key and identifiers, edition, activation status, a hashed device identifier, computer name/platform, activation dates and network information processed by the licensing provider. This supports activation, device limits, replacement computers, trial eligibility and refund cancellation.
- Support: your email address, correspondence and any files or diagnostics you choose to provide. Send only information needed to resolve your request; avoid sending full inspection records where an example with personal details removed will suffice.
- Testimonials: when you submit a testimonial, we store your name, optional company, review text, publication permission and submission date in Cloudflare. Reviews remain private until approved. Approved reviews display your submitted name, company and text publicly. We use Cloudflare Turnstile and temporary abuse-prevention counters to protect the form. Contact us to request removal. Please do not include inspection client information in a testimonial.
- Website and service access: IP address, browser/device details, request times and security or error information handled by hosting, download and service providers.
Local inspection data and online features
Your working profile, bookings, inspection reports, photos and backups normally remain on your computer unless you export, share or use an online feature. We do not automatically back up or synchronize your full local data folder.
When you publish a report or send an agreement through Bicc, relevant information is uploaded to our hosted services. This can include inspector/company contact details, client names and emails, property addresses, agreement text, report PDFs and associated delivery records. Report PDFs may contain photographs and other information you included.
Online agreement acceptance records include the typed name, agreement version/content reference, consent, acceptance time, IP address and browser information. Email delivery records can include recipient, message identifiers, send/delivery status, bounce or complaint details. These records support the inspector's workflow, delivery troubleshooting and dispute handling.
Inspectors are responsible for having authority to provide client information and for explaining their inspection-data practices to clients. If you are an inspection client, contact your inspector about the contents of a report or agreement. You can also contact Bicc about information held by our hosted services.
Purposes and service providers
We use information to fulfil purchases, issue and validate licences, send requested reports and agreements, record acceptance, prevent abuse, troubleshoot delivery, answer support requests, handle refunds and meet applicable recordkeeping obligations.
Providers involved include Stripe (checkout/payments), Keygen (licensing), Cloudflare (website/download infrastructure and verification), Amazon Web Services (hosted processing, storage and email), and Google/Gmail (support email). The website also loads fonts and styling resources from Google Fonts and a Tailwind CDN; visiting it sends ordinary browser/network information to those providers. Their own privacy notices describe their processing.
Our AWS hosted services operate in the United States. Other providers may process information in Canada, the United States or other countries, where it may be accessible under local laws. Information is shared with providers as needed for the functions described, with recipients you direct us to contact, or where required by law.
Cookies and local storage
Bicc stores application settings, local data and agreement-acceptance information on your device. Download verification and payment providers may use cookies or similar technologies for security and checkout. Blocking them may prevent those features from working.
Retention and safeguards
Local files remain under your control until you remove them. Licence, purchase and service records may be retained to support ongoing licences, refunds, audit/dispute needs and legal obligations; these records do not all have an automatic deletion date. Agreement-link expiry does not mean the underlying acceptance record has been deleted. Temporary uploaded report files have a separate cleanup process, while delivery and order metadata can remain longer. Email recipients and your inspector may retain their own copies.
We use encrypted connections, provider access controls and restricted server-side credentials. No system can guarantee absolute security. Protect your licence key, devices, backups and private report/agreement links. Contact us to discuss retention or deletion of a particular record; we will explain any legal or operational reason it must be retained.
Your choices and requests
You can choose whether to use online publishing and email features. Providing the information needed for payment, activation or those services is necessary to use them. Contact us to request access or correction, discuss deletion or withdraw consent where applicable. We may need to verify your identity, and some records must be retained for legal or legitimate ongoing service needs. We will explain any limitations and the effect on service access. You can raise unresolved privacy concerns with the appropriate privacy regulator, including the Office of the Privacy Commissioner of Canada.
Updates
We will update the version/date when these practices change and provide additional notice or obtain consent where required. A new policy does not authorize unrelated new uses of previously collected information without the applicable legal basis.