Legal

GlacierPoint Snapshot Privacy Policy

Version 2026-11-03, effective November 3, 2026.

The short version

  • GlacierPoint Snapshot backs up the configuration of Microsoft 365 tenants, never mail, files, sites or chats; configuration can still name people, such as administrators and mail contacts. The Windows app on your computer does the work; we hold no password, token, secret or certificate for any tenant.
  • You choose per tenant where backups are kept. Hosted backups are encrypted on your computer, stored encrypted, and decrypted on our server only while the service works on them (checking, comparing, showing, exporting, preparing a restore, change alerts). Backups in a local vault stay on your computer; the portal keeps codes and counts.
  • The portal sets one cookie to keep you signed in. No analytics, no advertising, nothing loaded from other companies.
  • We do not sell personal data and do not train artificial intelligence on your data.

1. Who we are

1.1 GlacierPoint Snapshot is a configuration backup and restore service for organizations that use Microsoft 365, provided by GlacierPoint Technologies LLC, 1043 S Roselle Rd #1053, Schaumburg, IL 60193, United States ("we", "us"). Questions about this policy or your personal data: privacy@glacierpointtech.com.

1.2 The service is a website and web portal at snapshot.glacierpointtech.com and a Windows program, the app, that our customers run on their own computers to back up, compare and restore the configuration of their Microsoft 365 tenants. This policy covers visitors of the website, people who sign up, are invited to a workspace or use the portal and the app, people who write to us, and (in section 5) people named in the configuration our customers back up.

2. Our two roles

2.1 Controller. We decide how and why we use the personal data needed to run customer accounts and workspaces, bill, answer enquiries and support requests, send the emails of the service, and keep the website and portal secure. This policy covers that data.

2.2 Processor. Backups, restore plans and restore results, and the records the portal keeps about a customer's tenants, are processed on behalf of the customer, on its instructions under our Terms of Service and, where the customer has signed one with us, our Data Processing Addendum (DPA), whose Schedule 1 describes this processing for GlacierPoint Snapshot; the DPA is available on request. The customer decides which tenants to back up, where the backups are kept and for how long. If your name or address appears in a customer's backup (for example as an administrator or a mailbox owner in its tenant), please contact that organization first; we will help it respond. Section 5 describes this data so customers and their staff can see what it contains.

3. What we collect as controller

