English

Privacy Policy

Effective Date: November 14, 2026 — including the revisions of November 3 to 10, 2026 for AccessPoint 2.6.0 and Hosted AccessPoint (Section 15)

Applies to: this website, AccessPoint 2.6.0, Hosted AccessPoint, and Realizer's services around them

Publisher: Realizer Services Inc. | Contact: privacy@realizer.io

1. Introduction

This Privacy Policy describes how Realizer Services Inc. ("Realizer", "we", "us", "our") collects, uses, stores, and protects information in connection with AccessPoint, our access-to-information and privacy management solution for Microsoft 365 and Azure ("the App").

AccessPoint comes in two editions:

This policy covers these contexts:

2. Data Controller and Data Processor Roles

3. Information Collected via the Website

3.1 Information You Provide

We collect information that you voluntarily provide, including:

3.2 Automatically Collected Information

When you visit our website we use Google Analytics 4 to understand which pages are read and how visitors arrive. It records the pages you view and how long you stay, the site or search engine that referred you, your browser and device type, and an approximate location derived from your IP address; Google Analytics 4 does not log or store IP addresses. We have turned off Google signals and every advertising feature, so nothing is used for advertising and no profile is built across other websites. Visitors in the European Economic Area, the United Kingdom and Switzerland are asked before analytics cookies are set; elsewhere two first-party cookies (_ga and _ga_ followed by our property identifier) distinguish returning visitors. You can opt out on any device by opening any page of this site with ?ga=off added to the address, for example realizer.io/?ga=off, and ?ga=on turns it back on. The site sets no other tracking cookies.

Which button you pressed. Links from this site to the Hosted AccessPoint sign-up carry the name of the button pressed (cta, for example web-pricing), and links to the deployment page carry the name of the page they were on (via). These names describe our pages, not you; we count them in Google Analytics, and Section 5.9.6 describes what the sign-up keeps.

The interactive demo. The demo opens on its own page at demo.realizer.io. It uses the same Google Analytics property and the same consent choices as www.realizer.io, and counts only anonymous use of its screens — the sample, the language and the jurisdiction chosen, the steps completed and the buttons of its About panel. It never records anything typed in the demo, sets no advertising cookies and does not track you across other websites. The choice you make on its notice is kept in your browser (rz-consent), and ?ga=off opts you out on the demo too. Section 5.11 describes the demo in full.

4. Data Processed by the App (Customer Environment)

All of the following data is stored and processed exclusively within the customer's own Azure subscription and Microsoft 365 tenant. Realizer does not have access to this data.

For Hosted AccessPoint, the same descriptions apply to the data an organization keeps in it, with Section 5.9's differences: it is stored in Realizer's Azure subscription in Canada on the organization's behalf, and the Microsoft 365 parts (Section 4.5 and the Microsoft Graph permissions of Section 8.1) and repository connectors (Section 4.8) are not part of it.

4.1 User Identity Data

4.2 Case Data

4.3 Documents and Recordings

Email conversion. When an email file is converted for preview, the customer's API fetches remote images the message references (at most 25 images of up to 4 MB each, over an SSRF-hardened client with an 8-second timeout) so the rendered PDF matches what the recipient saw, then renders the page offline so that nothing contacts the network during rendering or when the PDF is later viewed. Because the images are fetched, the image hosts named in the email — including a sender's "tracking pixel", if the message carries one — see a request from the customer's App Service at conversion time, which can tell a sender that the message was opened. No other party sees the message. Attachments are extracted into child documents by default (tenant toggle Features:ExtractEmailAttachments).

4.4 Configuration Data

4.5 Records Captured from Microsoft 365

The Documents workspace lets a signed-in user add records from their own Microsoft 365 content. Every capture is initiated by the user, gated by the tenant toggle Features:M365CaptureEnabled (with separate toggles for the request and assignment workspaces), and stored as an ordinary document in the customer's Blob Storage. Which identity performs the read matters for privacy, so each source is listed with its token:

SourceWhat is capturedToken usedNotes
Outlook email ("My Email", shared/intake mailboxes)Selected messages, downloaded as .eml filesThe user's delegated token (Mail.Read, Mail.Read.Shared)Exchange mailbox permissions still apply — a user sees only mailboxes they already hold access to
Outlook calendarA date window of the user's own (or a shared) calendar, rendered as one day-grouped schedule recordThe user's delegated token (Calendars.Read, Calendars.Read.Shared)Items whose sensitivity is Private, Personal, or Confidential are excluded by default (opt-in). Attendees and location are included by default; descriptions and meeting join links are off by default. The record carries a banner noting the exclusion and that attendee names are third-party personal information subject to review
Teams chats and channel messagesThe user's own chat and channel conversations, rendered as transcriptsThe user's delegated token (Chat.Read, ChannelMessage.Read.All, Team.ReadBasic.All, Channel.ReadBasic.All)Only conversations the user is a member of
OneNotePages from the user's notebooksThe user's delegated token (Notes.Read, Notes.Read.All)
SharePoint lists and filesLists rendered as records; files copied from sites and OneDriveThe user's delegated token (Sites.Read.All, Files.Read.All)SharePoint permissions still apply
Teams meeting recordings and transcriptsRecordings of meetings the user organized, with the Teams-generated transcriptThe user's delegated token (OnlineMeetingRecording.Read.All, OnlineMeetingTranscript.Read.All, OnlineMeetings.Read)Graph lists recordings for the organizer only. The MP4 is downloaded through the user's browser into the upload queue and uploaded to the customer's API; the Teams WebVTT transcript is imported with it and is treated as authoritative — the recording is never re-transcribed. Nothing transits the publisher
Microsoft 365 Copilot interaction historyThe user's own Copilot conversations, grouped by session, rendered as transcriptsThe API's application permission (AiEnterpriseInteraction.Read.All) — there is no delegated permission for this dataRetrieval is performed server-side by the customer's API and is always scoped to the signed-in user's own Entra object ID, never tenant-wide. Requires the user to hold a Microsoft 365 Copilot licence. The permission is granted by default at setup with an opt-out

