Terms of Service — Hosted AccessPoint

Version française : Conditions d'utilisation — AccessPoint hébergé

Last updated: November 10, 2026
Effective: when AccessPoint 2.6.0's hosted service opens
Provider: Realizer Services Inc., head office in Nova Scotia, Canada
Contact: support@realizer.io

These terms are the agreement between Realizer Services Inc. ("Realizer") and an organization that uses Hosted AccessPoint.

1. These terms

1.1 What they cover. These terms govern Hosted AccessPoint ("the service"): the AccessPoint software that Realizer runs for organizations, reached at app.realizer.io and at the regional addresses it sends people to, such as ca.app.realizer.io. They do not cover:

• AccessPoint for Microsoft 365, which a customer deploys in its own Microsoft 365 and Azure and buys through the Microsoft commercial marketplace;
• the AccessPoint Training Lab (learn.realizer.io), which runs under its provider agreement;
• Realizer's website and demo, which Realizer's general Terms of Service cover.

1.2 Accepting them for an organization. The service is for organizations: public bodies, businesses, non-profit organizations and professional practices. The person who creates an organization in the service accepts these terms on its behalf. So does each member who becomes an Administrator, or who buys a plan, add-on or bundle for it. Each of them confirms that they may bind the organization. "You" and "your organization" mean that organization.

1.3 What the agreement is made of.

• These terms.
• The price list in force when you buy: the prices, plans, allowances and add-ons shown on Realizer's pricing page and in Settings → Subscription.
• Realizer's privacy notice (https://www.realizer.io/privacy), which describes how Realizer handles personal information in the service.
• Any written agreement your organization signs with Realizer for the service, such as an Enterprise agreement (section 12).

A signed written agreement prevails over these terms where they differ. The privacy notice governs how personal information is handled; what these terms add to it, such as the incident notice in section 14.7, also applies. For the service, these terms replace Realizer's general Terms of Service.

1.4 Words used in these terms.

• Member: a person your organization has admitted to the service.
• Administrator: a member who holds the Administrator role, or another role your organization gives the permission to manage its settings.
• Account contact: the person whose name and e-mail address Realizer keeps for security and account notices. At first it is the person who created the organization.
• Customer data: everything your organization and its members put into the service or receive through it — cases, documents, recordings, contacts, configuration, members' details and audit records — and what the service produces from it.
• Plan: the trial, Free, Essentials, Professional or another plan on the price list. A paid plan is one with a price.
• Allowance: the requests and assessments a plan includes, and the monthly amounts of a metered add-on.
• Add-on: an optional module sold monthly or yearly with a paid plan, such as AI Assist, the public portal, media or AccessPoint Learning.
• Bundle: a one-time purchase of extra units, such as 10 requests.
• Read-only: readable, searchable, reportable and downloadable, with no new case, no change to a case and no new release.
• Lab mode: the training copy of your organization, which holds fictional cases.

2. The service

2.1 What it is. The same AccessPoint software as the Microsoft 365 edition — requests, complaints, assessments, privacy breaches, audits, risks and the privacy program, with redaction, letters, computed deadlines and reports — run by Realizer and used in a web browser. Lab mode, with fictional training cases, is included on every plan.

2.2 What it does not include. Features that need your organization's own Microsoft 365 or Azure are not part of the service: capturing records from Microsoft 365, Teams notices, the directory check, roles bound to Entra groups and repository connectors. They are part of AccessPoint for Microsoft 365.

2.3 Where your data is kept. Your organization chooses its region at sign-up, from the regions open to new organizations. At the date of these terms there is one, Canada: data is stored in Microsoft Azure's Canada Central region, with backups and copies of stored files in Canada East, and it stays in Canada except as section 14.5 says. app.realizer.io is the service's entry, where people sign up and sign in before they are sent to their organization's region. Realizer does not move your organization's data to another region without the written agreement of one of its Administrators.

2.4 Updates. Realizer updates the software regularly. Updates are part of the service and need no action from you. Section 23 says what happens when a change removes something your paid plan relies on.

3. Members and Administrators

3.1 Members. Members are unlimited on every plan. A person joins only through an Administrator's invitation, accepted with a Microsoft account that proves the invited address. A colleague from the organization's own Microsoft organization may ask to join; an Administrator decides, and an approval is such an invitation. Administrators choose whether colleagues can find the organization this way. Administrators can limit the organization to accounts of named Microsoft organizations (Who can join) and choose how soon idle members are signed out.

