Legal

Terms of Service

Last updated: September 2026

These terms cover what BlinKode does, what it doesn’t, what stays yours, and where responsibility sits. Two sections matter more than the rest — what BlinKode is not and the limits you should know about. If you read nothing else, read those.

1. Who these terms are with

These Terms of Service are an agreement between you and BlinKode Technologies Inc., a corporation incorporated under the Canada Business Corporations Act and registered in Ontario (“BlinKode”, “we”, “us”). They govern your use of the BlinKode website, CodeEase, Codiag, and any related plugin or service we provide (together, the “Service”).

By creating an account or using the Service, you agree to these terms and to our Privacy Policy. If you’re using BlinKode on behalf of a firm or employer, you confirm you’re authorized to accept these terms for them. You must be at least 18 years old.

2. Where BlinKode is right now

BlinKode is in active development, and we’d rather set expectations honestly than quietly.

• Pricing is not fixed. Plans shown on the pricing page are indicative and may change.
• Trial mode is on. Billing is not switched on. You are not being charged, and no subscription is in force.
• Features are still moving. CodeEase is live; Codiag is coming soon. Any of them may change, and we may add, alter or withdraw functionality as we build.

Before we charge anyone, we will publish updated terms covering subscriptions, renewal, refunds and cancellation, and give you notice. Nothing in these terms commits you to a payment today.

3. Your account

You’re responsible for the accuracy of your account information and for keeping your credentials secure. Tell us promptly at support@blinkode.ca if you believe your account has been accessed without your permission. You’re responsible for activity under your account.

4. Teams, seats, and who owns the work

CodeEase is sold by the seat. Seats in one team share a single usage allowance and a single invoice. The person who creates a team is its admin: they buy seats, invite and remove members, and are responsible for the subscription. The admin role can be handed to another member, and takes effect only when that member accepts it.

Work you create as a member of a team belongs to that team. Projects, notes and drawings you make on a team’s seat stay with the team if you leave, are removed, or close your account: they transfer to the team’s admin. This is the one place where closing your account does not take your work with it, and it applies only to work created under the team. Anything you made on your own account, before joining, remains yours and is not affected.

You keep read-only access to what you made. When your work transfers to the team’s admin, you can still open and read the projects you created. You just can’t change them. The admin can withdraw that access at any time, the same way they would any other share. This does not apply if you close your BlinKode account entirely: there is then no account left to hold the access.

A team’s admin can open any project created under their team, including one you have not shared. That is what makes a firm’s work reachable when the person who made it is on leave or has left.

You can share a project outside your team. Anyone you name receives a guest view: your analysis, your notes, and the provisions you relied on by reference, never the Code text itself, which is licensed to subscribers. If you are a member of a team, this means work owned by the team can be shared beyond it by your action, so share deliberately. A share is revocable at any time and can only be opened by the person you addressed it to.

5. Trials, usage and limits

A free trial is one per person, ever, not one per account or per email address, and runs for 30 days. It carries a usage allowance, and it can be ended early if it is being used to avoid paying for the Service.

Usage is metered. Every AI answer costs us real money, so we record what each account uses and what it costs. Paid plans include a generous monthly allowance and we do not cut you off for a heavy month. We do apply an automatic ceiling far above normal use, which pauses AI features if an account’s usage looks runaway rather than human: a stuck browser tab, or a script. Reading the Code, your projects and your notes are never affected by that pause, and we will always be in touch if it happens.

6. Acceptable use

You agree not to:

• Scrape, bulk-export, resell or redistribute BlinKode’s structured content, or use it to build a competing product;
• Reverse engineer, probe or interfere with the Service, or attempt to access another user’s account or projects;
• Upload content you don’t have the right to use, or anything unlawful or malicious;
• Use the Service in a way that misrepresents its output as an official determination of compliance.

7. Your content stays yours

You keep ownership of everything you bring or create: your drawings, notes, canvases, project briefs and conversations, and the Codiag reports, findings and review packages you generate from them. You grant us only the limited licence we need to host, store, process and display that content back to you in order to operate the Service. That licence ends when you delete the content or close your account, except that closing your account does not erase our closed record of it, which the Privacy Policy describes and which you can ask us to delete.

