Talentflake

Talentflake privacy policy

How Talentflake handles account information, workspace records, authentication, and connected MCP tools.

Scope and publisher

Talentflake is published by Bytespoke. This policy covers the Talentflake web app and its released MCP connection. It explains the information involved in using the service, how that information supports its features, and where to send privacy requests. The Bytespoke privacy policy provides additional information about Bytespoke; the contact link is below.

If you use Talentflake through your employer or another organization, its administrators manage your workspace access and business records. Your organization may also provide privacy information about its use of Talentflake.

Account and workspace information

Talentflake processes account and authentication information, such as your name, email address, account identifiers, organization and company memberships, and access roles.

The web app stores records that you or your organization enter, upload, create, or update. Depending on the features you use, these may include employee and employment information, attendance, project and activity assignments, time reports, leave information, expense claims and receipts, reimbursement information, customer and supplier details, approvals, and reports.

Attendance information includes check-in and checkout times. Where your organization enables location-related attendance features and you provide the requested information, attendance records can also include location, address, device, or network information. The released MCP tools do not collect or invent GPS or device-location data.

How information supports the service

Talentflake uses account and workspace information to authenticate users, establish organization and company access, carry out requested workflows, maintain the associated records, and provide the reports and approvals available to authorized users.

Information in a workspace is made available according to the user roles and permissions configured for that workspace. Some workflows allow an authorized colleague or approver to review or act on a record.

Authentication, browser state, and service providers

Talentflake uses Supabase for its authentication and database services. The web app uses browser authentication state to maintain sign-in and stores browser preferences such as the selected display theme.

Hosting and infrastructure services process the requests needed to operate the web app and may retain operational logs under their applicable policies. The complete production-provider inventory, processing locations, and any additional analytics or tracking disclosures remain to be finalized. This policy does not assert that additional tracking is absent.

Access and security

Talentflake uses authenticated accounts and role-, organization-, and company-scoped access checks to control access to records and actions. Protect your account credentials and only share workspace access with people your organization authorizes.

For suspected account-access or data-exposure issues, contact support@bytespoke.com. Do not send passwords, authorization codes, access tokens, or unnecessary employee information in your message.

Retention, deletion, and privacy requests

The web app stores task and business records. Disconnecting an assistant or ending a sign-in session does not itself delete the records created or updated in Talentflake.

Record-specific retention periods, deletion schedules, and backup handling for the web app have not yet been finalized. A retention period or deletion rule for MCP tool-audit metadata has also not yet been defined. These are separate categories of records and may ultimately have different rules.

Contact privacy@bytespoke.com to ask about your information or request access, correction, or deletion. Identify the relevant Talentflake organization and record type without sending unnecessary sensitive information. Requests concerning employer-managed records may also need to involve your organization. The handling of a request depends on the applicable records, account arrangements, and legal obligations.

MCP connections: requests and task records

When you connect an external AI assistant through MCP, the connection processes the information needed for the requested Talentflake action and returns the result to that assistant. Depending on the tool, this can include account and organization identifiers, attendance, project time, leave information, expense information, and approval information. Existing Talentflake permissions continue to control access.

Talentflake MCP does not maintain separate MCP conversation or task storage. Tool requests run without a persistent MCP session. Records created or updated through those tools are stored in the Talentflake web app; the no-separate-storage statement does not apply to the web app records themselves.

MCP connections: audits, OAuth, and external assistants

For security and operations, Talentflake records limited tool-audit metadata: the tool name, user, organization, OAuth client, and outcome. These audit records do not include tool arguments or HR payloads. They are separate from Talentflake task records.

Supabase handles OAuth authorization and grants. Hosting and infrastructure logs may also be retained under the providers' policies. The absence of a persistent MCP session does not mean that OAuth records, audit metadata, or infrastructure logs are absent.

The external AI assistant you choose receives your requests and relevant tool results and handles them under its own terms and privacy settings. Review those settings before connecting it to your workspace. You can review or revoke connected assistants through the signed-in Integrations page; revocation does not remove information already received by an external assistant.

Contact

Bytespoke publishes Talentflake. For privacy questions, retention information, or requests concerning your information, email privacy@bytespoke.com. For product support, email support@bytespoke.com.