3.2 Sign-in. Members sign in with a Microsoft work, school or personal account. Microsoft and the account's own organization check its password and multi-factor authentication; Realizer never sees a password. Your organization asks its members to protect their accounts.

3.3 Who you admit. Your organization decides who becomes a member and which roles each one holds, and it is responsible for what its members do in the service. The service has no link to your directory, so it does not notice when someone leaves: remove leavers yourselves. Tell support@realizer.io at once if you believe someone has reached your organization without permission.

3.4 Administrators and the account contact. Keep at least one Administrator — we recommend two — who reads the e-mail AccessPoint sends. Trial reminders, allowance warnings, the move to the Free plan and deletion warnings go to Administrators, and only Administrators can buy. Keep the account contact current by writing to support@realizer.io: it is where Realizer sends security and account notices.

3.5 One organization, its own records. Each organization uses the service for its own records. Handling requests, assessments or other cases for other organizations — as a consultant, a service firm or a shared service — needs a written agreement with Realizer. Do not create organizations to repeat a trial or to get around a plan's limits. Only the first organization an account creates, and the first of a Microsoft organization, starts with the trial; any other starts on the Free plan. Realizer limits how many organizations one account creates.

4. Plans

4.1 The plans. The service is offered as a free 30-day trial, the Free plan, paid plans (Essentials and Professional at the date of these terms) and Enterprise by written agreement. The price list says what each plan includes: its price, its registers, its allowances, its storage and the add-ons sold with it.

4.2 Read-only, never hidden. A register or add-on outside your plan is read-only. What your organization made with it stays readable and downloadable.

4.3 Changes. Section 23 says how Realizer changes prices and plans.

5. The free trial

• The trial lasts 30 days from the day the organization is created. It needs no card, and it never turns into a paid subscription by itself.
• It includes every register and every add-on except the public portal, within the trial's allowances shown in Settings → Subscription.
• An Administrator may extend it once, by 30 days, from day 20 of the trial until 30 days after the move to the Free plan — for example while a purchase order or a security review is pending. Realizer may extend a trial further at its discretion.
• When the trial ends without a paid plan, the organization moves to the Free plan (section 6). Nothing is deleted.
• Each organization has one trial.

6. The Free plan

• Your organization moves to the Free plan when its trial ends without a paid plan, or when its paid subscription ends.
• Free includes 5 requests and 5 assessments a year worked in full; audits are not included. This allowance belongs to your Microsoft organization (for a personal Microsoft account, to that account), not to one organization in the service: all the organizations on the Free plan created with accounts of the same Microsoft organization share it, each taking a request or an assessment from it when it needs one, and its year is counted from the day the first of them moved to Free. Deleting or abandoning an organization does not renew or restore it. Every received request can still be recorded beyond that (section 8).
• Everything else stays readable and downloadable but is read-only: the other registers and the add-ons. AI Assist and OCR are off. Add-ons and bundles cannot be bought on Free; bundle units bought earlier stay usable until they expire.
• Lab mode stays on. Uploading your own files into Lab mode is off.
• Free has smaller storage and e-mail limits than the paid plans (sections 9.3 and 16).
• Free costs nothing and needs no card. Realizer provides it as is, may change what it includes with 30 days' notice, and may end the Free plan with 90 days' notice, during which your organization can download its data or choose a paid plan.
• A Free organization nobody uses is deleted after warnings (section 15.4).

7. Allowances

7.1 What counts.

• A request counts once, when it is recorded. A Draft request that is deleted gives its unit back. A closed request brought in by a data import does not count. Nothing in Lab mode counts.
• An assessment or audit counts when it is started. An update assessment of an assessment that is in effect is free.
• Members, documents and pages never count.

7.2 How allowance arrives.

• Monthly subscriptions: each paid month's allowance arrives when the month is paid. What is not used is kept until it is 12 months old.
• Annual subscriptions: when the year is paid, 15 months' allowance arrives at once. It lasts until the end of that year and does not carry into the next.
• Bundles: their units arrive when they are paid for and last 12 months.
• Units are used in the order they expire. No allowance arrives for a period that is not paid.

7.3 When the plan changes.

• Upgrade: the extra allowance for the rest of the period arrives when the prorated charge is paid (section 11.3).
• Downgrade: allowance already received stays until it expires.
• End of a paid plan: the plan's allowance ends with it. Bundle units stay until they expire.

8. When an allowance is used up

