Intellectual Property & Licence

This Intellectual Property & Licence policy (this “IP Policy”) is part of the Cubicle Terms & Conditions. It binds every person and organization that accesses, views, evaluates, administers, hosts, screenshots, discusses internally, or otherwise uses Cubicle, including the participating school division, its trustees, officers, employees, substitutes, contractors, consultants, volunteers, IT staff, vendors, and anyone they allow to see the service.

By signing in, clicking to accept, using the service, or continuing to use it after this policy is posted, you agree. If you do not agree, do not access Cubicle and do not use knowledge of it to build anything else.

If any part of this IP Policy is held too broad to enforce, it will be narrowed only to the minimum extent required, and the rest remains in force. The Owner’s intent is the strongest protection of Cubicle that applicable law allows.

All right, title, and interest in and to Cubicle is and remains exclusively with the Cubicle Owner (the “Owner”). That includes, without limitation:

• Source code, object code, scripts, database schemas, migrations, configuration, and build tooling.
• Visual design, layout, typography, colour, motion, iconography, the Cubicle wordmark, and the distinctive schedule-board arrangement.
• User experience, information architecture, booking/share/swap/issue/QR workflows, and the way those pieces fit together.
• Documentation, legal pages, operator guides, label and QR designs, copy, and training explanations.
• Inventions, know-how, methods, algorithms, access-control model, sealed QR payload design, and other trade secrets.
• Updates, improvements, and future versions, whether suggested by users or not.

No school division, staff member, contractor, student, parent, or third party acquires ownership of Cubicle by using it, paying for hosting, suggesting a feature, appearing in a screenshot, or administering allowlists. Use is not authorship. Hosting school data in the service is not a transfer of the software.

Nothing in any informal conversation, ticket, email, or classroom demo is an assignment of intellectual property unless it is a written instrument signed by the Owner that expressly assigns those rights.

Subject to the Terms and this IP Policy, the Owner grants a limited, personal (or, for the division, institutional), non-exclusive, non-transferable, non-sublicensable, non-assignable, revocable licence to access the then-current hosted instance of Cubicle solely to coordinate school laptop-cart operations for the participating division, and only while the user remains allowlisted.

This is a licence to use the live service. It is not a sale of software, not a copy of the source, not an on-prem perpetual licence, not an escrow of code, and not permission to reproduce Cubicle anywhere else.

• You may not copy, download (except ordinary browser caching), or retain the application except as technically required to display a page you are authorized to see.
• You may not sublicense, rent, lend, lease, timeshare, or commercially exploit the service.
• You may not move Cubicle to another school, company, or product without a separate written licence from the Owner.
• When access ends, the licence ends immediately. Knowledge you gained while using Cubicle remains subject to the prohibitions below.

The participating school division is a licensee, not a co-owner, not a joint author, and not a commissioner of a work made in the course of employment for the Owner unless a separate written agreement signed by the Owner says otherwise.

Providing Cubicle to the division, connecting it to school Google accounts, storing school operational records, or listing the service in an internal catalogue does not:

• Assign copyright, trademark, industrial design, or trade-secret rights to the division or to the Crown.
• Create a work made for hire, a commissioned work, or an implied licence to reproduce Cubicle.
• Authorize the division to obtain a competing or replacement system by showing Cubicle to a vendor, student intern, or staff developer.
• Authorize the division to sell, gift, open-source, or “hand over” Cubicle to another school, consortium, or ministry.
• Give the division a right to source code, design files, or a local copy of the repository.

School operational records (bookings, issues, inventory, allowlist) remain school records as described in the Privacy Policy. The software that processes those records remains the Owner’s.

Except to the limited extent a mandatory statute cannot be waived, and except with the Owner’s prior explicit written permission, no person or organization may do any of the following with Cubicle or with knowledge obtained from it:

• Copy, reproduce, republish, or distribute the software, interface, documentation, or distinctive visual design.
• Sell, licence, lease, gift, or otherwise transfer Cubicle or a copy or adaptation of it.
• Remake, rewrite, reimplement, port, or rebuild Cubicle, in whole or in part.
• Create a derivative work, fork, clone, “inspired by” version, or unofficial companion app.
• Create a competing, substitute, or overlapping product for booking, sharing, swapping, or labelling school technology carts or similar equipment.
• Commission, hire, or pay anyone else to do any of the above.
• Use Cubicle as the specification, prototype, or reference for a request for proposals, intern project, capstone, hackathon, or vendor bid.
• Open-source, publish, or leak any part of Cubicle, including screenshots used as a build guide.
• Remove, hide, or alter proprietary notices, legal pages, or the Cubicle wordmark.

These prohibitions apply whether the result is free or paid, internal or public, web or native, open-source or closed, “just for our school” or for resale.

Changing the look does not make a copy lawful. You may not create a product that is similar to Cubicle by dressing it in a different colour, typeface, layout, component library, or brand name, or by adding, removing, or rearranging features.

Without the Owner’s explicit written permission, you may not:

• Reproduce Cubicle’s structure, sequence, and organization (for example a period board, cart inventory, share/swap/issue flows, QR labels, and staff allowlist) under another name.
• Translate Cubicle into another framework, language, or platform (including “we rewrote it in X”).
• Ship a “simplified”, “mobile-only”, “admin-only”, or “white-label” variant.
• Claim independent creation where the new work was built by people who used, administered, or were briefed on Cubicle.
• Use a different UI, different feature set, or different branding as a defence if the work is derived from, modelled on, or intended as a replacement for Cubicle.

Generic facts (that schools share laptop carts) are not monopolized. What is protected — and what you are forbidden to take — is Cubicle itself: its expression, its combination of workflows, its look and feel, its documentation, and any substitute built from exposure to it.

