Data handling

How your data is handled

A plain-language description of the data practices and user responsibilities implemented in StakeSync AI today.

This notice explains what information the product handles, how AI features use delivery context, what may be stored and which controls are currently available. It applies to the StakeSync AI website and product at getstakesync.live and reflects the current product implementation.

Last updated: 14 September 2026. This operational notice is not a negotiated enterprise data processing agreement and does not claim certifications or controls that have not been established.

Information handled

What StakeSync AI processes

Account and profile information

When you create an account, StakeSync AI stores the information needed to provide and secure it, including your email address and the profile details you provide, such as your name, organisation and role.

Delivery data you provide

You choose which Excel or CSV files to upload and which Jira or Azure DevOps connection to configure. The product works from the records made available through those actions.

Workspace records

The service may retain account-scoped records you choose to create, including derived metrics, reports, delivery snapshots, preferences, feedback and delivery-memory summaries.

Technical and preference data

The product stores session information and preferences needed for sign-in, workspace continuity, appearance, accessibility and other settings. Some preferences remain in your browser, while signed-in account preferences may also be saved to your account.

Processing

What happens when you use delivery data

Step 1
You provide data
You upload a supported file, enter information, or configure a supported source connection. You are responsible for having authority to use that information.
Step 2
The product analyses it
Uploaded files are read in your browser and converted into structured delivery records and metrics. For guests, the active workspace remains in that browser session and is not saved to an account.
Step 3
AI features process context
When you use an AI feature, the relevant prompts, delivery metrics and workspace context are sent through StakeSync AI's server-side AI service to generate the requested response.
Step 4
Selected records may be saved
For signed-in users, file names, derived metrics, generated reports, snapshots and memory summaries may be saved to the account. The upload workflow does not store the original file, although saved snapshots and reports may contain structured data derived from it.

Controls and limits

What you can control

Account-scoped access

Saved profiles, preferences, reports, snapshots and memory records are associated with the signed-in account. Access rules restrict ordinary users to their own records. Authorised administrators may access limited operational records where administration or support requires it.

Clear the active workspace

Removing an upload clears it from the active workspace. Signing out clears the session-scoped workspace from that browser tab. These actions do not automatically delete separately saved reports, snapshots, memory records or account details.

Delete saved items where offered

Features such as delivery snapshots provide their own delete controls. The current product does not provide one control that deletes the complete account and every associated record at once.

Review AI output

AI-generated content can be incomplete or inaccurate. It is decision support, not a substitute for professional judgement. Review the source evidence and verify important conclusions before acting.

Responsible use

Terms for using the product

Use StakeSync AI only with information you are authorised to provide. Do not upload unlawful content, credentials, secrets, or personal and confidential information that is not needed for delivery analysis.

You remain responsible for the source data, the questions you ask, the people with access to your signed-in browser session, and any decision made using the product's output. Do not treat an AI response, forecast, score or recommendation as guaranteed, complete or independently verified.

Jira and Azure DevOps connections are optional. If you configure one, the product uses the credentials and permissions you provide to retrieve the selected delivery records. You are responsible for keeping those credentials secure and revoking access when it is no longer needed.

Common questions

Direct answers about current behaviour

Do I need to give StakeSync AI access to Jira or Azure DevOps?: No. You can start with the Excel or CSV exports you already produce. Connected sources are optional and only used when you set them up.
Is the original uploaded file stored?: The current upload workflow reads the file in your browser and does not save the original file. For signed-in users, the service may save the file name and derived metrics, reports, snapshots or memory summaries created from the data. Those saved records may contain structured data derived from the file.
Who can see my delivery data?: Ordinary account access is restricted to the signed-in user's own saved records. Authorised administrators may access limited operational records for administration or support. StakeSync AI does not currently provide shared-workspace invitations.
Does the AI train on my data?: StakeSync AI sends relevant content to its AI service when you request an AI feature. The service uses external AI providers to generate responses, voice features and delivery memory. This page does not make a model-training or provider-retention promise that has not been contractually established.

Have a specific data-handling question before trying StakeSync AI? Read the FAQ. For account-specific requests, use the feedback and support option after signing in.

Try StakeSync AI