Pilot policy · 25 August 2026
Privacy
SeatRoster is designed for organizations that coordinate shared workplace seating. During the controlled pilot, an organization administrator provisions access and determines the organization’s seating rules.
Information kept
A global account contains your name, verified email, language preference, and a password credential stored only as a memory-hard scrypt hash. Each organization separately controls your role, primary team, and policy-group memberships. Booking requests contain the organization, location, date, period, status, original request time, and assigned seat where applicable.
Information not kept
SeatRoster does not store profile photos, phone numbers, titles, IP addresses, device profiles, behavioral profiles, personal calendar data, readable passwords, or free-text audit payloads.
Visibility and waitlists
Your organization chooses whether allocated colleague names or availability only is shown. Waitlist names are never exposed. Administrators have an operational list, not an employee analytics dashboard.
Retention
Booking history stays linked to a person for 90 days and is then anonymized. Minimal audit events—actor, action, target type, and timestamp—are deleted after 90 days. Removing a member cancels future requests and revokes active sessions. A global account is deleted when no organization memberships remain.
Contact
Questions about an organization’s membership or seating policy should first go to that organization’s administrator. Product privacy questions may be sent to privacy@seatroster.com.