Captured records are converted to PDF in the customer's App Service, stamped with their source (for example "Email Export", "Calendar Export", "Teams Meeting Recording", "Copilot Export"), and are indistinguishable from manual uploads thereafter.

4.6 Optional Azure Services

Customers may deploy the following services within their own Azure subscription by setting a deployment parameter. Each is provisioned by the same template as the rest of AccessPoint, in the customer's resource group, and each authenticates with the App Service's managed identity only — local authentication and API keys are disabled on every account that supports it (disableLocalAuth). None of them is required; an undeployed service simply leaves its feature unavailable. Document and case content processed by them does not leave the customer's Azure environment and is never sent to Realizer.

4.6.1 Azure OpenAI (AI Assist)

4.6.2 Azure AI Search (content and semantic search)

4.6.3 Azure AI Document Intelligence (OCR)

4.6.4 Azure AI Speech (transcription of recordings)

4.6.5 Microsoft Defender for Storage (malware scanning)

4.6.6 Media processing worker (Azure Container Apps)

4.6.7 Document worker (Azure Container Apps, deployed by default)

4.6.8 Application Insights and Log Analytics (always deployed)

4.7 Privacy by Design

AccessPoint enforces role-based data access:

4.8 Records Captured through Repository Connectors

The Documents workspace can also add records from systems outside Microsoft 365 — network file shares, Hyland OnBase, OpenText Content Server, an Azure Blob container, a records database, a search server — through repository connectors that the customer's administrator registers. A connector is a service the customer operates (in their own Azure subscription or on their own premises; Realizer publishes ready-to-run connectors and a software development kit, but they run in the customer's environment) or a built-in reader inside the customer's API. Every capture is initiated by a user, gated by the tenant toggle Features:ConnectorsEnabled and by the same case-level authorization as a file upload, and stored as an ordinary document in the customer's Blob Storage.

4.9 Public Intake Portal and Online Payments (Optional)

A customer may deploy a public portal (deployPublicPortal=true, then switched on in Settings) where members of the public submit requests (and, where the customer publishes those forms, complaints or incident reports), follow their status, reply, pay fees and download responses. The portal is a separate web application in the customer's own subscription, with its own identity that can reach only the portal's own database schema and storage containers. It never contacts Realizer, and the data below is the customer's, under the customer's control.

4.10 Case Archiving: Storage Tiers, Preservation Holds and Disposition

AccessPoint can lower the storage cost of closed cases and dispose of records a records schedule no longer requires. All of it is off until the customer's administrator switches a storage policy on; the jurisdiction packs suggest one policy per case type, imported switched off.

4.11 Discovery Surveys

The privacy program can ask staff, through a discovery survey, where personal information is held and who is responsible for it.

4.12 Lab Mode and the Training Copy

AccessPoint keeps a training copy of the customer's organization (on by default; an administrator can switch it off) where staff practice on fictional training cases in Lab mode (called train mode before version 2.6.0).

4.13 AccessPoint Learning (version 2.6.0)

AccessPoint Learning — learning modules the customer writes or receives in jurisdiction packs, learning paths, checks, decisions, certificates and completion records — runs entirely in the customer's own AccessPoint; nothing about anyone's learning is sent to Realizer.

