Security and privacy by design.
This page is meant to answer the practical trust questions buyers ask before rollout: what data is used, how location-aware features work, what AI touches, and where to find supporting policy detail.
Data collected and why
We collect account, usage, device, and communications data needed to run the platform and support you. Details are in our Privacy Policy.
Location and attendance data
Location may be used to validate clock-ins and enforce on-site policies you configure. Retention and categories of processing are described in the Privacy Policy.
AI features and data handling
Sync AI and related features may process prompts and context to generate answers or actions according to your workspace rules. Third-party AI service providers may assist as disclosed in the Privacy Policy.
Access controls
Role-based access helps ensure staff see schedules, tasks, and data appropriate to their responsibilities. Administrators can manage membership and permissions centrally.
Operational safeguards
Audit-ready histories, approval flows, and role-based visibility all support more accountable operations. Security is not just about infrastructure; it is also about making actions, changes, and exceptions easier to review.
Incident readiness
Teams evaluating SuprSync typically want a clear escalation path. Use this page together with your status page, privacy policy, and support process so buyers know where operational and security questions go.
Privacy
Review collection, retention, and AI-processing notes in the Privacy Policy.
Operations
Review safeguards, access controls, and support paths before rollout.
Support
Security and trust questions should have a clear routing path for prospects and customers.
Copyright © 2026 SuprSync. All rights reserved.