Terms & Service Commitments

Terms of Service

The agreement

These terms apply when you buy or use our services. A written proposal or statement of work, where one exists, takes precedence over anything here that conflicts with it.

Fees and billing

• Engagement setup fees are one-time and payable before work begins.
• Hosting and user seats are billed monthly in advance and renew until cancelled.
• Prices shown in currencies other than US dollars are indicative; the final conversion is applied by Stripe at checkout.
• Taxes are added where applicable.

Cancellation

You may cancel a recurring subscription at any time, effective at the end of the paid period. One-time setup fees are not refundable once the work has started.

Your responsibilities

• Keep your account credentials secure and tell us promptly if they are compromised.
• Make sure you have the right to any content or data you give us to host.
• Do not use the service unlawfully or to harm others.

Intellectual property

You keep ownership of your content and data. We keep ownership of our platform, tooling and anything we built before or outside your engagement. On full payment you receive a licence to use the deliverables we built for you.

That licence is non-exclusive and is granted per tier. What each tier includes, and what the recurring component covers, is set out in Licensing & the Estimator.

One boundary is worth stating here rather than only there, because it is the one most often assumed the other way. The output of our APIs is yours — the records, documents and responses a service returns to you are your data and you may use, export and retain them. The orchestration engines that produce it are not licensed to you: the intake, validation and sequencing engines are protected trade secrets, run only in our infrastructure, and are not distributed or licensed for self-hosting. Nothing in these terms grants a right to the implementation behind an endpoint you are entitled to call. The full position, including what we do not claim, is in What integrators see, and what stays internal.

Liability

Nothing here limits liability that cannot lawfully be limited. Otherwise, our total liability is capped at the fees you paid us in the twelve months before the claim, and neither party is liable for indirect or consequential loss.

Enterprise Service Level Agreement

This SLA applies to customers on an enterprise agreement.

Availability

We target 99.9% monthly availability for hosted services, measured excluding scheduled maintenance announced at least 48 hours ahead. If we miss it, you may request a service credit within 30 days of the affected month.

Backups

Databases are backed up daily and the last 30 backups are retained. Point-in-time recovery is not enabled, so recovery is to the most recent daily backup rather than to an arbitrary moment; where an engagement needs finer recovery than that, it is scoped and priced.

Accessibility Statement

We want this site to be usable by everyone, including people who use a screen reader, navigate by keyboard, or need larger text or stronger contrast.

Our commitment

We build and test to WCAG 2.2 Level AA, and we apply Level AAA contrast on body text where it does not compromise legibility elsewhere.

What we have done

• A toolbar on every page for text size (100–150%) and high-contrast or monochrome viewing. Open it with the button at the bottom right, or press Alt + A.
• A "skip to main content" link as the first item for keyboard users.
• Visible focus outlines on every interactive control.
• Text alternatives for images, icons and status badges.
• Layouts that reflow to 320px and respect reduced-motion preferences.

Known limitations

Some longer video material does not yet have captions. We are working on it, and we will provide a transcript on request in the meantime.

Tell us if something does not work

Email info@gwizweb.com with the page and what happened. We aim to reply within 5 business days and will offer the information in another format if that is quicker for you.

Standards this site and the platforms are measured against

We build to WCAG 2.2 Level AA and test against it. The standards below are the ones that actually govern, and it is worth being precise about how they relate — several of them point back to the same WCAG criteria at different versions.

WCAG 2.2 Level AA

Our working target, and the strictest of the set. It adds criteria the older standards do not contain — focus appearance, dragging alternatives, and target size among them — so building to 2.2 covers the versions referenced below.

ISO/IEC 40500

ISO/IEC 40500:2012 is WCAG 2.0 ratified verbatim as an ISO standard rather than a separate rulebook. Meeting WCAG 2.2 Level AA meets it; we list it because procurement documents often cite the ISO number.

EN 301 549

The European public-procurement standard. Its current revision incorporates WCAG 2.1 Level AA for web content and adds requirements beyond the web — documents, hardware and support services — which are scoped per engagement rather than assumed.