8.1 A received request can always be recorded. Whatever its plan or allowance, your organization can record a request it has received. The request gets its number, received date, computed due date, requestor and documents, and the automatic acknowledgement your organization set up goes out. It appears in lists, My Day and reports, and it can be closed or withdrawn.

8.2 Its case work waits. Past the allowance, the work on such a request — assignments, letters, fees, redaction, extensions, consultations and release — waits until a unit covers it: the next allowance, a bundle or a plan change. Units go to waiting requests, earliest due date first. Moving from the trial or Free to a paid plan unlocks every waiting request at once.

8.3 Assessments. Past the allowance, a new assessment or audit cannot be started.

8.4 No surprise charges. There is no overage billing and no automatic top-up. Administrators are warned in the service at 80 % and 100 % of an allowance, and by e-mail when it is used up. An Administrator can buy a bundle in one click, charged to the card on file.

8.5 Your deadlines keep running. A waiting request's statutory clock runs as it would anywhere else. Your organization decides whether to add units, change plan, wait for the next allowance or answer outside AccessPoint, and it is responsible for meeting its deadlines. Realizer is not responsible for a deadline missed while a request waits.

9. Add-ons, bundles and storage

9.1 Add-ons.

• An Administrator can add an add-on to a paid subscription at any time. The rest of the current period is charged, prorated, on the next invoice.
• Removing an add-on takes effect at the end of the period already paid, and it keeps working until then. Nothing is refunded or credited for that period, and nothing made with it is deleted: it becomes read-only.
• A metered add-on, such as AI Assist, OCR or media, has a monthly allowance that resets each month and does not carry over; usage bundles add to it. When both are used up, the feature pauses until the next month or a new bundle. Recording requests, deadlines, letters, redaction by hand and release never stop.
• An add-on is sold only where the service runs it.
• The public portal is not part of the trial. When the public portal add-on ends, or your organization becomes read-only, the portal stops accepting new submissions; what it already received stays. Your organization tells requesters how else to reach it. A payment provider your organization connects to collect fees from requesters is its own supplier, under its own agreement with that provider.

9.2 Bundles.

• Bundles are one-time purchases, for paid plans only, charged to the card on file when an Administrator buys them.
• Their units last 12 months from purchase, whatever plan your organization moves to — Free included — and then expire.
• Bundles are not refunded or exchanged, and unused units are not credited. If Realizer refunds a bundle it charged in error, it withdraws that bundle's unused units; units already used stay used.

9.3 Storage.

• Each plan holds a set amount of files — originals and their converted copies — shown on the price list. A paid plan can add more with the extra-storage add-on.
• When storage is full, members cannot add new files. What arrives with a received request, such as a requester's attachments or intake e-mail, is always stored.
• Realizer never deletes files to make room.

10. Fees, currency and taxes

10.1 Prices. Your organization pays the fees of the price list in force when it buys, for the plan, interval, add-ons and bundles its Administrators choose.

10.2 Currency. Before the first purchase, an Administrator chooses the organization's billing country, which sets its currency:

• Canada: Canadian dollars;
• the United States: US dollars, at the same numbers as in Canadian dollars;
• the United Kingdom, Jersey, Guernsey, the Isle of Man and Gibraltar: pounds sterling;
• the euro area and the other places that use the euro: euros;
• everywhere else: US dollars.

Prices are face values in each currency; Realizer does not convert them. The currency stays with the subscription. To pay in another currency, your organization subscribes again in it at the end of a paid period, which Realizer helps arrange.

10.3 Taxes. Prices do not include taxes.

• For an organization billed in Canada, Realizer adds GST/HST, and any provincial sales tax it is registered to collect.
• Elsewhere, Realizer adds no sales tax unless it becomes registered to collect it there. Your organization accounts for any tax its own law places on the purchase.
• An organization that is exempt from a tax gives Realizer the evidence the law requires before it is invoiced.
• If the law requires your organization to withhold tax from a payment, it pays the additional amount needed for Realizer to receive the full fee.

11. Billing, renewal, plan changes and cancellation

11.1 Payment through Stripe. Paid plans are billed by card through Stripe, Realizer's payment processor. Card numbers go to Stripe and never reach Realizer or AccessPoint. Invoices are sent through Stripe to the billing e-mail address — at first, that of the Administrator who first opened checkout. Your organization keeps a valid payment method on file.

11.2 Automatic renewal. A paid subscription renews automatically at the end of each month or year, for the same interval, and the card on file is charged, until it is cancelled.

