Endstack

Defines team membership data — team ID, role, and associated plan — as a specific metadata element stored by Endstack for team-access management.

" Team membership — if applicable, your team ID, role (admin/member), and associated plan"

Enumerates specific purposes for which Endstack uses collected data — service provision, infrastructure maintenance, team management, user communication, AI request processing, and Terms enforcement — linking each purpose to specific data categories, thereby defining the permitted uses of personal data and creating an obligation to limit use to those purposes.

" Provide the Service Account info, instance metadata — to authenticate you, provision your container, and route you to your desktop Maintain and operate infrastructure Instance state, infrastructure metadata — to start/stop containers, ma..."

Specifies that upon termination user access ceases, Endstack may delete the user's container and contents after a reasonable retention period, and account metadata may be retained for legal, regulatory, or legitimate business purposes — defining post-termination data lifecycle obligations and permissions.

" Upon termination, your right to access the Service ceases. We may delete your container and its contents after a reasonable retention period following termination. Account metadata may be retained as required for legal, regulatory, or legi..."

Specifies retention periods and deletion procedures for each data type: account information is retained while active and deleted upon request subject to legal requirements; instance metadata is retained while the instance exists and cleaned up after deletion; container contents are deleted after a reasonable grace period post-termination; AI conversations are stored locally in the user's container and the provider does not retain copies, with a note that AI providers may retain data per their own policies with an opt-out where supported — the non-retention of AI conversations is user-favorable.

" Account information Retained while your account is active. Deleted upon account deletion request, subject to legal retention requirements. Instance metadata Retained while your instance exists. Cleaned up after account deletion. Contai..."

Segment identifies the plan types offered (Individual, Team, Enterprise) and notes that plan details, pricing, features, and usage limits are described on the website and subject to change, establishing the framework of plan-level differences.

" We offer Individual plans and Team plans. Enterprise plans may be offered in the future. Plan details, pricing, features, and usage limits are described on our website and may change over time."

Defines the team plan tier as enabling multiple users to access a shared desktop environment, with the team administrator responsible for managing membership, roles, and permissions.

" Team plans allow multiple users to access a shared desktop environment. The team administrator manages membership, roles, and permissions."

Assigns responsibility to the team administrator to manage access controls and ensure appropriate use by team members in shared desktop environments, while disclosing that all team members may access shared files and resources.

" In shared desktop environments, all team members may have access to shared files and resources. The team administrator is responsible for managing access controls and ensuring appropriate use by team members."

Describes user-level isolation through individual Linux user accounts within shared containers, while disclaiming full isolation by noting shared desktops inherently involve shared resources and advising user judgment about data storage.

" Each user on a team plan has their own Linux user account within the shared container, providing a degree of user-level isolation. However, shared desktops inherently involve shared resources, and users should exercise judgment about what ..."