The org chart that draws itself. Live demo, no sign-up.Play with it →
Privacy

What we hold, and why

Sprooster reads your company directory to draw an org chart. That's the whole job — so this policy is mostly about directory data, who sees it, and how to get rid of it.

Last updated: 25 July 2026. Sprooster is operated by Mantelin LLC, 116 Agnes Rd, Ste 200, Knoxville, TN 37919 (“Sprooster”, “we”). Questions, requests, or complaints: privacy@sprooster.com. This page is the plain-language summary; the complete policy — Mantelin’s Core Privacy Terms plus the Sprooster Schedule — is published at /legal/privacy.

Who the customer is

Sprooster is sold to organizations. When your employer connects their directory, they are the controller of the personal data inside it and we are a processoracting on their instructions. If you are an employee and want your entry corrected or removed, your employer’s administrator is the right first stop — they control the source directory, and Sprooster reflects it.

What we collect from your directory

When an administrator connects Google Workspace, Microsoft Entra ID, or uploads a CSV, we read the fields needed to build an org chart and a people directory:

We do not request or receive email content, files, calendars, chat messages, login history, salary, performance data, or any other HR record. On Google Workspace the connection is read-only and limited to three admin.directory.*.readonly scopes; we never write to your directory.

Google user data — Limited Use

Sprooster’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Concretely: directory data obtained through Google APIs is used only to provide the org chart and people directory to members of your own workspace. It is never sold, never used for advertising, never used to train generative AI or machine-learning models, and never read by our staff except where you ask us to for support, or where the law requires it.

What we collect from you directly

Your account (name, email, and sign-in identifiers) is handled by our authentication provider so we never hold your password. We also keep ordinary operational records: server logs, sync run history, and errors, which we use to keep the service working and to show your administrator whether the directory sync is healthy.

Who can see it

Directory data is visible to signed-in members of the same workspace, and to nobody else. Workspace membership is determined by your verified email domain or an explicit invitation. Administrators can publish a read-only view of an org chart externally; that is their deliberate act, and it is off by default.

Sub-processors

We use a small number of vendors to run the service: cloud hosting and application delivery, a managed Postgres database, authentication, and error monitoring. They process data only to provide those functions to us. The current list is published at /legal/subprocessors.

How it’s protected

Traffic is encrypted in transit. Directory credentials — service-account keys and OAuth refresh tokens — are encrypted with AES-256-GCM before they are stored, using a key held outside the database, so the database alone cannot yield a credential. Credentials are write-only through our interface: once saved, the browser never receives them back. Details are in our technical documentation.

How long we keep it

Directory records persist while the workspace is active. Someone removed from your directory is pruned on the next sync. When a workspace is closed, its data — people, chart, and stored credentials — is deleted within 30 days. Disconnecting a directory stops the sync immediately and deletes the stored credential; the people already synced remain until they are removed or the workspace is closed.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict its processing. Because your employer controls the source directory, please direct these requests to their administrator; we will assist them promptly, and we will forward any request sent to us. If you believe we have handled your data improperly you may complain to your local data protection authority.

Changes

If we change this policy materially we will update the date above and tell workspace administrators before the change takes effect.