11.3 Changing plan. An Administrator changes plan on Stripe's billing page (Manage billing).

• A change that costs more — an upgrade, or monthly to annual — takes effect at once. The prorated difference for the rest of the period is invoiced and charged at once.
• A change that costs less — a downgrade, or annual to monthly — takes effect at the end of the period already paid.

11.4 Cancelling. An Administrator can cancel at any time in Manage billing. The cancellation takes effect at the end of the period already paid. Until then the plan keeps working; afterwards the organization moves to the Free plan. Cancelling does not close the organization — section 15.3 says how to do that.

11.5 No refunds of partial periods. Fees are not refunded for a period that has started — for a cancellation, a downgrade or an add-on removed during the period — or for allowance that was not used. The only refunds are for a charge Realizer made in error, those that sections 14.4, 22.3 and 23 promise, and those the law requires.

11.6 Billing errors. Tell support@realizer.io about a charge you believe is wrong within 60 days of it. Realizer corrects a confirmed error by refund or credit.

11.7 Failed payments. If a renewal payment fails, Stripe retries it over about two weeks. Meanwhile the subscription keeps working, but no new allowance arrives until the payment succeeds. If every retry fails, the subscription is cancelled and the organization moves to the Free plan: nothing is deleted, and whatever Free does not include becomes read-only. The unpaid amount remains owed, and Realizer may ask for it before the organization subscribes again.

12. Enterprise and other written agreements

Enterprise plans are sold by written agreement, usually an annual contract billed by invoice. So are invoice or purchase-order billing, a dedicated database or region, a service-level commitment and any other term Realizer agrees to in writing. A signed written agreement prevails over these terms where they differ, and these terms govern everything it does not cover. Terms printed on a purchase order or in your organization's own forms do not apply unless Realizer signs them.

13. Your data

13.1 It is yours. Your organization owns its customer data. Realizer claims no rights in it except the right to host, copy, process, transmit and display it as needed to provide, secure and support the service for your organization, and as the law requires.

13.2 Your organization's responsibilities. Your organization is the controller of the personal information in its customer data: it decides what it collects, keeps and deletes. It is responsible for:

• having the legal authority to collect and use what it puts into the service, and giving the notices its law requires;
• the content of its records, letters and uploads;
• its retention periods and preservation holds;
• answering people's requests about their information, with Realizer's help (section 14.6);
• its own assessment of using a hosted service, including whether the locations in section 14.5 meet its residency and procurement rules;
• telling its staff never to enter real personal information into Lab mode's training cases.

13.3 The privacy notice. Realizer's privacy notice says what personal information the service holds, where, for how long and who processes it, and Realizer handles personal information as it says.

13.4 What Realizer does not do. Realizer uses customer data only to provide, secure and support the service. It does not sell customer data, share it for anyone else's purposes, use it for advertising or use it to train AI models.

13.5 Realizer's own records. Realizer keeps its own records of the service: your organization's name and region, its plan and billing state, the account contact, counts and dates of its use (such as how many members signed in — never the content of a case) and the technical logs needed to run and secure the service. Realizer is the controller of these records and uses them to run, secure, bill and support the service and to report on it, as the privacy notice describes.

14. How Realizer processes your data

These commitments apply to the customer data Realizer processes for your organization as its processor (service provider).

14.1 Instructions. Realizer processes customer data only to provide the service as these terms describe and as your organization uses and configures it — which together are your organization's instructions — and as the law requires. If the law requires other processing, Realizer tells your organization first, unless the law forbids it.

14.2 People. Only Realizer personnel who need access to operate, secure or support the service have it, and each is bound to keep customer data confidential. Operations on a whole organization — an export, a move between databases, a deletion — run only through logged operator commands inside the service's own environment, never through a web page.

14.3 Security. Realizer keeps reasonable technical and organizational safeguards in place, including:

• encryption in transit and at rest;
• each organization's data kept apart at every layer, so no other organization can reach it;
• sign-in through Microsoft;
• malware scanning of uploaded files;
• a tamper-evident audit ledger of what happens on each case;
• monitoring and alerts;
• backups kept in Canada.

14.4 Service providers. The service providers that process customer data are listed in the privacy notice. At the date of these terms the only one is Microsoft, which hosts the service, signs people in, carries its e-mail and runs its AI services. Stripe processes billing details, not customer data.