You may not “take inspiration” from Cubicle to produce another scheduling, inventory, or staff-operations product. You may not use memory, notes, recordings, screenshots, screen shares, or verbal walkthroughs of Cubicle as the brief for a designer, developer, student, or vendor.

• Do not send Cubicle screenshots or recordings to an outside developer “so they know what we need”.
• Do not write an RFP or statement of work that is Cubicle restated in other words.
• Do not ask staff to list Cubicle’s screens or rules so another app can match them.
• Do not use Cubicle as a teaching example for how to build a competing internal tool.
• Do not train or fine-tune a model on Cubicle’s UI, copy, schema, or source in order to generate a similar product.

If the division later wants a different system, it must specify its operational needs independently, without using Cubicle as the template, and must not copy Cubicle’s expression. When in doubt, obtain the Owner’s written permission first.

Non-public aspects of Cubicle are the Owner’s confidential information and trade secrets, including architecture, access control, QR seal design, unpublished features, security configuration, and operator documentation.

• You will not disclose that information except to other authorized staff who need it for legitimate school use of the live service.
• You will not publish it, post it in public issue trackers, or give it to vendors.
• Confidentiality continues after you leave the school or stop using Cubicle.
• School operational records remain confidential school information as well; this section does not make those records the Owner’s property.

Cubicle source and design materials, where they exist, are private. Access to a repository, hosting account, or design file — if ever granted — is a limited, revocable privilege and not a gift of ownership.

• Do not clone, fork, mirror, or download the repository except as the Owner expressly allows in writing.
• Do not add collaborators, make the repository public, or copy it to another host.
• Do not extract assets, fonts, or components for other products.
• Any copy you hold after access is revoked must be destroyed.

Without the Owner’s explicit written permission, you may not:

• Decompile, disassemble, reverse engineer, or attempt to derive source or schemas from the client, network traffic, or QR payloads, except only as a mandatory statute for interoperability cannot be waived — and even then, only after written notice to the Owner and only for lawful interoperability with Cubicle itself, never to build a substitute.
• Scrape, crawl, or bulk-export the interface or data except through features IT has approved for school reporting.
• Probe, fuzz, or attack the service as “research” on production systems without written authorization.
• Feed Cubicle’s UI, copy, or code into a generative model to produce a similar application, theme, or workflow.

“Cubicle”, the Cubicle wordmark, and related logos and product names are trademarks and official marks of the Owner, whether registered or unregistered. You may refer to Cubicle factually as the school’s internal cart-scheduling tool. You may not:

• Use Cubicle marks on another product, bid, or website in a way that suggests sponsorship or that the other product is Cubicle.
• Register domain names, social handles, or app-store listings that impersonate Cubicle.
• Issue a press release claiming the division owns or built Cubicle.

If you suggest an idea, design, name, or improvement, you assign to the Owner all intellectual-property rights in that feedback, to the extent you have any, and you waive moral rights in it to the extent permitted by the Copyright Act (Canada) and other applicable law. The Owner may use feedback without credit, payment, or obligation.

Suggesting a feature does not make you a co-author and does not entitle you to a licence beyond ordinary use of the live service.

Bookings, issues, inventory, and staff directory fields are school operational records. The Owner processes them to run the service and does not claim to own the division’s underlying facts (who booked which cart). The Owner does claim ownership of the software, schema design, and presentation used to store and show those facts.

Exporting school records through approved admin tools for school purposes is allowed. Exporting them in order to populate a clone of Cubicle is not.

This IP Policy binds, without limitation:

• Every signed-in user, including teachers, substitutes, temporary staff, and administrators.
• The participating school division as an institution, and its board, officers, and agents.
• Contractors, consultants, managed-service providers, and student interns who see Cubicle in the course of work for the division.
• Anyone who obtains Cubicle materials from a person who was bound.

The division will not authorize, fund, or look the other way on a project that would breach this IP Policy. Staff who commission a clone still breach this policy personally as well as on behalf of the institution.

The only exception to the prohibitions in this IP Policy is prior explicit written permission from the Owner. Verbal approval, a Slack or Teams message, a ticket comment, silence, or continued provision of the service is not permission.

Written permission, if granted, will state the exact scope (who, what, how long, for which school). Anything not stated is withheld. Permission may be refused for any reason or no reason, and may be revoked.

Requests: it-support@rbe.sk.ca with the subject line “Cubicle Owner — written IP permission”.

Sections concerning ownership, prohibitions, confidentiality, trade secrets, moral rights, trademarks, remedies, and this survival clause continue after you stop using Cubicle, after you leave the school, and after the division stops using the service.

A breach of this IP Policy would cause irreparable harm for which money may be inadequate. The Owner may seek immediate injunctive or other equitable relief in any court of competent jurisdiction, without the need to post a bond to the extent a court will allow, and without limiting any other remedy.

The Owner may also recover damages, disgorgement of profits from a forbidden product, destruction or delivery-up of infringing copies, and reasonable legal fees to the extent permitted by law. These remedies are cumulative.

Unauthorized copying or circumvention of technical measures may also violate the Copyright Act (Canada) and other criminal or civil law. The Owner may report unlawful access or theft of trade secrets to law enforcement.

Allowing the division to use Cubicle, fixing bugs, adding features, or remaining silent about a suspected copy is not a waiver of the Owner’s rights. Waiver requires a written instrument signed by the Owner that identifies the specific right waived.

School operational questions: it-support@rbe.sk.ca.

Infringement, cloning, unauthorized repositories, or permission requests: the same address, subject “Cubicle Owner — IP”.

Related documents: Terms & Conditions, Acceptable Use Policy, Privacy Policy, Security & Data Safety.

This IP Policy is posted at mycubicle.app. The effective date above is the current version.