Service Level Agreement

Effective 2026-04-28

This SLA defines the service commitments Indoor Informatics Oy ("we") makes to GymPlus customers. It is incorporated by reference into the GymPlus Standard Customer Contract.

Contents

  1. Scope and definitions
  2. Service commitments
  3. Measurement methodology
  4. Maintenance windows
  5. Exclusions
  6. Service credits
  7. Reporting
  8. Limitations
  9. Changes to this SLA

1. Scope and definitions

This SLA applies to the GymPlus SaaS platform and the edge devices we deploy at customer premises.

TermDefinition
PremiseA single customer site with at least one Indoor Informatics edge device installed and provisioned for production use.
Service hoursMon to Fri 09:00 to 17:00 EET (Helsinki time), excluding Finnish public holidays. SLAs that reference service hours pause outside this window.
Premise uptimeThe percentage of premise operating hours during a calendar month in which the edge device sent at least one valid image to the cloud per 10-minute window.
Premise operating hoursHours the gym is open to members. If unknown, default is 06:00 to 24:00 local time.
Calendar monthThe measurement period for all uptime commitments.
First responseThe first human reply from our team to a support request, sent during service hours.

2. Service commitments

2.1 Premise uptime

MetricCommitmentMeasurement
Per-premise uptimeAt least 95% per calendar monthPer Section 3.1

Our internal target is 99% per premise. The 95% figure is the contractual floor below which service credits may be claimed.

2.2 GymPlus dashboard and API

MetricCommitmentMeasurement
Dashboard availabilityAt least 99% per calendar monthPer Section 3.2
Customer-facing API availabilityAt least 99% per calendar monthPer Section 3.2

2.3 Support response

We commit to first-response targets only. Resolution is best-effort and depends on root cause and customer cooperation.

SeverityDescriptionFirst response (service hours)Update cadence
P1, CriticalService down for multiple premises or all customers1 hourEvery 2 hours until mitigated
P2, MajorSingle premise fully down, or major feature unavailable4 hoursDaily
P3, MinorSingle device or feature degraded; workaround available1 business dayAs progress occurs
P4, LowQuestion, feature request, cosmetic issue2 business daysAs progress occurs

Severity is determined by us in good faith, communicated to the customer, and may be adjusted as new information emerges.

2.4 Data freshness

StreamCommitment
Live occupancy data in dashboardWithin 60 minutes of edge ingestion
Daily aggregate analyticsAvailable by 12:00 EET the following day
Tailgating event notificationsWithin 10 minutes of detection (where the add-on is contracted)

3. Measurement methodology

3.1 Premise uptime calculation

Premise uptime % = (operating minutes with active device) / (total operating minutes) × 100

3.2 Dashboard and API availability

Availability % = (in-month minutes with successful synthetic check) / (total in-month minutes) × 100

3.3 Support metrics

4. Maintenance windows

TypeNoticeCounts as uptime?
Planned maintenanceAt least 48 hours advance notice via email and Slack channels (where available)Yes
Emergency maintenanceBest-effort notice as soon as practicalYes
Edge device firmware and component updatesRolling deployment; an individual device may be briefly offlineYes

Planned maintenance is normally scheduled outside member-facing hours (weekend nights, EET).

5. Exclusions

The following do not count against our uptime or response commitments.

  1. Customer-side network and power. ISP outages, customer LAN or Wi-Fi changes, firewall changes, VLAN reconfiguration, electrical outages, building maintenance.
  2. Customer-side hardware events. Physical damage, tampering, unauthorized relocation, theft, environmental damage (water, heat, dust).
  3. Customer-requested changes. Equipment remapping, camera repositioning, premise layout changes (these initiate a change request, not an outage).
  4. Third-party service outages beyond our control, including authentication providers, AWS, Microsoft Azure, camera vendor cloud services, partner integrations.
  5. Force majeure. Natural disasters, war, strikes, government actions, pandemics, internet backbone outages.
  6. Beta or preview features. Anything explicitly labelled as beta, preview, or experimental.
  7. Periods awaiting customer input. The support clock pauses while we wait for customer-supplied information, access, or on-site action.
  8. Suspended service. Periods where the customer has unpaid invoices more than 30 days overdue.

6. Service credits

Service credits are the customer's sole and exclusive remedy for missed commitments under this SLA.

6.1 Credit schedule

Applied to the affected premise's monthly subscription fee for the month in which the miss occurred.

Monthly premise uptimeCredit
90.00% to 94.99%5% of premise monthly fee
80.00% to 89.99%10% of premise monthly fee
Below 80.00%25% of premise monthly fee

For dashboard or API availability below 99% in a calendar month, a 5% credit is applied to the customer's total monthly platform fee, once per affected month regardless of duration.

6.2 Cap and stacking

6.3 Claim process

Customers must claim credits in writing (email to support@gymplus.fi) within 30 days of the affected month's invoice, including:

We will respond within 10 business days with our measurement and either confirm the credit or explain the variance. Credits not claimed within 30 days are waived.

7. Reporting

Customers may request a written uptime report for any calendar month within the prior 12 months. We will deliver the report within 10 business days. Chain customers receive automatic monthly reports as part of standard account management.

8. Limitations

9. Changes to this SLA

We may update this SLA with at least 30 days' notice to customers. Any changes that materially reduce the commitments above will not apply to existing contract terms; they take effect at the next contract renewal.