• Realizer is responsible for its service providers' processing as for its own, within section 27.
• Before a new service provider starts processing customer data, Realizer tells your Administrators by e-mail at least 30 days ahead. Only an urgent change needed to keep the service secure or running may come sooner, and then Realizer tells them as soon as it can.
• If your organization objects on reasonable grounds and Realizer cannot resolve the objection, your organization may end its subscription, and Realizer refunds the unused part of any period already paid.

14.5 Locations. Customer data is stored in your organization's region — Canada at the date of these terms. It is processed outside that region only:

• by Microsoft's sign-in and Azure Front Door, global services that handle each request on its way in;
• by AI Assist's models, and only after an Administrator allows it (section 17).

14.6 Help with your obligations. Realizer helps your organization, as far as it reasonably can, to answer people's requests about their information, to respond to a regulator and to assess the service. Most of this is self-serve: the download of section 15.1, the service's exports, the privacy notice and Realizer's privacy and security documentation.

14.7 Security incidents. If Realizer confirms a security incident that has affected, or likely affected, your organization's customer data, it tells your Administrators and account contact by e-mail without undue delay, and no later than 48 hours after confirming it.

• The notice says what Realizer knows and what it does not know yet. Realizer keeps your organization updated as it learns more.
• Realizer takes reasonable steps to contain the incident and gives your organization the information it needs for its own notices to regulators and individuals.
• Telling your organization about an incident is not an admission of fault.

14.8 Demands from authorities. If a court, government or other authority demands customer data from Realizer, Realizer refers it to your organization where it can, tells your organization unless the law forbids it, and discloses only what it is legally required to.

14.9 Information about the service. Realizer makes available the documents that describe how the service protects customer data — the privacy notice, its privacy impact assessment material and its security documentation — and answers reasonable written questions about them. On-site audits and independent assessments are available only under a written agreement (section 12).

15. Downloading your data, leaving and deletion

15.1 Download at any time. An Administrator can download all of the organization's data from Settings → Subscription — every record and file, requester details included; Lab mode's fictional cases are left out. It works on every plan and in every state, read-only included. Up to three downloads can be started a month, and each is kept for 14 days. Case exports, response packages and the Settings export workbook stay available too.

15.2 When Realizer deletes customer data. Only:

• when your organization deletes it, or its own retention rules purge it;
• when your organization leaves (section 15.3);
• when an unused Free organization is deleted after warnings (section 15.4);
• after the agreement ends (section 15.5); or
• where the law requires it.

15.3 Leaving. To close the organization, an Administrator writes to support@realizer.io.

• Realizer confirms the request with your Administrators, records a complete export of the organization and offers it to them — on request, in the form that AccessPoint for Microsoft 365 imports.
• Realizer deletes the organization after the export has been offered for 30 days, or sooner if an Administrator asks, and in any case within 60 days of the request.
• Closing deletes everything, including cases under a preservation hold.
• Cancelling a paid subscription alone does not close the organization: it moves to the Free plan.

15.4 Unused Free organizations. A Free organization is unused when no member has signed in and no case has been created (public-portal submissions included) for 12 months — or, for an organization that never really started (no real case, a single member and no Lab mode case finished), for 90 days after its move to Free. Realizer may then delete it, under these rules:

• Every active Administrator is warned by e-mail 30 days and 7 days before the deletion date, and Settings → Subscription shows the date.
• While the organization holds an open received request, the first warning comes at least 90 days before the date, and every warning gives the number of open requests.
• A warning that reached nobody is sent again and does not count.
• Any member's sign-in, or a new case, cancels the deletion and starts the count again.
• A preservation hold on any case prevents the deletion.
• The deletion is done by Realizer's staff after the date has passed, never automatically.

Trial and paid organizations are never deleted for inactivity. Realizer may also remove an organization whose creation was never completed.

15.5 After the agreement ends. When the agreement ends under section 22, your organization stays read-only for 30 days so its Administrators can download its data, and Realizer then deletes it.

15.6 Deletion is final. A deleted organization cannot be restored. Copies of deleted data remain in Realizer's backups and logs until they age out, within 60 days. Realizer does not use or restore those copies, except while recovering the whole service after an incident, after which it deletes them again. Realizer keeps its own records of a deleted organization as the privacy notice describes.

16. E-mail sent through the service

• Letters, notices, invitations and codes go from Realizer's shared sending address, accesspoint@notices.realizer.io, under your organization's name. Replies go to the address an Administrator chose and confirmed.
• Your organization is responsible for what it sends and to whom.
• The service limits how many recipients each organization reaches an hour and a day, with lower limits on the trial and the Free plan. Mail over the limit is not sent. Realizer may lower an organization's limits where they are misused.
• Realizer sends Administrators its own fixed notices about the trial, the plan, allowances and deletion. Switching your organization's e-mail notices off stops the reminders, but never a notice that affects your records: the move to the Free plan, an allowance used up or a deletion warning.