ADA Title III

Title III itself sets no technical standard for websites; WCAG is what the Department of Justice has pointed to in enforcement and settlement agreements. We therefore treat WCAG 2.2 AA as the practical bar and document conformance rather than asserting statutory compliance, which only a court or regulator can determine.

AODA — the Canadian baseline

Ontario's Integrated Accessibility Standards Regulation requires WCAG 2.0 Level AA, excluding live captions and pre-recorded audio description. It is our floor, not our target: building to WCAG 2.2 clears it with margin.

What we actually ship

A skip link, visible focus that is never obscured by our own chrome, contrast and reduced-motion modes the visitor controls, decorative elements hidden from assistive technology, and theme-aware colour tokens defined for light and dark. Conformance is documented per engagement; we do not publish a blanket certification.

Non-exclusive, non-transferable

Clients receive a revocable licence to use the software as a service for the term of the engagement, covering the running system and its API output. It conveys no copy of the implementation, no right to sublicense or host it for a third party, and no right to reconstruct internal behaviour.

API output, not internals

An integrator sees request and response bodies. The rules, thresholds, orderings and prompts that produce those responses are not part of the interface and are treated as trade secrets.

What “black box” does and does not mean

It is accurate about distribution: the implementation is not handed over and an API consumer cannot read it. It is not a claim that the output cannot be studied. Anyone entitled to call an endpoint can observe what it returns, and we do not pretend otherwise.

Registered marks

ReliAble Independent Living Services Inc.® and ReliAble Living® are registered trademarks, used on this platform under licence from their proprietor. No client engagement conveys any right to use them.

Permitted use

Factual reference only — naming the service actually being received. The marks may not appear in a client’s own branding, product naming, domain names or advertising without separate written permission.

Separate from the trade-secret position

A trademark protects what the service is called; the trade-secret position above protects how it works. G Wiz Software Solutions Inc. asserts copyright in the platform itself. The three are additive, not alternatives.

What runs only in our infrastructure

Not deployed to client environments, not distributed.

Data ownership and residency

You own your data

We hold it as a processor, to operate the service, and assert no ownership of client records, documents or submissions. On termination it is exported in a machine-readable form on request and deleted on the agreed retention schedule.

Encryption

AES-256 at rest across every store, Google-managed. TLS enforced in transit, with HTTP redirected to HTTPS at the edge. Both apply regardless of region.

Residency, as currently configured

Canadian residency currently applies to the claim and assessment intake paths, which are stored in Toronto (northamerica-northeast2): the ReliAble Living secure intake documents, the scoping-estimator submissions, and the STRUCTiO SABS and HCAI referral records together with the pending-review queue holding referrals too incomplete to file. The operational databases, Firestore and media storage are in United States regions (us-central1, us-east1, us-west2, and the US multi-region).

That is residency of data at rest, not of processing. The applications on the SABS and HCAI intake path run on Cloud Run in us-central1, so a referral is stored in Canada and processed in the United States.

Canadian processing is staged for clients who need it. Because the referral database is already in Toronto, moving the service there is a redeployment rather than a data migration: the deploy is scripted, and its prerequisites — a Toronto subnet on the same network, the private services peering the database uses, project-scoped secrets — are verified rather than assumed. Nothing is running in Toronto today and this page will not imply otherwise; standing it up for a healthcare procurement that requires in-Canada processing is about an hour, and it is scoped in the engagement.

Any statement that the platform as a whole stores data in Canada would be incorrect, and we will not make one. Canadian regions are available for Cloud Run, Cloud SQL, Firestore and Cloud Storage, but moving an existing store is a migration with downtime rather than a configuration flag. Where an obligation requires Canadian residency, it is scoped and priced in the engagement.

If your procurement process requires Canadian residency for data listed above as United States, raise it before signing — it is an open item, not a solved one.

Data residency & tenant isolation

Where data is stored, and what keeps one tenant’s records away from another’s.

Canadian residency, stated precisely

