What GC Surge commits to for availability, speed and security, and how long your data is kept.
Who it is for: Admins, and anyone who must check GC Surge for their company's security or purchasing review.
Topic | Commitment |
|---|---|
Uptime | 99.9% uptime service level agreement (SLA) for alarm reception and operator monitoring. |
Planned maintenance | Announced at least 48 hours in advance. |
Scale | At least 10,000 cameras per account, and bursts of 1,000 alarms per minute. |
Reliability | Every alarm is stored before it is classified. On a temporary fault, GC Surge tries again, so no alarm is lost. |
Speed | A camera alarm is received, classified by NOVA99x and shown in GC Surge within 5 to 10 seconds. |
Topic | Commitment |
|---|---|
Data in transit | All communication is encrypted with TLS 1.2 or higher. |
Stored credentials | Credentials, for example the user name and password of your devices, are stored encrypted with AES-256. |
Account separation | Alarms of one account never appear in another account: not in the queue, Recordings, reports or billing. |
Data | Kept for |
|---|---|
Alarm data | At least 12 months |
Video snapshots | 90 days by default |
Audit logs | At least 12 months. Nobody can edit or delete them, including admins. |
Billing records | At least 7 years |
Thank you — your feedback goes to the team that owns this page.