17. AI Assist

• AI Assist — Ask AccessPoint, drafting, summaries, translation and AI suggestions such as redaction suggestions — is optional: an add-on on paid plans, and included in the trial.
• It sends the text a feature needs, which can include personal information from your cases, to Azure OpenAI models that Realizer provisions in Canada. Microsoft offers those models only as global deployments, so Microsoft may process prompts and answers in its other Azure regions worldwide.
• For that reason, AI Assist stays off for each organization until one of its Administrators reads the statement in Settings and allows it. An Administrator can withdraw that permission at any time, and the AI features that need it stop at once. If the statement changes materially, AI pauses until it is allowed again.
• What the AI produces is stored in your organization's region, like everything else. Microsoft does not use prompts or answers to train its models; its abuse monitoring applies under Microsoft's terms, and your organization uses AI Assist in line with Microsoft's code of conduct for Azure OpenAI.
• Text recognition (OCR), search and transcription are processed in Canada and need no permission.
• AI output can be wrong, incomplete or out of date. It is a suggestion for a person to check: drafts open in an editor and are never sent by themselves, and AI redaction suggestions apply only when a person accepts them. Your organization makes every decision, and it is responsible for what it sends, releases or withholds.

18. Jurisdiction packs, computed outputs and your decisions

18.1 What they are. AccessPoint includes jurisdiction packs and other content describing laws, regulations, deadlines, fees, exemptions, notification duties and reporting formats ("jurisdiction content"). It calculates dates, figures and statuses from your records using that content ("computed outputs").

18.2 Provided as is. Jurisdiction content is prepared from publicly available sources as of the version date shown in the product, and is provided "as is" for general information. It is not legal advice, and Realizer does not review it against your organization's circumstances. Laws and regulators' instructions change. Applying a pack asks the Administrator to confirm that the organization understands this.

18.3 Your organization's responsibility. Your organization is responsible for confirming jurisdiction content before relying on it, adjusting it in Settings where it does not fit, checking computed outputs and AI suggestions before it submits or acts on them, and its own compliance. AccessPoint is a case-management tool; using it does not make an organization compliant.

18.4 No warranty. To the extent the law allows, Realizer makes no warranty that jurisdiction content or computed outputs are complete, current or accurate for any purpose, and is not liable for any loss arising from reliance on them.

18.5 Updates. Realizer may update jurisdiction content at any time. An update reaches your organization only when an Administrator applies it, and applying a pack never overwrites an item your organization changed unless a full import is chosen and confirmed.

19. Acceptable use

Your organization and its members must not:

1. use the service in breach of the law or of anyone's rights, or to store or send content the organization has no right to hold;
2. send bulk, marketing or unsolicited e-mail through the service, or try to get around its e-mail limits;
3. try to reach another organization's data, accounts or sessions, or any part of Realizer's systems beyond what the service offers you;
4. probe, scan or test the service's security, or load-test it, without Realizer's written permission — report a suspected vulnerability to security@realizer.io instead;
5. interfere with the service, overload it, or get around its limits — allowances, storage, e-mail limits or the limits on creating organizations — for example by creating organizations to repeat a trial;
6. upload malicious code on purpose (records that happen to contain it are held by malware scanning);
7. reach the service by automated means other than the features Realizer provides;
8. resell, rent or sublicense the service, or give anyone access other than as a member acting for your organization;
9. reverse-engineer the service, except as far as the law allows despite this term;
10. enter real personal information into Lab mode's training cases;
11. use the service where sanctions laws that apply to Realizer forbid it.

Realizer may remove or block content that breaks these rules, and may suspend the organization under section 21.

20. Availability, maintenance and support

• Realizer works to keep the service available, but provides it without a service-level commitment: no promised uptime, response time, recovery time or amount of recent work that could be lost in a recovery, unless a written agreement says otherwise (section 12).
• Realizer plans maintenance for quiet times. It posts service events — outages, degraded service and maintenance with a noticeable effect — on its status page, https://www.realizer.io/status.
• Realizer keeps backups in Canada to recover the service after an incident. They are not a way to restore records your organization deleted.
• Support is by e-mail at support@realizer.io, with no promised response time outside a written agreement. The help pages in the product and on Realizer's website explain how the service works.