The assessment and claim intake paths — the ones that carry claimant-identifying and clinical material, and the ones PIPEDA and SABS workflows actually touch — are stored in northamerica-northeast2 (Toronto). That now includes the STRUCTiO SABS and HCAI referral database, which holds referrals parsed out of intake mail and the review queue for the ones arriving incomplete, on a Cloud SQL instance with no public IP address.

The processing is not Canadian. The services on that path run on Cloud Run in us-central1; the records they write are in Toronto. Both halves are stated because only one of them is Canadian, and a reviewer asking about residency is usually asking about both.

The platform as a whole is not. Three of thirteen stores are Canadian; the operational databases, Firestore and the media buckets are in United States regions. A claim of blanket Canadian residency would be incorrect, and this page will not make one. The full table is in GOVERNANCE.md and is re-checked against the live infrastructure rather than carried forward.

Canadian residency for a store currently in the United States is available — Montréal and Toronto regions exist for Cloud Run, Cloud SQL, Firestore and Cloud Storage — but moving an existing store is a migration with downtime, not a flag. Where an obligation requires it, raise it before signing and it is scoped and priced as part of the engagement.

Tenant isolation in the query, not the interface

Tenant scope is applied server-side on every request, not by hiding a control. Access is re-checked per call rather than trusted from a token, so revoking an account takes effect immediately rather than at token expiry.

Each service runs as its own service account with secrets granted per secret where practical, so a compromise is bounded by that service’s grants rather than a shared project identity.

Database addressing

STRUCTiO’s database has no public IP and is reachable only over a private address from inside the VPC. Sessions are signed with a key held in Secret Manager rather than a per-instance value, so a session is valid across instances and invalid after rotation.

Encryption at rest is Google-managed AES-256 across every store, and TLS is enforced in transit with HTTP redirected at the edge. Those apply regardless of region.

What integrators see, and what stays internal

The boundary between the published interface and the implementation behind it, drawn where it actually falls.

Published: the API’s behaviour

Request and response bodies, status codes, error shapes, rate limits and the sequence in which calls must be made. Anything an integrator needs to build against, and anything they can observe by calling an endpoint they are entitled to call.

This is documented and stable. Breaking changes are notified before they reach production.

Internal: how the answer is produced

The rules, thresholds, orderings, prompts and schemas that turn an input into that response. Those run only in infrastructure operated by G Wiz Software Solutions Inc., are not deployed to client environments, and are treated as trade secrets.

Reverse engineering, decompilation, traffic interception to reconstruct internal logic, schema extraction, and bulk retrieval intended to reproduce a dataset or a model are each a breach of licence.

Where the phrase “black box” is accurate, and where it is not

It is accurate about distribution: the implementation is not handed over, and an API consumer cannot read it.

It is not a claim that the output cannot be studied. Anyone entitled to call an endpoint can observe what it returns and draw conclusions from it. We do not claim otherwise, and a vendor who does is describing something no hosted API can deliver.

Tenant scope is enforced in the query

Hiding a control is a convenience for the person using it; the boundary that matters is the one the server applies to every request. Access is re-checked on each call rather than trusted from a token, so revoking an account takes effect immediately rather than at token expiry.

Per-service identities

Each service runs as its own service account — STRUCTiO as sa-structio-app, and likewise for the platform backend, Dorothy @Home and the public site — so a compromise is bounded by that service's grants rather than a shared project identity. Secrets are granted per secret where practical.

Staff access, described accurately

Google and Microsoft work-account sign-in, with every OAuth round trip bound to the browser that began it and a mismatched callback refused with HTTP 403 before the code is redeemed. Administrative access is an explicit allow-list of individual addresses, re-checked on every request — not a domain rule; the current list includes three addresses outside @gwizweb.com. High-consequence actions additionally require a passkey confirmation valid for fifteen minutes.

Private database addressing

The STRUCTiO database has no public IP and is reachable only over a private address from inside the VPC. Sessions are signed with a Secret Manager key rather than a per-instance value, so a session is valid across instances and invalid after rotation.

Commercial Model & Licensing Terms

