LEGAL
Privacy information.
Local MayaUPS stores monitoring records on your server. Connecting optional MayaUPS Cloud shares a defined set of readings and summaries. Its mail relay also receives alarm information and recipient addresses when used.
Monitoring data
MayaUPS runs on your server and retains the full detailed monitoring history locally. The optional MayaUPS Cloud connection sends device identity, reachability, conditions, eight readings, daily summaries and battery-health results, along with observation and software information. The MayaUPS Cloud page describes the data sent in detail. Known battery-install dates and the last transfer reason are included where supplied.
| Data set | Location or path | What it contains |
|---|---|---|
| Local records | Site MayaUPS server | Detailed history, other readings, energy, local service notes, audit, local users and shutdown settings. Equipment credentials and agent certificates remain on site. |
| Shared monitoring | Site to MayaUPS Cloud, when connected | Equipment identity, reachability, conditions, eight readings, daily summaries and battery health. Software and reporting information, known battery dates, transfer reason where supplied and group reserves are also included. |
| Published service reports | Portal; copies retrievable by the site | Approved reports and PDFs published for the relevant customer. These are separate from local service notes. |
| E-mail relay | Site to relay service, when used | Alarm text, device, condition, severity and the addresses of that alarm’s recipients. The complete recipient address book is not uploaded. |
| Local SMTP | Site to your mail server | An alternative route explicitly selected by the administrator for alarm e-mails. |
Shared data includes equipment identifiers. The relay handles the relevant recipients’ addresses. Review the detailed field list before enabling the connection.
Data that remains local
SNMP and device credentials, shutdown policies and targets, agent certificates, local users, the other local readings, component-level alarms, energy data, local reports and the local audit remain on site. Published technician reports and their archived PDFs are separate portal records.
Alarm e-mail relay
When a site connection is configured, alarm e-mails use the portal’s mail server by default. The alarm text, device, condition, severity and that alarm’s recipient addresses leave the site for delivery. You can explicitly choose your own SMTP server instead. The full recipient address book is not uploaded.
Portal retention and access
The optional portal is hosted in Beauharnois, Quebec. Raw readings are kept for 31 days, daily summaries for two years, battery-health results for six years and receipt records for 90 days. Your service provider opens access per contact; each contact sees only their own organisation’s data and published service reports.
Published service reports, their PDFs and photos have no automatic age-based deletion. The supplied backup script removes database copies older than 14 days; they can contain records older than the windows above. Confirm the retention actually configured on the server.
| Category | Window | Location |
|---|---|---|
| History displayed on the equipment page | 30 days | MayaUPS Cloud portal |
| Reading samples | 31 days | MayaUPS Cloud storage |
| Daily summaries | 2 years | MayaUPS Cloud storage |
| Battery-health results | 6 years | MayaUPS Cloud storage |
| Data receipt records | 90 days | MayaUPS Cloud storage |
| Published service reports, their PDFs and photos | No automatic age-based deletion | MayaUPS Cloud storage |
| Portal backups | The supplied script removes database copies older than 14 days; copies can retain records beyond the windows above. Confirm deployed retention. | MayaUPS Cloud server |
| Detailed local history | Local retention settings | Your MayaUPS server |
The 30-day display is not the retention period for every category. MayaUPS Cloud windows apply to the categories listed. Plan local retention, backups and service records separately.
Public website
On the contact page, the optional project brief is assembled in your browser and is not sent to this website. Email links open your email app, where you review and send the message. This website has no account registration or enquiry form, sets no cookies on its pages and runs no analytics or advertising scripts. It is served through Cloudflare, which may receive network error reports from your browser.
Supplier
MayaUPS is published by 9326227 Canada Inc.
Registered office: 5 Rue Goodfellow, Delson QC J5B 1V2.
Enquiries: info@mayaups.com.
Service providers
This website is served through Cloudflare, which may receive network error reports from your browser. The MayaUPS Cloud service (connect.mayaups.com) runs on an OVHcloud server in Beauharnois, Quebec. Relayed alarm e-mails and portal e-mails also pass through a mail provider.
Browser alerts, when enabled and subscribed to, use the browser vendor’s push service.
Person in charge of personal information
9326227 Canada Inc. is responsible for the personal information processed by this website and by MayaUPS Cloud. The person in charge of the protection of personal information is Christian Barkley. Write to info@mayaups.com to ask for access to or correction of your personal information, or to make a complaint. Last updated: 16 October 2026.