We do not use your content to train AI models, and we do not share it with anyone else for that purpose. How your content is handled in practice, including the fact that neither assistant is given your drawings, is set out in the Privacy Policy.

8. Our content

The Service, including our Master Card structure, the explanations, diagrams, relationship maps, and the software and design behind them, belongs to BlinKode and is protected by copyright and other rights. You may use it for your professional work. You may not copy, redistribute or republish it as a product or dataset of its own.

Building codes and referenced standards are published by governments and standards bodies, not by BlinKode. We structure and explain that material; we don’t own it, and we’re not its official publisher. The official published text always governs.

9. What BlinKode is not

10. Limits you should know about

We disclose the known limits of the Service rather than bury them, because you can only rely on something sensibly if you know where it stops:

• Coverage. Only the code books and editions listed in the product are covered. Others are not.
• Local amendments. Municipal amendments, zoning and authority-specific requirements are not included, and remain yours to check.
• Referenced standards. We identify which standards a clause depends on; we don’t reproduce standards published by others.
• Reading aids. Explanations, diagrams, decision charts and the answers of Code Assistant and Project Assistant are reading aids and may be incomplete or wrong. They are cited so you can check them, and you should.
• Ambiguous provisions. Where a provision is genuinely open to interpretation, or where applying it depends on project-specific facts, BlinKode shows what the requirement turns on. It does not resolve the ambiguity for you.

11. Service provided “as is”

The Service is provided on an “as is” and “as available” basis. To the fullest extent permitted by law, we disclaim all warranties, express or implied, including any warranty of merchantability, fitness for a particular purpose, and non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or that its content is complete, current or accurate.

12. Limitation of liability

To the fullest extent permitted by law, BlinKode’s total aggregate liability arising out of or relating to the Service will not exceed the greater of (a) the amount you paid us for the Service in the twelve months before the event giving rise to the claim, or (b) CAD $100.

We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost business, loss of data, or business interruption, even if we were advised such damages were possible.

Code accuracy specifically

Because this is the risk that matters most for a product like ours, we state it directly rather than leaving it to the general wording above. We are not liable for any loss arising from reliance on BlinKode’s guidance, including a design decision, permit submission, rejection, delay, rework, deficiency, or construction outcome, where that reliance concerned any of the limits disclosed in section 8, or where the official published code text differs from what the Service showed.

This is why sections 7 and 8 exist and why every card is cited: BlinKode is built to be checked. Verification against the official code text remains part of your professional responsibility, and nothing in the Service transfers that responsibility to us.

Nothing in these terms limits liability that cannot be limited under applicable law, including for fraud or for death or personal injury caused by negligence.

13. Suspension and termination

You can stop using the Service and close your account at any time by emailing support@blinkode.ca. We may suspend or terminate an account that breaches these terms, or where we’re required to by law. Where circumstances reasonably allow, we’ll give you notice and an opportunity to export your projects first.

14. Changes to these terms

We may update these terms as the product develops. For material changes, including any change that introduces billing, we’ll give at least 30 days’ notice before they take effect. Continuing to use the Service after that means you accept the updated terms.

15. Governing law and disputes

These terms are governed by the laws of the Province of Ontario and the federal laws of Canada that apply there, without regard to conflict-of-laws rules. The courts of Ontario have jurisdiction, and you consent to their venue.

Talk to us first. If something goes wrong, email contact@blinkode.ca and give us a genuine chance to resolve it before starting formal proceedings. Most problems are faster to fix that way.

16. General

If any provision of these terms is found unenforceable, it will be limited or severed to the minimum extent necessary and the rest will remain in force. Our failure to enforce a provision isn’t a waiver of it. You may not assign these terms without our consent; we may assign them as part of a merger, acquisition or sale of assets. These terms, together with the Privacy Policy, are the entire agreement between us regarding the Service.

17. Contact

BlinKode Technologies Inc., 818–273 South Park Road, Thornhill, Ontario L3T 0B5, Canada.
General: contact@blinkode.ca · Support: support@blinkode.ca