21. The read-only state and suspension

21.1 Never locked out. Whatever happens to its plan or its payments, your organization keeps reading and downloading its records. A lapse never deletes anything.

21.2 When a paid plan ends — cancelled, or after failed payments — the organization moves to the Free plan, and whatever Free does not include becomes read-only (sections 6 and 11.7).

21.3 Suspension. Realizer may suspend an organization:

• for a serious or repeated breach of section 19, or another material breach of these terms;
• to stop a security threat to the service or to other organizations;
• where the law or an authority requires it.

Realizer tells your Administrators and account contact why, unless the law or the security of the service forbids it, and lifts the suspension once the cause is resolved. A suspended organization becomes read-only after a short grace period, and all sending and outbound features pause — notices, letters, invitations, portal intake and AI — while its records stay viewable and downloadable and Lab mode stays on. Where needed to stop harm, Realizer may limit or stop one activity, such as sending e-mail, at once.

22. Ending the agreement

22.1 By your organization. At any time: cancel the paid subscription (section 11.4) and close the organization (section 15.3).

22.2 By Realizer, for cause. Realizer may end the agreement with an organization that materially breaches these terms and does not remedy the breach within 30 days of a notice describing it. It may end it at once, by notice, for a breach that cannot be remedied or for a serious or repeated breach of section 19. No refund is due when the agreement ends for cause.

22.3 By Realizer, without cause. Realizer may end the agreement with an organization, or stop offering the service, by giving at least 90 days' notice. It then refunds the unused part of any period already paid.

22.4 What happens next. Section 15.5 applies. Fees already owed stay owed, and the sections that by their nature continue — among them sections 13, 14 (until the data is deleted), 15, 18, 24 (except the right to use the service) and 25 to 31 — continue.

23. Changes to the service, prices and these terms

23.1 The service. Realizer improves and changes the service over time. If a change removes a feature of your paid plan that your organization relies on in a material way, Realizer gives your Administrators at least 30 days' notice. If your organization cancels before the change takes effect, Realizer refunds the unused part of any period already paid. A change needed for security or required by law may take effect sooner.

23.2 Prices and plans. Realizer may change its prices, plans, allowances and add-ons. A change that affects an existing subscription:

• is announced by e-mail to your Administrators and account contact at least 30 days before it applies to a monthly subscription, and at least 60 days before it applies to an annual one;
• applies from your first renewal after that notice period, never to a period already paid;
• can be avoided by cancelling before that renewal.

A change that only lowers a price or adds allowance may apply at once. New prices apply at once to new purchases. Changes to the Free plan follow section 6.

23.3 These terms. Realizer may change these terms. It publishes the new version with a new "Last updated" date and, for a material change, tells your Administrators and account contact by e-mail at least 30 days before it takes effect. A change required by law or needed for security may take effect sooner. If your organization does not accept a material change, it may cancel before the change takes effect, and Realizer refunds the unused part of any period already paid. Using the service after a change takes effect means your organization accepts it.

24. Intellectual property and feedback

• Realizer and its licensors own the service, the AccessPoint software, jurisdiction packs, templates, documentation and Realizer's trademarks.
• Realizer gives your organization a non-exclusive, non-transferable right, for as long as it uses the service under these terms, to use the service and to let its members use it for its own work. No other right is granted.
• Your organization may keep and use the letters, reports, release packages and other outputs the service produced for it — including the jurisdiction content in them — for its own records and work, also after it leaves.
• Open-source components are used under their own licences, listed in AccessPoint's third-party notices.
• Realizer may use suggestions and feedback from your organization or its members freely and without obligation.
• Realizer does not name your organization as a customer, or as the source of feedback, without its permission.

25. Confidentiality

• Each party keeps the other's confidential information confidential, uses it only for this agreement and shares it only with people who need it for that purpose and are bound to keep it confidential. Customer data is your organization's confidential information. Realizer's non-public information — its security documentation, prices quoted to your organization and the terms of a written agreement — is Realizer's.
• Information is not confidential if it is or becomes public through no fault of the recipient, if the recipient already had it or develops it independently, or if the recipient receives it lawfully from someone else.
• A party may disclose confidential information where the law requires it — including a public body's access-to-information law — or a court orders it. Where the law allows, it first tells the other party so that it can object. Where your organization's access law gives a third party notice before its confidential information is released, your organization gives Realizer that notice.

26. Warranties