DataSourcePurposeLegal basis (GDPR / UK GDPR)Retention
Account: email address, name (for an invited member, the name the owner typed), workspace, role, when and how the account was created (sign-up, invitation or our administrator), last sign-in time; at sign-up the organization nameYou, or the workspace owner who invited youProvide accounts and workspacesContract; for a member invited by an owner, until that member accepts the invitation, the legitimate interests of the workspace owner and of us in facilitating authorized multi-user access to the serviceWhile the account exists; deleted when the last workspace it belongs to is closed, or on request; we carry out a request to close a workspace within 30 days, and once it is carried out the deletion is immediate
Password hash (scrypt), only if our administrator set a password at your requestYouSign-inContractUntil changed or the account is deleted
Sign-in and sign-up codes, sessions and invitation links, stored only as hashesGenerated by usSign-in, joining a workspaceContract; legitimate interests (security)Codes 10 minutes; sessions 12 hours; invitations 14 days
Invitations: the invited address, the role and name the owner gave, who invitedThe workspace ownerInvite a memberLegitimate interests of the workspace owner and of us in facilitating authorized multi-user access to the serviceUntil accepted, declined or canceled, and at most 14 days
IP addressesYour browser or the appPrevent abuse and password guessing; show the member approving a new app where its request came fromLegitimate interests (security)Throttle counters in memory only; a pending app connection request keeps the address until it expires (10 to 30 minutes); web server logs, below
Connected apps: computer name, operating system, app version, the name given, who approved it and when, last contactThe app, the member approving itShow the workspace which computers are connected; authenticate themContract; legitimate interests (security)While the workspace exists; a revoked app is removed 400 days after it was revoked
Tenant records: tenant ID, initial domain, display name, where backups are kept, retention setting, which app registered it, result of the last run, the schedule the app runs and the end date of its certificate for scheduled backupsThe app, the ownerProvide the service (processor data, listed here for completeness)ContractWhile the tenant is registered
Notification choices per memberYouSend the emails you choseContractWhile the membership exists
Activity log: time, the member's email address or the app's name, action, a short detail, the tenant; never a setting value and never an IP addressYour use of the portal and the appShow the workspace what happened; security and supportLegitimate interests (security, accountability)The most recent 500 events per workspace, and none older than 400 days
Terms acceptance and tenant authorization records: the version of the Terms accepted, the time, the account, the workspace and the IP address of the acceptance; for a purchase, a record of its own with the exact text shown at checkout or at activation, the versions of the Terms and of the MSP Addendum and their links, the ticking of the box, the time, the account, the IP address, the organization and the authority asserted; for a tenant, who confirmed that the workspace may connect it, when, how and through which appYou, when you accept the terms, buy a plan or confirm a tenantEvidence of the agreement and of the authorization to back up and change a tenantContract; legitimate interests (evidence of the agreement)An acceptance is kept on the membership and removed when the member leaves, the account is deleted or the workspace is closed; its entry in the activity log follows that log's limits. A purchase acceptance is kept under the same rule as a Terms acceptance. A tenant's confirmation is kept while the tenant is registered.
Plans and billing: plan, start and end dates, allowance counts per tenant, invoices; payment by card, bank debit, Link or bank transfer, and whether the plan renews automaticallyYou; usSell and account for plansContract; legal obligation (tax records)A tenant's plan row is removed 400 days after the tenant is deleted; invoices and payment records 7 years, as tax law requires
Billing, for plans paid online: the Stripe customer, subscription and invoice identifiers, the amounts and their status, and the billing name and address you entered; never a card number or a bank account number, which Stripe holdsYou, through Stripe; usCharge for plans, renew them when you chose it, send invoices and receipts, and keep tax recordsContract; legal obligation (tax records)As the plans and billing row above: a tenant's plan row 400 days after the tenant is deleted; invoices as stated there
Sales enquiries and invoice requests: what you write to us; a request from the portal also carries the workspace, the owner, the tenant, the plan and its priceEmail; the portal's Request an invoiceReply to you and invoiceLegitimate interests; steps before a contractNot stored in the portal; each message kept in our mailbox for 24 months after we receive it (our replies, 24 months after we send them); an entry in the activity log
Support requests: form, subject, message, your email address and role, workspace, the tenant you name, app and portal versions, the computer it was sent from, and the app's diagnostics if you attach themThe portal's Support page or the appAnswer your requestContractNot stored in the portal; each message kept in our mailbox for 24 months after we receive it (our replies, 24 months after we send them); an entry in the activity log with the form and the reference only
Emails we send you: codes, invitations, welcome and renewal mails, notifications about scheduled backups and changes, certificate warnings, copies of your support requestsGenerated by usDeliver the serviceContract; legitimate interestsSent through our Microsoft 365 mail service, which keeps no copy of a sent message; Microsoft keeps delivery records (sender, recipient, subject, time and delivery status) for 90 days
Web server logs: IP address, time, method, the page path without its query, status, the referring site without its path, the browser's identification string and timingsYour browser or the appSecurity and troubleshooting; weekly counts of visits and pages viewed (with referring sites, browser families and countries) that identify no one and are kept 1 yearLegitimate interests14 days, rotated daily; the system journal, which holds what the portal and its jobs report and no request lines, is kept 90 days

We do not ask for or use special categories of personal data.

4. Cookies and browser storage

The portal sets one strictly necessary cookie, cfgbackup_session, when you sign in. It holds a random session identifier, lasts 12 hours, is marked HttpOnly and SameSite=Lax, and is Secure over HTTPS. The sign-in, sign-up and invitation pages keep your progress (including the email address and organization you typed) in your browser's session storage, which is cleared when you close the tab; the portal also keeps there the items you selected for a restore and whether the search panel is open, and keeps your display preferences for change views in local storage.

We use no advertising, analytics or tracking cookies, and the website and portal load no scripts, styles or fonts from third parties. Our emails show the product's mark, loaded from our server when your mail program displays pictures; that request is logged like any other web request, carries no identifier of you, and is not used to tell whether you opened a mail. The footer of every page of the website and the portal links to this section.