G Wiz Software Solutions Inc. operates a value-based, non-exclusive platform licensing framework. Hourly billing is not offered for build work, and there is no open à la carte per-feature price list.

Upfront System Analysis & Onboarding Fee

A one-time fee, paid before build work begins. It covers understanding the workflows you actually run, auditing the systems and integrations involved, reviewing data handling and access, and producing a written scope with a fixed price against it. Scope changes are re-quoted rather than absorbed silently.

Monthly Platform Licence Retainer

A recurring fee for the term of the engagement, covering the non-exclusive licence to use the running platform described above, together with hosting, monitoring and alerting, dependency and security updates, support and incident response. Billed monthly, and per seat where seats apply.

Why there is no per-feature menu

A published figure for a capability is either wrong or meaningless until someone has looked at the work. The same feature is a week against one intake process and a quarter against another, and quoting it as a line item moves the estimating risk onto whoever signs. Scope is established first, then priced once.

This is not a claim that no figure is ever published. A fixed entry fee for a defined tier does not vary with scope and can be stated honestly in advance; a menu a client could add up without anyone having examined their workflows cannot.

Currency

Prices are held in one currency as the source of truth. Checkout is presented and charged in your region’s currency, converted at the payment processor rather than against a rate table maintained here. That is regional checkout, not multi-currency accounting — the ledger side does not do multi-currency.

Licensing & the Estimator

How the System Analysis & Licensing Estimator routes a workflow into a formal analysis agreement — without a per-feature price list behind it.

It returns a routing, not a price

The Estimator asks what intake arrives, whether any of it routes to a named assessor or adjuster, what happens to documents once they arrive, and roughly how many arrive in a month. From that it indicates a track — managed CMS, or enterprise cloud architecture — and states the reasons for it.

The rule is one rule: work implying a queue with decisions in it is enterprise work. A brochure site with a contact form is not, however many pages it has.

What it is not

It is not a quote and produces no figure. It does not price features: there is no per-feature cost model behind it to expose. And it binds neither party — nothing is committed until a written scope is agreed and signed.

The routing is computed in the browser for immediacy and again on the server, which does not trust the browser’s copy. Both results are recorded, so a disagreement between them is visible rather than silently resolved.

How a routing becomes an agreement

1. The Estimator indicates a track, with its reasons.
2. Enterprise-track work begins with the Upfront System Analysis & Onboarding Fee. No build price is issued before the analysis is done.
3. The analysis produces a written scope with a fixed price against it. That document, not the Estimator’s output, is the commitment.
4. On acceptance the Monthly Platform Licence Retainer begins, under the non-exclusive licence described above.

Sample documents you upload to it

Stored in a bucket in northamerica-northeast2 (Toronto), separate from the ReliAble Living secure intake store, deleted automatically after ninety days, and never made publicly accessible.

The form asks for blank templates rather than completed files, because it is an ordinary web upload and not the secure intake path. If a file containing client information is sent in error, tell us and it will be deleted.

Infrastructure notes

The compute, networking and deployment detail behind the integrations. It is here rather than on the home page because it is how the platform is built, not what an engagement buys.

Serverless containers on Cloud Run

Each service runs as a container that scales from nothing to a traffic spike and back, billed for the seconds it actually ran. There is no instance to patch, and no capacity decision to get wrong in advance.

Health-gated releases

A new revision is deployed with no traffic and a private tag, checked on that tag, and only then moved to serving. A release that fails its check is never reached by anyone, and rolling back is a traffic change rather than a redeploy.

Private network addressing

Databases carry no public IP and are reachable only over a private address from inside the VPC. Services reach on-premise equipment through an outbound tunnel, so no port is opened on your network for us.

Per-service identity

Each service runs as its own service account with secrets granted per secret where practical, so a compromise is bounded by that service’s grants rather than by a shared project identity. The accounts are listed in the isolation section above.

Contact

Governance, privacy, security and procurement: info@gwizweb.com. Suspected exposure of client data: the same address, immediately and before remediation — remediating first frequently destroys the evidence needed to determine scope.

The full document, including the complete residency table, is maintained as GOVERNANCE.md in the site repository.