• Each party confirms that it has the power to enter into this agreement.
• Realizer provides the service with reasonable care and keeps the commitments in sections 13 to 15.
• Otherwise, to the extent the law allows, the service, jurisdiction content, computed outputs and AI output are provided "as is" and "as available". Realizer gives no other warranty or condition, express or implied, including of merchantable quality, fitness for a particular purpose or non-infringement, or that the service will be uninterrupted or error-free or will meet your organization's legal obligations.

27. Limitation of liability

27.1 Excluded damages. Neither party is liable to the other for indirect, incidental, special, consequential or punitive damages, or for loss of profits, revenue, savings, goodwill or opportunity, or for business interruption, however caused and even if told they were possible. Realizer is also not liable for fines, penalties or other consequences of a deadline or obligation your organization missed, or for decisions your organization made on jurisdiction content, computed outputs or AI output.

27.2 The cap. Each party's total liability under or in connection with this agreement is limited to the fees your organization paid Realizer for the service in the 12 months before the event that gave rise to the claim, or CA$100 (or the same amount in your billing currency) if that is more.

27.3 Exceptions. The limits in sections 27.1 and 27.2 do not apply to your organization's obligation to pay fees, its indemnity in section 28 or its breach of section 19, nor to liability the law does not allow to be limited, such as for fraud or wilful misconduct.

27.4 Every kind of claim. These limits apply whatever the legal basis of the claim — contract, tort (including negligence), statute or otherwise.

28. Your organization's indemnity

To the extent the law that governs your organization allows it, your organization will defend Realizer against claims by third parties — including people whose information it holds, and authorities — arising from its customer data, from its use of the service in breach of these terms or the law, or from its members' actions. It pays the amounts finally awarded, or agreed in a settlement, and reasonable legal costs.

Realizer tells your organization promptly about such a claim, lets it control the defence and any settlement, and cooperates at your organization's cost. A settlement may not make Realizer admit fault or pay anything without Realizer's consent.

29. Governing law and disputes

• These terms are governed by the laws of Nova Scotia and the federal laws of Canada that apply there, without regard to rules that would apply another law. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
• Before going to court, a party writes to the other to describe the dispute, and the two try in good faith to resolve it for 30 days.
• The courts of Nova Scotia have exclusive jurisdiction over disputes about these terms or the service, and both parties accept their jurisdiction. Either party may still ask any competent court for urgent relief to protect its confidential information or intellectual property.

30. Notices

• To your organization: by e-mail to the account contact and the Administrators, and in the service where useful. An e-mail notice is given when it is sent, unless the sender receives a delivery failure.
• To Realizer:
  • legal notices, privacy questions and requests, support, billing and changes to the account contact: support@realizer.io;
  • suspected vulnerabilities: security@realizer.io.

  A notice to Realizer is given when Realizer receives it.

• Realizer's security notices come from security@realizer.io. They never carry an attachment, and never ask for a password, a code or a sign-in through a link.

31. General terms

• Entire agreement. The documents in section 1.3 are the whole agreement about the service and replace earlier proposals and understandings about it.
• Assignment. Your organization may transfer this agreement only with Realizer's written consent, which Realizer will not unreasonably refuse; no consent is needed for a transfer to a body that succeeds your organization by law, such as after an amalgamation or reorganization. Realizer may transfer this agreement to an affiliate or to a successor to its business, with notice to your organization.
• Severability. If a term is invalid or unenforceable — including because a law that governs your organization does not allow it to accept that term — the term applies as far as it validly can, and the rest of these terms stay in force.
• No waiver. Not enforcing a term is not a waiver of it.
• Force majeure. Neither party is liable for a delay or failure caused by events beyond its reasonable control — such as natural disasters, war, terrorism, civil unrest, epidemics, government action, failures of the internet, of power or of a cloud provider's region, or attacks it could not reasonably prevent — except for an obligation to pay. The affected party tells the other and resumes as soon as it can.
• Independent parties. The parties are independent contractors. Nothing in these terms creates a partnership, agency or employment.
• No third-party beneficiaries. Only your organization and Realizer can enforce these terms.
• Survival. Terms that by their nature continue after the agreement ends continue (section 22.4).
• Language. These terms exist in English and in French, and both versions have equal force. An organization in Québec receives the French version first; it may expressly choose to be bound by the English version.
• Interpretation. Headings are for convenience. "Including" means "including without limitation".
• Electronic acceptance. Accepting these terms electronically binds your organization as a signature would.