5. Data Processed by Realizer (Platform Services, Hosted AccessPoint and Realizer's Other Services)

For the Microsoft 365 edition, Realizer's Platform services process a limited set of data to support licensing, Teams notifications, jurisdiction packs, first-time setup, Teams tab routing, and software distribution. Email notifications, the in-app notification feed, documents, case records, AI prompts, and search indexes never transit Realizer. Hosted AccessPoint, where Realizer hosts all of that on the customer's behalf, is Section 5.9; Realizer's other services are Sections 5.10 to 5.12.

5.1 Licence Validation

When the App starts and periodically during use, the customer's API sends a request to Realizer's Platform API (api.realizer.io) to validate the customer's subscription. While a licence is invalid the API backs off (five minutes, doubling) rather than polling continuously.

Data transmitted:

The request authenticates with a Microsoft Entra token issued to the customer's App Service managed identity, which carries a License.Validate role on Realizer's application; the token's tenant claim identifies the customer. Where the customer's Azure subscription belongs to a different Entra tenant from its Microsoft 365 (a split-tenant installation), the token is issued instead to the installation's Microsoft 365 application — an app registration with no secret or key, which proves itself with a user-assigned managed identity in the customer's subscription — so the token still names the customer's Microsoft 365 tenant and carries nothing more. A legacy static API key remains supported as a fallback for un-migrated deployments.

Data NOT transmitted:

Purpose: To verify that the customer has an active AccessPoint subscription. The response carries the signed licence, which names the modules the subscription includes (for example AI Assist, the public portal, video and audio records, repository connectors) so the App can offer what is licensed; it holds no personal data. The response also carries the latest published AccessPoint version number (and, optionally, a link to the update template) so the App can show administrators an "Update available" notice. Realizer's Platform determines that number by reading its own release marker (get.realizer.io/public/accesspoint/latest/version.txt); the customer's API does not contact the distribution site for this.

When a subscription lapses (version 2.6.0). If the subscription has expired beyond its grace period, or Realizer revoked it, AccessPoint becomes read-only instead of stopping: no data is deleted; reading, search, reports, exports and Lab mode keep working; every change is refused; and e-mail and Teams notices, the public portal's intake and payments, repository connectors and AI Assist pause until the subscription is renewed. Nothing more is sent to Realizer.

Data stored: one licence-token record per tenant and subscription (replaced on each validation; revoked records are retained as an audit trail), the tenant's subscription status, and, on the tenant record, the self-registered API base URL, the time of the first and the latest validation, and the version the latest validation reported.

How Realizer uses these records: besides licensing, Realizer uses these existing records — no new data is collected — to understand whether a deployment is set up and up to date, and to support the customer.

Retention: Tenant ID and licence status are retained for the duration of the subscription plus 90 days after expiration for billing reconciliation. The self-registered API base URL is stored as part of the tenant's subscription record.

5.2 Teams Activity Feed Notifications

Teams activity feed notifications are optional and default to on. In the default mode, when a notification is triggered (e.g., a custodian is assigned new work), the customer's API sends a request to Realizer's Platform API, which sends the notification via Microsoft Graph on behalf of the customer's tenant. This relay exists because Graph requires that activity notifications be sent by the application that owns the Teams app manifest, and AccessPoint's Teams app is published under Realizer's multi-tenant application.

Data transmitted (default relay mode):

FieldContainsPersonal data?
tenantIdCustomer tenant GUIDNo — identifier
recipientUserIdRecipient's Entra user object IDNo — identifier
activityTypeA fixed manifest value (e.g., assignmentCreated)No
previewTextAssignment or task name and due datePotentially — free text
topicTextThe in-app notification textPotentially — free text
templateParameters.actorNameDisplay name of the staff member who triggered the notificationYes — a personal name
templateParameters.requestNumberRequest reference number (request-anchored types only)No — reference
relatedEntity, relatedRecordIdRecord type and GUID for the click-through deep linkNo — identifiers

Data NOT transmitted:

Two controls reduce or eliminate this flow:

  1. Minimize — the tenant setting Notifications:TeamsMinimalPayload (Settings → Setup → Teams Notifications → "Minimize Teams notification content") replaces previewText, topicText, and actorName with fixed placeholders ("AccessPoint Notification", "You have a new AccessPoint notification", "AccessPoint"). No free text or personal name leaves the tenant; only routing identifiers do.
  2. Direct relay — the app setting Notifications:TeamsRelayMode=Direct makes the customer's API call Graph itself with its managed identity, so nothing reaches Realizer. It requires the TeamsActivity.Send role on the customer's managed identity and a Teams manifest pointed at the customer's own application (User Guide, Step 8e).

Turning Teams notifications off in the Setup panel also eliminates the flow; email and in-app delivery of the same notifications are always in-tenant. Notifications about training cases (Section 4.12) are never sent through Teams.

Purpose: To deliver Teams activity feed notifications.

Data stored: none. The Platform logs the tenant identifier of each relayed notification for troubleshooting.

Retention: The Platform's operational logs, including the tenant identifier of each relayed notification, are kept for 90 days for troubleshooting, then automatically deleted.

5.3 API Address Discovery

When the SharePoint web part loads and no manual API-address override is configured in the tenant, it calls the Platform's api-discovery endpoint to look up the customer API address that the licence validation self-registered (Section 5.1).

Data transmitted: a Microsoft Entra bearer token issued to the signed-in user for Realizer's application — the same token the web part uses to call the customer's own API. The Platform reads only the token's tenant claim to select the record; it does not store the token or the user's identity.

Data returned: the customer's own API base URL.

Data stored: none beyond the tenant record already described in Section 5.1. The Platform logs the tenant ID and whether a URL was found.

5.4 Teams Personal Tab Routing and First-Time Setup

Teams tab routing. The AccessPoint Teams app's personal tab opens through a Platform address (api.realizer.io/apps/accesspoint/redirect-to-sp) that decides whether the tenant has AccessPoint installed and redirects the user's browser to their own SharePoint site (or to a welcome page when it does not). This design is required by how Teams desktop establishes single sign-on with SharePoint.

Finish Setup page. After a template deployment, an administrator may open the Platform's Finish Setup page (api.realizer.io/apps/accesspoint/setup) to grant the Microsoft Graph permissions the App's managed identity needs (Section 8.1), instead of running the deployment script.

SharePoint package install page (2.5.0). For a new installation an administrator may open the Platform's install page (api.realizer.io/apps/accesspoint/install) to install the App's SharePoint package into the tenant app catalog instead of uploading it by hand.

5.5 Jurisdiction Packs

Jurisdiction packs (jurisdiction-specific templates, exemptions, holidays, notification templates, and detection rules) are downloaded from the Platform on request by an administrator. Each download and each installation report authenticates as in Section 5.1.

5.6 Software Distribution

AccessPoint's installable artifacts are published to Realizer-operated endpoints. Fetching them reveals ordinary request metadata to Realizer — the artifact and version requested, the connecting IP address, and the time — and nothing else.

5.7 Summary — What Realizer Receives, and When

FlowWhenWhat Realizer receivesContains personal data?How to eliminate
Licence validationStartup and periodicallyTenant ID, API version, API base URLNoNot applicable (required for licensing)
Teams activity relayEach Teams notification (default mode)Tenant and recipient GUIDs, activity type, request number, record ID; plus title, preview text, and acting user's name unless minimizedActing user's name and free text unless minimizedMinimize toggle, Direct relay mode, or disable Teams notifications
API address discoveryWeb part load (when no override and cache expired)User's bearer token (tenant claim read; not stored)Token only, transientlyConfigure the manual AccessPoint_ApiUrl storage-entity override
Teams tab routingEach time the Teams personal tab is openedSharePoint domain, tenant ID, localeNoUse AccessPoint from SharePoint rather than the Teams tab
Finish Setup pageOnce per setup or upgrade, by an administratorTenant ID, managed identity ID, administrator's delegated token (transient)Administrator identity, transientlyUse Deploy-AccessPoint.ps1 instead
SharePoint package install pageOnce per new installation, by an administratorTenant ID, SharePoint name, version, IP address, time — never a token (it stays in the administrator's browser)NoInstall from AppSource, with Deploy-AccessPoint.ps1 -DeploySharePointApp or by hand
Jurisdiction packsOn administrator requestTenant ID, pack code, item types, installing user IDInstalling administrator's object IDDo not import packs (universal baseline is imported automatically)
Artifact downloadsDeployment and upgrade; and when an administrator chooses Update now (SharePoint package) in Settings → SetupVersion requested, IP address, timeNoUpdate the SharePoint package by hand instead of with Update now
Container image pullDocument worker replica start (default on); each media-worker or accessibility-checker scale-upImage tag, IP address, time, pull cadenceNoMirror the images into the customer's own registry
In-app helpEach time a user opens the Help panelPage requested, browser IP address and user agent, timeIP address only, as for any web siteDo not open the Help panel
Repository connector traffic (browse, search, capture, collection; attribution headers)Never — the customer's API talks to connector hosts the customer operates———
Email notificationsNever———
Account contact (Section 5.8)Once, at subscription activation, from the Microsoft commercial marketplaceThe subscription's beneficiary email address (or the purchaser's), the purchaser and beneficiary tenant IDs, and the subscription nameYes — a work email addressNot applicable; it is how we reach you about your subscription and about security. You choose which mailbox it is
Hosted AccessPoint (Section 5.9)While the organization uses itEverything the organization keeps in AccessPoint, hosted for it as its processorYesUse the Microsoft 365 edition
Hosted organization record and activity summary (Sections 5.9.3 and 5.9.4)At creation; then at most once a dayOrganization name, the creator's name and email address, region, sign-up attribution, the creator's Microsoft organization (or a hash of a personal account); counts and dates of useThe creator's name and email addressNot applicable (needed to run the service)
Hosted active-session counts (Section 5.9.4)Every five minutes, from each regionTwo counts for the whole region: sign-in sessions active in the last 5 and 15 minutes, and when they were measuredNoNot applicable (needed to run the service)
Hosted billing (Section 5.9.7)Paid plansPlan, add-ons and Stripe's subscription status; usage counts over the plan's allowanceA billing email address, held by StripeStay on the trial or the Free plan

5.8 Your Account Contact and Security Notices

What we hold, and where it comes from. When a subscription is activated through the Microsoft commercial marketplace, Microsoft's fulfilment service gives Realizer the subscription's beneficiary email address (falling back to the purchaser's), the purchaser and beneficiary tenant identifiers, and the subscription name. The address is stored on the tenant and subscription records as the organization's account contact. For Hosted AccessPoint, the account contact is the name and email address of the person who created the organization (Section 5.9.3). Apart from the members of a hosted organization, whose data Realizer hosts for the organization (Section 5.9), it is the only contact information for your organization that Realizer holds — AccessPoint's own security, privacy, and operations contacts stay inside your tenant and are never sent to Realizer (Section 5.1 stands: licence validation transmits no personal data).

What we use it for.

Why it matters that it is a role mailbox. This address is Realizer's out-of-band channel: the one that still works when your deployment is down, when it is the thing that is compromised, or when the artifacts you deploy are themselves the incident. We ask customers to make it a monitored role mailbox (for example itsecurity@yourorganization.gov) rather than an individual's address, to confirm it at activation, and to keep it current — a personal address leaves with the person, and a notice that lands in a disused inbox is the same as no notice at all.

How to update it. Contact support@realizer.io (or privacy@realizer.io) and we will change it; re-activating the subscription from the Microsoft marketplace also rewrites it. We confirm the change with the new address before using it.

What we record about the address itself. Beside the address and an optional label: whether it has been confirmed, when it was confirmed, when it was last re-confirmed, when we last sent it a confirmation or reminder, whether it looks like a role mailbox, and how the confirmation was made — either the literal marker that it was confirmed from the address itself or on the activation page, or, where marketplace sign-in is in use, the sign-in name of the person who activated the subscription. That sign-in name is the only other personal identifier in this record; it exists so that a later dispute about who set an organization's notification address has an answer.

Retention. Kept for the duration of the subscription plus 90 days, on the same schedule as the licence and subscription records (Section 9.2).

How Realizer contacts you. Security notices and advisories are sent from security@realizer.io, a shared mailbox in Realizer's own Microsoft 365 tenant, delivered through Microsoft Graph. Microsoft provides that mailbox, as it does the rest of Realizer's business systems; no separate email marketing or delivery service is involved, and no customer address is uploaded to a third-party sending platform.

Status of this section: the account contact and the marketplace data have always been held (they were missing from earlier versions of this policy — see Section 15). The advisory page (https://api.realizer.io/security/advisories), its Atom feed (https://api.realizer.io/security/advisories/feed.atom) and the security@realizer.io sending mailbox are live (confirmed 2026-10-05). The status page (https://www.realizer.io/status) is served by Realizer's website, separately from the Platform services it reports on, so it stays reachable when they are not.

5.9 Hosted AccessPoint (app.realizer.io, version 2.6.0)

Hosted AccessPoint is the same software run by Realizer: an organization signs in with a Microsoft account and uses AccessPoint in a web browser, with no Azure subscription or SharePoint of its own. It is part of version 2.6.0. Here Realizer hosts the organization's data: everything Section 4 describes as kept in the customer's own Azure subscription is kept in Realizer's, for the organization. Realizer is the organization's service provider — a data processor — for that data; the organization remains the controller (Section 2) and decides what it collects, keeps and deletes.

The service is governed by the Terms of Service for Hosted AccessPoint, published on Realizer's website beside its general Terms; wherever they concern personal information, they follow this notice.

5.9.1 Where the data is

5.9.2 Signing in and members

5.9.3 The organization's record at Realizer

When an organization is created, the service registers it with Realizer's control plane (api.realizer.io, part of the Platform):

The shared Free allowance. For each Microsoft organization (or hashed personal account) whose organizations use the Free plan, the control plane keeps that free allowance: the day its year started and, for each request or assessment one of the organizations took from it, the kind, the number, the date and which organization took it — counts and dates only, no name and no case content. An organization learns from it only how much is left, never which other organization took what. When an organization is deleted, what it took stays counted for the rest of that year, and ninety days after the deletion it no longer says which organization took it (below); the allowance itself is deleted once none of the Microsoft organization's organizations is left and its last year has ended.

The control plane issues the organization's licence and keeps its plan, add-ons, trial and billing state and the history of changes to them (for example a trial extension, with the requesting member's masked address and reason). Jurisdiction packs are read through it, with no installation record. The service itself keeps a registry entry with the organization's name, its status, the creating account's identifier (to limit how many organizations one account creates and which of them start with the trial), the creating work account's Microsoft organization (one trial per Microsoft organization, and to show the organization's name to colleagues who sign up), whether colleagues can find it, and its Who can join list.

When the organization is deleted. When the service deletes an organization — an inactive Free organization purged, an abandoned trial removed, or an organization that leaves (Section 5.9.8) — it tells the control plane the date and which of the three it was, and nothing else. The organization's subscription ends then; a lapse or the Free plan does not end it. Ninety days after the deletion Realizer deletes its licence records of the organization, its staff's notes about it and its account contact, and removes from the records it keeps for its accounts and for the service's figures everything that names the organization or its people: the name, the creator's name and address, the sign-up attribution, its Microsoft organization (or the hash of a personal account) and the masked address of the member who asked for a trial extension — and its share of a shared Free allowance stops naming it. What stays is the plan, statuses, dates, counts and amounts under an internal identifier, and one record that the deletion happened: a one-way hash of the organization's identifier, the dates and the counts. Its company is deleted from HubSpot and its deals keep only their plan, stage and value (Section 5.12); Stripe keeps its invoices and payments for Realizer's accounts, without the customer's email address and name (Section 5.9.7). If the organization's subscription becomes active again at Realizer before then, nothing is deleted until Realizer has looked at it. The admin console's audit of what Realizer's own staff did is never edited, and can still name the organization as the subject of an action (Section 5.12).

5.9.4 The activity summary (service operations data)

With its licence refresh, at most once a day, the service reports for each organization a summary that holds counts and dates only: the dates of the first real request, the first assessment, the first Lab case finished and the second member to join; the number of members; how many signed in over the last 30 days; and the last day anyone signed in. It holds no name, no address and no case content — its format has no text field, and tests fail if one is added. Realizer keeps only the latest summary for each organization and uses it to see whether organizations get started with the service, to support them and to report on the service; it is not sent to HubSpot or to any analytics service.

Active sessions. Every five minutes, over the same connection to Realizer's control plane, each region reports how many sign-in sessions were active on it in the last 5 and 15 minutes — two counts for the whole region, with no name, address or organization — so Realizer can plan maintenance for a quiet time. A session counts as active when its member did something in the service in that time; the region counts its own sessions and sends only the two numbers. Realizer keeps these counts for eight days, to show a week of activity by hour.

5.9.5 Email

5.9.6 Sign-up attribution

When someone reaches the sign-up page from the marketing demo or a campaign link, the page keeps only these keys from the link, in the browser's session storage, through sign-in: pack, lang, from, demo, steps, size and cta (the jurisdiction pack and language, where the visitor came from, the demo sample, the steps completed, the price band checked and the button pressed), the campaign tags utm_source, utm_medium, utm_campaign, utm_term, utm_content and utm_id, and gclid (an advertising click identifier). Each value is checked against a pattern and limited to 100 characters, in the browser, by the service and again by Realizer, which stores them on the organization's record (at most 2,000 characters) to learn which demos and campaigns bring customers. They are never used to build a link or a page, and Realizer does not send them to HubSpot, Google or anyone else.

5.9.7 Billing (Stripe)

The trial needs no card. Paid plans are billed by Stripe. Realizer creates the organization as a Stripe customer with the organization's name, its hosted identifier and a billing email address — that of the Administrator who first opens checkout. On Stripe's own checkout page the Administrator enters the card, the billing address and, optionally, a tax number; these go to Stripe and never reach AccessPoint or Realizer. Before the first purchase the Administrator chooses the organization's billing country, which sets the currency — Canadian dollars in Canada, US dollars in the United States, pounds in the United Kingdom, euros in the euro area, US dollars elsewhere — and the organization's subscription keeps it; the country and currency are kept with the organization's billing record. Stripe tells Realizer the subscription's status, plan, currency and add-ons. Requests and assessments beyond a plan's allowance are not billed by usage: an Administrator may buy a bundle of units, charged once to the card on file through a Stripe invoice. An Administrator manages billing in Stripe's own customer portal. Realizer's revenue reports keep Stripe's identifiers, statuses, dates and amounts only (Section 5.12). When Realizer deletes its records of a deleted organization (Section 5.9.3), it removes the customer's email address and name from Stripe and keeps the Stripe customer: its invoices, credit notes and payments are Realizer's accounting records. Stripe keeps them — each invoice with the name and billing address it was issued to, and the customer with the billing address and any tax number entered on Stripe's page — under Stripe's own retention, as Realizer's payment processor and for the tax and financial record-keeping that applies to Stripe and to Realizer.

5.9.8 The trial, the Free plan, a lapse and leaving

5.9.9 Realizer's access

Realizer operates the service and administers its Azure resources. Operations on a whole organization — export, a move to another database, purge — run only through an operator command inside the service's own environment, never through a web page or an API, and each is logged with the operator's name. The settings that send every organization's email belong to Realizer; an organization's Administrator manages everything else. Realizer uses an organization's data only to provide, secure and support the service, and does not sell or share it.

5.9.10 Who else processes it

Section 8.5 lists every service provider Realizer uses.

5.9.11 AI Assist

AI Assist (Ask AccessPoint, drafting, summaries, translation and AI suggestions such as redaction suggestions) sends the text the feature needs — for example the case's text and excerpts of its documents, including any personal information in them — to Azure OpenAI models that Realizer provisions in its subscription in Canada. Microsoft offers the current models in Canada only as Global deployments: Microsoft may process some prompts and answers in its other Azure regions worldwide.

5.10 The AccessPoint Training Lab (learn.realizer.io)

The Training Lab is Realizer's online simulation of AccessPoint, where training providers run classes. It is separate from the App: nothing passes between a customer's AccessPoint and the Lab (Section 4.12). Each provider decides what its classes collect and is the controller of its learners' data; Realizer runs the Lab as the provider's processor under the provider agreement.

5.11 The Marketing Demo (demo.realizer.io)

5.12 Realizer's Customer Records and Admin Console

Realizer's customer records (HubSpot). Realizer keeps a record of each customer organization in its customer relationship management system, HubSpot (operated by HubSpot, Inc.; Realizer's account is hosted in HubSpot's Canadian data centre in Montréal), to manage subscriptions, renewals, billing and support.

Billing and revenue records. For its revenue reports and accounting, Realizer imports Microsoft marketplace orders and revenue from Partner Center, with the customer's company name — never a person's name or email address — and, for Hosted AccessPoint, Stripe's paid invoices, credit notes and payouts, read with a read-only key, keeping Stripe's identifiers, statuses, dates and amounts — never a name, address, email or tax number. Monthly summarized journals of revenue, fees and tax are posted to Realizer's accounting system, QuickBooks Online — totals only, no personal data.

The admin console (admin.realizer.io) is Realizer's internal tool over these records. Only Realizer's own staff accounts can sign in, with multi-factor authentication; email addresses are masked in its lists; and every action is recorded in an append-only audit with who acted, what they did, why, and the record before and after. That audit is never edited: it is Realizer's evidence of what its own staff did, it holds no email address of a customer's people, and an entry about an action on an organization can still name that organization after Realizer's other records of it are deleted.

6. Data We Do NOT Collect

For the Microsoft 365 edition, Realizer does not collect, store, or have access to:

For Hosted AccessPoint, Realizer holds the organization's case data, documents and requester information on the organization's behalf (Section 5.9) and uses them only to provide, secure and support the service: none of it goes to Realizer's customer records (HubSpot), billing or accounting, or to any analytics, and the hosted pages load no analytics or advertising script. What Realizer receives for its own records about a hosted organization is the organization's record and a summary of counts and dates (Sections 5.9.3 and 5.9.4). The marketing demo's usage statistics (Section 5.11) are the only analytics Realizer runs around AccessPoint.

7. Data Storage and Security

7.1 Customer Data (App)

7.2 Platform Data (Realizer)

7.3 Website Data

8. Third-Party Data Sharing

Realizer does not sell, rent, or share customer data with third parties.

The third-party services involved in data processing are:

8.1 Microsoft Graph API

AccessPoint reads and writes Microsoft 365 data through Microsoft Graph under three sets of permissions. All Graph calls are made from the customer's tenant (by the signed-in user's browser or by the customer's API) except the Teams activity relay described in Section 5.2.

Application permissions on the customer's App Service managed identity — granted by the administrator via the Finish Setup page or Deploy-AccessPoint.ps1; used by the customer's API without a signed-in user:

PermissionPurposeWhat is read or sent
Mail.SendSend email as the mailboxes AccessPoint is configured to use: notifications, portal verification codes and security-advisory notices from the configured shared sender mailbox; correspondence and automatic acknowledgements from the mailbox chosen for the letter — the sending officer's own mailbox (the default), an intake mailbox the customer has listed, or the shared sender mailboxMessage content, from the customer's own mailbox to the recipient through the customer's own Exchange Online — never via Realizer. Grants no read access: the API cannot open, list or search any mailbox. Tenant-wide until the customer restricts it with an Exchange application access policy to a group holding the mailboxes AccessPoint sends as
User.ReadBasic.AllValidate that the shared mailbox exists; resolve notification recipientsBasic profile fields (name, email) only; no mailbox contents
TeamsAppInstallation.ReadForUser.AllCheck whether the AccessPoint Teams app is installed for a recipient before sending a Teams notificationThe recipient's installed-apps list, filtered to AccessPoint
Application.Read.AllTeams setup validation — confirm Realizer's application is consented in the tenantService principal metadata; read-only
AppCatalog.Read.AllTeams setup validation — confirm the AccessPoint Teams app is in the organization's catalogCatalog metadata; read-only
AiEnterpriseInteraction.Read.All"Add from Microsoft 365 → Copilot" capture (Section 4.5)The signed-in user's own Copilot interaction history — the API always scopes the call to that user's object ID. Granted by default; opt out at setup (-DisableCopilotCapture, or the Finish Setup checkbox)
User.Read.AllDirectory reconciliation (nightly sweep for disabled or deleted user accounts)Account status (accountEnabled) of AccessPoint's own users and the ids in the deleted-users recycle bin — never mail, files or message content. Granted by default; opt out at setup (-DisableDirectoryReconciliation, or the Finish Setup checkbox)
GroupMember.Read.AllGroup-based roles — resolve whether a signing-in AccessPoint user belongs to an Entra group an administrator bound to a roleMembership of AccessPoint's own users in the specific groups bound to AccessPoint roles only (checkMemberGroups, together with User.ReadBasic.All) — never the tenant's group directory, other groups' membership lists, mail, files or message content. Granted by default under the same opt-out as User.Read.All
TeamsActivity.Send (optional)Only when the customer adopts the Direct relay mode (Section 5.2)Teams activity notifications sent by the customer's own identity

The managed identity also holds the non-Graph License.Validate role on Realizer's application (Section 5.1). On a split-tenant installation (Section 5.1) these permissions and that role are held instead by the installation's Microsoft 365 application in the customer's Microsoft 365 tenant, which signs in with no secret through a user-assigned managed identity in the customer's subscription; the permissions and their purposes are the same.

Delegated permissions requested by the SharePoint package — approved by a SharePoint administrator; exercised in the signed-in user's browser with the user's own identity, so the user can never read more than they already can in Microsoft 365:

PermissionPurpose
User.Read.AllPeople picker, user search and resolution
Sites.Read.AllSharePoint site browsing and Lists capture
Files.Read.AllFile browsing and capture from sites and OneDrive
Mail.ReadEmail capture and preview from the user's own mailbox
Mail.Read.SharedEmail capture from shared and intake mailboxes the user already has access to
Calendars.ReadCalendar capture (Section 4.5)
Calendars.Read.SharedCalendar capture from shared mailboxes
Chat.ReadTeams chat capture
ChannelMessage.Read.AllTeams channel message capture
Team.ReadBasic.All, Channel.ReadBasic.AllListing the user's teams and channels for capture
Notes.Read, Notes.Read.AllOneNote capture
OnlineMeetingRecording.Read.AllListing and downloading recordings of meetings the user organized (Section 4.5)
OnlineMeetingTranscript.Read.AllDownloading the Teams transcript of those meetings
OnlineMeetings.ReadReading the meeting metadata needed to list recordings
GroupMember.Read.AllThe group picker an administrator uses to bind an Entra group to an AccessPoint role
access_as_user (Realizer's application)The token audience for calls to the customer's own API and to the API address discovery endpoint (Section 5.3); not a Graph permission

Realizer's multi-tenant application — consented by the customer's administrator; operated by Realizer for the Teams relay only:

PermissionPurpose
TeamsActivity.SendSend Teams activity feed notifications on behalf of AccessPoint (Section 5.2). Cannot read Teams messages, channels, or any other tenant data
AppCatalog.Read.AllResolve the Teams app's catalog identifier so the notification carries the AccessPoint icon; read-only
User.ReadBasic sign-in scope

8.2 Realizer Platform API

Used to validate the subscription, relay Teams notifications, discover the API address, route the Teams tab, finish setup, serve the SharePoint package install page, and download jurisdiction packs — each described in Section 5 with the exact data transmitted — and, for Hosted AccessPoint, as the control plane that registers organizations, issues their licences and keeps their plans and billing state (Section 5.9.3).

8.3 Microsoft Azure (optional services)

Azure OpenAI, Azure AI Search, Azure AI Document Intelligence, Azure AI Speech, Microsoft Defender for Storage, Azure Container Apps, and Application Insights — when the customer chooses to deploy them, these are Azure resources inside the customer's own Azure subscription under the customer's agreement with Microsoft; document and case content processed by them does not leave the customer's Azure environment and is never sent to Realizer (see Section 4.6).

8.4 Other

For the Microsoft 365 edition, no data is transmitted to any other third-party service, with one customer-chosen exception: when a customer switches on online payments, the payment provider it contracts receives the payment details in Section 4.9. Document conversion, redaction and PDF rendering run entirely inside the customer's Azure subscription: AccessPoint's own document engine in the App Service, and the document worker Container App (queue in, blob out, no network access needed for the content) — no document content is sent externally. The document viewer is served with all of its assets from the customer's own App Service; nothing is loaded from a third-party CDN. The face-detection and region-tracking models used for video redaction ship inside the application and call no external service. The only other outbound connections the App makes are the email image fetches described in Section 4.3, the artifact and image downloads described in Section 5.6, and the user's browser loading Realizer's help pages (Section 5.6).

8.5 Realizer's Service Providers (Subprocessors)

For Hosted AccessPoint, the Training Lab, the Platform and Realizer's own records, Realizer uses these service providers:

ProviderForWhat they processWhere
Microsoft (Azure, Entra ID, Azure Communication Services, Azure Front Door, Application Insights, Azure Container Apps, Microsoft Defender for Storage, Azure AI Document Intelligence, Azure AI Search, Azure AI Speech, Azure OpenAI)Hosting Hosted AccessPoint, its entry (app.realizer.io), the Training Lab, the Platform and the demo; Microsoft sign-in; email; Hosted AccessPoint's AI services; the Lab's AI draftingAll of Hosted AccessPoint's data and the Lab's; sign-ins; email recipients and content; the text an AI feature sendsCanada Central, with Hosted AccessPoint's backups and stored files geo-replicated to Canada East (Communication Services data stored in Canada; the Lab's AI drafting in Canada East). Hosted AccessPoint's Azure OpenAI models are Global deployments: for an organization whose Administrator allowed them, Microsoft may process prompts and answers in any of its Azure regions (Section 5.9.11). Entra ID sign-in and Front Door are global services
Microsoft 365 (Realizer's own tenant)Security notices and correspondence (Section 5.8)The account contact's address and the notices sent to itCanada
StripeBilling of Hosted AccessPoint's paid plans (Section 5.9.7)The organization's name, its hosted identifier and a billing email address (the address and name are removed 90 days after the organization is deleted; its invoices and payments stay with Stripe under Stripe's retention); the card, billing address and tax number entered on Stripe's page; the billing currency; bundles boughtStripe's own jurisdictions
HubSpot, Inc.Realizer's customer records (Section 5.12)Companies and deals; a proven organization address for Microsoft marketplace customers onlyHubSpot's Canadian data centre (Montréal)
Intuit (QuickBooks Online)Realizer's accounting (Section 5.12)Monthly summarized journals — totals, no personal dataIntuit's own
Google (Google Analytics)The marketing demo's usage statistics on direct visits (Section 5.11)Fixed event keys and Google's cookies on demo.realizer.io, with the request details any web request carriesGoogle's own

The customer's own deployment of the Microsoft 365 edition uses none of them except Microsoft, under the customer's own agreement (Sections 4.6 and 8.3).

9. Data Retention and Deletion

9.1 Customer Data

Data retention is fully controlled by the customer:

9.2 Platform Data

9.3 Website Data

Contact form submissions and demo requests are retained for the duration of the business relationship. You may request deletion at any time. Nothing is kept from a tool's results email except that hash, for 24 hours (Section 3.1).

10. Data Subject Rights

10.1 For End Users of the App

Requests related to personal data processed within AccessPoint (access, correction, deletion, portability) should be directed to the customer organization that deployed AccessPoint, as they are the data controller.

10.2 For Customer Organizations

As the data controller, customers can:

10.3 For Website Visitors and Platform Data

You have the right to:

To exercise these rights, or to request access to, correction of, or deletion of the limited data Realizer processes (tenant ID, licence records, subscription and account contact addresses, pack installation records), contact privacy@realizer.io.

If your work address is the account contact for a subscription (Section 5.8) and you would rather it were not, tell us and we will replace it with the address your organization nominates — we will ask the organization for a replacement first, because a subscription with no reachable contact cannot be told about a security incident.

10.4 For Hosted AccessPoint, the Training Lab and the Demo

11. International Data Transfers

12. Children's Privacy

AccessPoint is an enterprise business application. It is not directed at children and does not knowingly collect personal data from children under the age of 16. The same holds for the Training Lab, which is for professional training, and for the demo.

13. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated through:

14. Contact

For questions about this Privacy Policy or AccessPoint's data practices:

Realizer Services Inc. Email: privacy@realizer.io Website: realizer.io/privacy

15. Change History