5. Backups (processed for customers)

5.1 How they travel. For a hosted tenant the app compresses each backup and encrypts it on the customer's computer (AES-256-GCM with a new key for each upload, wrapped with the portal's RSA-3072 key) and uploads it over TLS. Our server decrypts it, checks it against a fixed format that rejects unexpected fields, computes its fingerprints, compares it with the previous backup, and stores it encrypted with AES-256-GCM under a key kept outside the database. The server decrypts a hosted backup again when a member opens, searches, compares or exports it, when a restore is prepared or checked against it, when it computes the changes for an email alert, and when it re-encrypts a backup for one of the customer's connected apps, which an owner must allow. For a tenant kept in a local vault, the backup never leaves the customer's computer.

5.2 What a backup contains. Configuration: settings, policies, rules and their names and descriptions. Where a setting refers to people, a backup holds what Microsoft returns for that setting, which can include:

AreaPersonal data that the configuration can contain
Entra IDObject identifiers and names of users, groups and applications included in or excluded from policies; who holds which administrator role, including eligible and time-limited assignments; members of administrative units and access package policies where the settings name them
Exchange OnlineNames and addresses of shared, room and equipment mailboxes and their settings; who has Full Access to them; mailboxes that forward mail and the addresses they forward to; mail contacts, which are names and external addresses of people outside the organization; accounts whose mailbox access is not audited; addresses and senders named in mail flow rules; holders of management roles
Defender and PurviewAddresses and domains in allow and block lists; people and groups a policy applies to or names; members of role groups
Intune, Teams, SharePoint, Power Platform and Microsoft 365 settingsGroups that policies are assigned to; role assignments; administrators or contacts named in tenant settings
Every hosted backupThe account that ran it as the app records it (for a backup a person starts, that person's user principal name), and the computer and app that sent it
Restore plans and resultsWho prepared and who confirmed a restore and the account that signed in for it; the names and results of the restored items, stored encrypted

5.3 What a backup does not contain.

  • No email messages, attachments, files, documents, site contents or chats: the app reads configuration only. Sites.Read.All is used to find the address of the SharePoint admin center, not to read sites.
  • No passwords or client secrets: Microsoft's interfaces do not return them, and the app does not ask for them.
  • No Microsoft sign-in tokens: they stay in the app's memory on the customer's computer and are discarded when it signs out or closes.
  • No usage telemetry from the app. Besides backups, the app sends the portal only what section 5.4 lists.

5.4 What the app sends besides backups. A connection request (computer name, operating system, app version); the registration of a tenant (tenant ID, initial domain, display name, where its backups are kept); the schedule it runs and the end date of its certificate for scheduled backups; failed runs (an error code, and for a hosted tenant the error message); restore results (for a restore prepared in the portal, each item's outcome and the account that signed in; for a restore from a local vault, counts only); and support requests, with diagnostics only when attached.

5.5 Local vault. For each backup in a local vault the portal keeps when it ran, how it ran (by a person or on a schedule), whether it succeeded, the number of items per setting type and how many were added, changed or removed, the codes of any errors and the size. Beside that it keeps the tenant's name and domain and the name of the computer and app that ran the backup. It never receives who ran the backup, the names of items, the messages of Microsoft's services or any setting.

5.6 On the customer's computer. Local vault backups, restore journals (the state before and after each restored item, with the account that signed in) and restore notes are kept encrypted with the key of the tenant's local vault and never sent to us. Run logs and diagnostics stay on the computer unless a member attaches them to a Technical Support request; the portal then removes the parts the app marks as local only (which may hold names from the tenant) and anything shaped like a token before mailing the request.

6. Who we share data with

We do not sell personal data, and we do not share it for advertising. We share it only with these providers, our professional advisers under confidentiality, and where the law requires. The first three process the backups we hold for customers as our subprocessors (listed in Schedule 1 of the DPA); Stripe does not receive them.

ProviderPurposeLocation
GreenCloudVPSHosts the portal server, its database and the encrypted hosted backupsChicago, Illinois, United States
Microsoft (Exchange Online, Microsoft 365)Relays our emails and holds the mailbox where sales enquiries and support requests arriveUnited States
Backblaze (B2 cloud storage)Holds encrypted copies of the server's nightly archivesUnited States (US East)
Stripe, Inc.Processes payments by card, bank debit and Link, renewals and invoices; holds the payment details and the billing name and address you enter. Stripe acts as an independent controller of the payment data it collects, under its own privacy policyUnited States

Plans are paid online through Stripe, or by invoice, on request, and bank transfer. We store no card or bank account number: Stripe holds them. Our TLS certificates come from Let's Encrypt, which learns the portal's host name and nothing about you. When a customer backs up or restores a tenant, the app talks to the customer's own Microsoft tenant and may install Microsoft's PowerShell modules from the PowerShell Gallery; those are the customer's relationships with Microsoft, not our subprocessing. When the list changes, we update it in this policy and email the owners of each workspace at least 30 days before a new subprocessor starts processing.

7. International transfers

We are based in the United States and our systems are hosted in the United States. We offer the service to organizations in the United States and do not currently offer it to organizations in the European Economic Area, the United Kingdom or Switzerland. If you write to us or visit the website from one of those places, the data you give us is transferred to and kept in the United States.

8. How we protect data

  • No access to tenants: we hold no password, token, client secret or certificate for any tenant. Scheduled backups use an app registration the customer owns, with a certificate whose private key Windows creates on the customer's computer and does not let leave it.
  • TLS 1.2 or 1.3 for the website and portal, with HSTS, a strict Content-Security-Policy and no framing by other sites; hosted backups are encrypted on the customer's computer before upload.
  • Encryption at rest: hosted backups are stored encrypted (AES-256-GCM), and so is every value in the portal's database (accounts, tenant records, summaries, restore plans, the activity log, sessions, codes and invitations), sealed with AES-256-GCM under a data key that is kept in a file outside the data folder. The keys that open uploads, sign licenses and restore plans and encrypt hosted backups, which sit in files beside the database, are sealed with the same data key. A copy of the database or of the data folder is therefore unreadable without that key. What stays readable is the name of each kind of record, how many there are and how large, the time each was first written, and the names, sizes and times of the folders and files of the encrypted hosted backups, which are made of workspace, tenant and backup identifiers. The data key is kept on the server so that the service can use the data, so this protects copies, not a running server.
  • The settings catalog that tells the app what to read and write is signed with a key kept offline, never on our server; the app uses only a catalog with that signature and checks each operation against fixed rules of its own. A restore prepared in the portal carries saved settings as data, not commands.
  • Sign-in codes are six digits, valid 10 minutes and usable once; codes and sessions are stored only as hashes, passwords as scrypt hashes; sign-in, sign-up, code, invitation and support requests are rate-limited, and repeated wrong passwords lock password sign-in of an account for 15 minutes.
  • A new app is connected only after a member approves its one-time code, seeing its computer name, the time and the address it came from; apps authenticate with tokens stored only as hashes, and an owner can revoke them. Connected apps may open earlier hosted backups only when an owner allows it.
  • The server accepts SSH with keys only, blocks repeated SSH failures, allows only web and SSH traffic and installs security updates automatically; the service runs as an unprivileged, sandboxed user; data files are readable only by that user. The server is monitored every five minutes.
  • Nightly backups of the server are encrypted to a key that is never on the server before they are written.
  • Workspace activity is logged and shown to the workspace.
  • If a breach of security affects personal data we hold, we tell the affected customers without undue delay so that they can meet their own duties, and we notify the people affected and the authorities where the law requires it, including under the Illinois Personal Information Protection Act. For the backups we process for a customer, we notify that customer without undue delay, as a signed DPA says.

We do not claim any security certification.

9. Retention and deletion

  • Hosted backups and local vault summaries are deleted by a daily job once they are older than the tenant's retention period: 365 days unless an owner sets 7 to 3,650 days. The newest complete backup of each tenant is kept while the tenant is registered. Backups older than the plan's history (30 days for the Preview and the One-time plan, 90 days for Essentials, one year for Professional and MSP) are hidden from view, not deleted. An owner can delete a backup, or a tenant with all its backups and restore plans, at any time. Hosted backups of a tenant whose plan has ended are kept for 90 days after the end and then deleted; the workspace's owners are emailed 30 and 7 days before, and a plan that runs again stops the deletion. For a Preview that never had a paid plan, the 90 days count from 30 days after its newest hosted backup. Backups in a local vault stay on the customer's computer.
  • Restore plans and their results are removed 400 days after their last change, by the same daily job, or when the tenant is deleted. Activity records older than 400 days and revoked apps 400 days after their revocation are removed the same way.
  • Account and workspace data is kept while the workspace exists and deleted when a request to close the workspace is carried out, which we do within 30 days of the owner's request, except records we must keep by law.
  • Backups of our server run nightly. The server keeps the newest archive of each of the last 14 days and of each of the last 8 weeks, so deleted data can remain in them for up to about eight weeks. Each archive is encrypted with a key that is not on the server, and an encrypted copy of it is also kept at Backblaze, which the server only adds to and never deletes from. Backblaze keeps each copy for about five months: a copy is hidden 120 days after it was uploaded and deleted 30 days later, so deleted data leaves the copies at Backblaze within about 150 days after the last archive that held it was uploaded. Backups are used only for recovery.
  • Which deletion comes first. When more than one of these rules applies, the earliest deletion wins: an owner's deletion of a backup or a tenant and the closing of a workspace take effect at once; the 90 days after a plan ends apply to hosted backups only, the newest included; local vault summaries follow the tenant's retention period whether or not a plan runs.

10. Our access and support requests

We have no sign-in to a customer workspace. The people who operate the service can reach the server, its database and the encrypted hosted backups; they do so only to run, secure, back up and repair the service, to answer a request the customer sends, or where the law requires. They manage the service from an operator console that can be reached only through an SSH tunnel to the server, which shows account, workspace, tenant and plan details and activity records, and never the contents of a backup or anything in a tenant; every action taken in it is written to an audit log, which is kept for 400 days. Support requests are mailed to us and not stored in the portal; the workspace's activity log records that one was sent, with its form and reference.

11. Your rights

11.1 Everyone. Write to privacy@glacierpointtech.com to ask what personal data we hold about you, to have it corrected or deleted, or to receive a copy of it. We may need to verify your identity and will reply within the time the law allows. The portal does not let you delete or export your account yourself: send the request by email and we do it for you. For data in a customer's backups, we pass your request to that customer, whose processor we are.

11.2 European Economic Area and United Kingdom. Under the GDPR and the UK GDPR you have the right to access your personal data, to have it corrected or erased, to restrict or object to our processing of it, including processing based on legitimate interests, to receive the data you gave us in a portable form, and to withdraw a consent at any time without affecting what was done before. You may complain to the supervisory authority of your country or, in the United Kingdom, to the Information Commissioner's Office.

11.3 California. If you are a California resident, the California Consumer Privacy Act, as amended by the California Privacy Rights Act, gives you rights to know, delete and correct personal information and to opt out of its sale or sharing, where that law applies to a business. We do not sell or share personal information (section 12). We are below the revenue and volume thresholds at which that law applies to a business; we watch them and will put the California-specific notices and request channels in place if we reach one. Until then we answer requests from California residents under section 11.1.

11.4 Illinois. The Illinois Personal Information Protection Act governs how we notify a breach of security (section 8). We do not collect biometric identifiers or biometric information.

12. No sale, no advertising, no AI training, no automated decisions

We do not sell or rent personal data or share it for cross-context behavioral advertising. We do not use customer backups to train artificial intelligence models. The service compares and restores configuration by fixed rules; we make no decisions about individuals that have legal or similarly significant effects.

13. Children

The service is for organizations and is not directed at children under 16. We do not knowingly collect their personal data.

14. Changes

We will post changes here with a new effective date, and tell workspace owners by email of material changes before they apply.

15. Contact

GlacierPoint Technologies LLC, 1043 S Roselle Rd #1053, Schaumburg, IL 60193, United States. Privacy: privacy@glacierpointtech.com. Support: support@glacierpointtech.com.