Privacy Notice

Talqen is an operations platform for structured Roblox communities. It enables organizations to manage staff profiles, applications, departments, ranks, permissions, operational records, audit history, and workflows connected to Discord and customer-configured Roblox experiences.

“Talqen,” “we,” “us,” and “our” refer to the operator of the Talqen platform. Talqen currently operates under the name Talqen. Its final legal entity, legal structure, jurisdiction, business address, and company registration details have not yet been established for publication.

Talqen’s websites include:

• www.talqen.net, the public marketing website;
• staging.talqen.net, the current platform environment; and
• app.talqen.net, the planned production platform address.

Contact details for privacy and legal requests will be added before this Privacy Notice is published.

This Privacy Notice explains how Talqen collects, uses, stores, discloses, and otherwise processes personal information in connection with:

• Talqen user accounts;
• Talqen customer workspaces;
• staff, member, application, moderation, activity, and operational records;
• the Talqen Discord bot;
• customer-configured Roblox integrations;
• the Talqen marketing website;
• early-access applications;
• support requests, bug reports, surveys, and product feedback; and
• the operation, security, and administration of the Talqen service.

This notice applies to Talqen account holders, workspace owners and administrators, staff and members participating in workspaces, applicants submitting information through Talqen, website visitors, early-access applicants, and people who contact Talqen.

Talqen does not currently allow a person to appear as a workspace profile without creating a Talqen account.

This notice does not control how Discord, Roblox, or a customer workspace independently uses personal information. Those parties may have their own privacy notices and legal responsibilities.

Talqen may act in different privacy roles depending on why information is processed.

3.1 Talqen as a controller

Talqen generally determines why and how personal information is processed for:

• account creation and authentication;
• platform access and session management;
• Talqen’s own website and communications;
• support and bug reports;
• platform security and abuse prevention;
• infrastructure and technical logging;
• service administration;
• product feedback and limited service improvement;
• legal compliance; and
• Talqen’s own contractual and operational records.

For these activities, Talqen generally acts as the organization responsible for deciding the purpose of the processing.

3.2 Talqen as a processor or service provider

Customer workspace administrators generally decide why information is collected and used for workspace operations, including:

• staff and member administration;
• recruitment and applications;
• ranks, departments, and permissions;
• disciplinary and moderation records;
• activity, attendance, and shift information;
• promotions and operational history;
• customer-created forms and fields; and
• information sent through customer-configured Roblox integrations.

For these activities, Talqen’s intended role is generally to process information on behalf of the customer workspace and according to its instructions.

Workspace administrators are responsible for deciding what information they request, ensuring that they have an appropriate reason to collect it, setting suitable permissions, responding to requests concerning their records, and complying with laws that apply to their organization.

4.1 Account and profile information

Talqen may collect or generate:

• display name;
• email address;
• internal Talqen user ID;
• authentication and session records;
• account status;
• workspace memberships;
• workspace roles and permissions;
• connected Roblox and Discord identifiers;
• profile information selected or provided by the user;
• timestamps associated with account activity; and
• security and access records.

Talqen uses Supabase Authentication to handle account credentials. Talqen does not receive or store users’ readable passwords.

Talqen does not currently collect dates of birth. A separate Talqen username and profile-image system have not been finalized and may depend on the platform’s final implementation.

4.2 Technical information

When a person visits or uses Talqen, Talqen and its infrastructure providers may process technical information generated through normal web requests and platform use, including:

• IP address;
• browser type and browser headers;
• device category or operating-system information contained in request headers;
• session identifiers;
• request timestamps;
• pages, routes, or platform functions accessed;
• authentication events;
• diagnostic and error information;
• network, routing, and security metadata; and
• interaction records needed to operate integrations.

This information may be processed by Talqen’s hosting, authentication, routing, email, database, and security providers.

4.3 Communications and submissions

Talqen may collect information provided through:

• support messages;
• bug reports;
• product feedback;
• early-access applications;
• surveys, if introduced;
• referral applications or records, if introduced;
• emails and other direct communications; and
• attachments or screenshots voluntarily submitted to Talqen.

Early-access information may be used to evaluate prospective communities, communicate with applicants, and plan onboarding.

Talqen workspaces may contain information entered, configured, or generated by customer organizations and their authorized users.

Depending on the features used, this may include:

• staff or member profiles;
• display names and account identifiers;
• Roblox usernames and user IDs;
• Discord usernames and user IDs;
• ranks, departments, teams, and permissions;
• application questions and answers;
• recruitment decisions and reviewer notes;
• disciplinary, conduct, warning, suspension, or moderation records;
• activity records;
• shift and attendance information;
• administrative notes;
• operational logs;
• promotion, demotion, and rank information;
• inactivity or absence records;
• credits, redemption information, and leaderboards;
• audit logs and change history;
• customer-created form questions or fields;
• uploaded files or attachments; and
• other records used for staffing, administration, accountability, or community operations.

Talqen determines which technical fields and features the platform supports. Customer workspace administrators decide which available features to use, what information to request, what records to create, and why those records are needed.

Workspace data may be visible to other authorized members depending on workspace roles, departments, ranks, permissions, and feature configuration. Separate workspaces do not have access to each other’s records by default.

Authorized Talqen personnel may access relevant workspace information where reasonably necessary to provide support, troubleshoot technical issues, investigate security or abuse, enforce Talqen’s terms, comply with legal obligations, or maintain the service. Talqen does not intend to routinely review workspace content or independently monetize identifiable workspace information.

Workspace administrators may be technically able to enter sensitive information into free-text fields or forms. Talqen intends to restrict customers from collecting unlawful, unnecessary, excessively intrusive, or inadequately protected information. Customers should not use Talqen to collect highly sensitive information unless doing so is necessary, lawful, and expressly permitted by Talqen’s applicable terms.

6.1 Discord bot

Talqen provides a bot-based, multi-guild Discord integration. Talqen does not currently provide “Sign in with Discord” and does not use personal Discord OAuth authorization as part of the current bot architecture.

When a user interacts with the Talqen bot, Discord may provide information required to process the interaction, including:

• Discord user ID;
• Discord guild or server ID;
• the command used;
• command inputs;
• timestamps;
• linked Talqen staff identity; and
• information required to produce the requested response or workspace action.

The Discord bot may support workflows such as:

• viewing staff profiles;
• recording or viewing activity minutes;
• weekly activity summaries;
• leaderboards;
• credits and redemption tracking;
• promotion dates and cooldowns;
• inactivity records;
• operational logs; and
• connecting a Discord guild to a Talqen workspace.

Bot interactions may create Talqen operational or audit records. This is different from storing ordinary Discord conversation history.

Talqen does not currently use the bot to routinely monitor ordinary Discord conversations, read general message content, collect Discord passwords, collect Discord account email addresses, or operate through direct messages. No bulk collection of complete guild member directories has been confirmed.

Discord bot credentials are operational secrets stored through private deployment settings and are not intended to be exposed to ordinary users.

6.2 Customer-configured Roblox integrations

Talqen may provide example code, software components, endpoints, or instructions that customers can install and configure within their own Roblox experiences.

Talqen does not automatically monitor all Roblox experiences or collect broad gameplay information from all users. The information transmitted depends on:

• which example code the customer installs;
• how the customer modifies or configures it;
• which Talqen endpoints the code calls;
• which operational features the customer enables; and
• which information the customer chooses to transmit.

Depending on the customer’s implementation, a Roblox integration may transmit:

• Roblox user ID;
• Roblox username or display name;
• Roblox group ID;
• group membership;
• group rank or role;
• account-verification status;
• activity information;
• shift or attendance information; and
• other customer-selected operational records.

Talqen does not intend to collect Roblox private messages, in-game chat content, inventories, purchases, Robux balances, or financial information through these integrations.

Customers are responsible for configuring their Roblox integrations appropriately, informing affected users where required, and ensuring that the information they transmit to Talqen is necessary and lawful.

Talqen may use personal information to:

• create and maintain user accounts;
• authenticate users and maintain secure sessions;
• provide the Talqen platform and requested workspace features;
• manage memberships, permissions, roles, and access;
• process workspace information according to customer instructions;
• operate Discord bot workflows;
• receive information from customer-configured Roblox integrations;
• send transactional, authentication, security, and service communications;
• respond to support requests;
• investigate bugs and integration failures;
• maintain audit logs and operational history;
• protect accounts, workspaces, users, and infrastructure;
• prevent fraud, abuse, unauthorized access, and misuse;
• investigate suspected violations and enforce Talqen’s terms;
• suspend or restrict accounts where necessary;
• maintain and troubleshoot platform infrastructure;
• improve functionality using limited service, support, and usage information;
• review early-access applications;
• administer future billing, referral, or subscription functions if introduced;
• comply with binding legal obligations; and
• establish, exercise, or defend legal claims.

Talqen does not currently sell or rent personal information. Talqen does not currently use personal information for targeted advertising, remarketing, advertising pixels, or cross-site behavioral tracking.

Talqen does not currently send personal or workspace data to an external AI provider. No confirmed solely automated decision-making system is currently used to make legal or similarly significant decisions about users.

Where the GDPR, UK GDPR, or a similar law applies, Talqen must have a valid lawful basis for processing personal information. The appropriate basis depends on Talqen’s final legal structure, its relationship with the person concerned, the relevant jurisdiction, and the specific processing activity.

Subject to legal review, Talqen may rely on:

• performance of a contract, where processing is genuinely necessary to create an account or provide a requested service;
• legitimate interests, where processing is necessary to secure, administer, maintain, improve, or protect Talqen and those interests are not overridden by the person’s rights;
• legal obligations, where a specific law requires processing;
• consent, where participation is optional and consent is the appropriate basis;
• steps requested before entering into a contract, such as reviewing an early-access or onboarding request; or
• vital interests, in limited emergencies involving a credible threat to life or physical safety.

For customer-controlled workspace information, the customer workspace is generally responsible for identifying its own lawful basis. Talqen ordinarily processes that information under the customer’s documented instructions.

These proposed bases require review once Talqen’s legal entity, governing jurisdiction, customer agreements, and launch markets are finalized.

Talqen uses cookies or similar browser technologies where necessary to authenticate users, maintain sessions, authorize requests, protect accounts, and provide requested platform functionality.

Supabase Authentication and the Talqen application may use cookies, local storage, session storage, or similar browser mechanisms. The exact implementation will be confirmed before publication.

Talqen does not currently have a confirmed dedicated analytics provider. Talqen does not currently use:

• advertising cookies;
• remarketing pixels;
• session-recording tools;
• heatmap tools; or
• confirmed cross-site behavioral analytics.

Vercel, Cloudflare, and other infrastructure providers may process request logs, routing information, security metadata, and technical headers. These server-side records are not necessarily cookies.

Talqen does not currently provide a non-essential cookie preference interface because no non-essential advertising or behavioral-tracking system has been confirmed. A separate Cookie Policy is planned.

Talqen uses service providers to host, secure, operate, and support the platform.

Current providers include:

• Supabase, for the primary database, authentication, and file storage;
• Vercel, for the marketing website, platform frontend, preview deployments, and applicable server-side processing;
• Railway, for Discord bot and long-running bot services;
• Resend, for transactional and website-related email delivery;
• Cloudflare, for DNS, routing, and tunnel or proxy functionality where configured;
• Discord, for bot-based operational workflows; and
• Roblox, where customer-configured integrations exchange information with Roblox and Talqen.

Talqen may also disclose limited information to authorized contractors, developers, accountants, lawyers, auditors, insurers, and other professional advisers where they require it for legitimate work and are subject to appropriate confidentiality obligations.

Workspace administrators may access and export workspace information according to their roles and permissions. Once a workspace independently exports or discloses information, its handling of that information is subject to the workspace’s own responsibilities.

Talqen may disclose information:

• where necessary to provide or secure the service;
• according to customer instructions;
• to operate integrations;
• to obtain professional services;
• to investigate abuse or enforce agreements;
• to comply with a valid legal request;
• to protect users or others from serious harm; or
• as part of a legitimate business transaction.

Talqen does not intend to publish private account or workspace information by default. Customers may choose to make limited information, such as rankings, leaderboards, or profiles, visible through configured features.

No payment provider, dedicated analytics provider, external error-monitoring platform, customer-support platform, or AI provider has currently been selected or confirmed.

Talqen is intended to be available worldwide. Its providers operate infrastructure in multiple countries, so personal information may be processed outside the country where a user or customer is located.

This may include transfers outside the European Economic Area, United Kingdom, or Switzerland.

Talqen’s specific Supabase, Vercel, Railway, and Resend processing regions have not yet been confirmed. Cloudflare may process traffic through its global network. Discord and Roblox also operate internationally.

Where required, Talqen intends to use a legally recognized transfer mechanism, which may include an adequacy decision, approved contractual clauses, or another valid safeguard. Talqen has not yet confirmed which transfer mechanisms apply to each provider and should not be understood as claiming reliance on a particular safeguard until that review is complete.

Talqen retains personal information only for as long as reasonably necessary for the purpose for which it was collected, including to provide the service, follow customer instructions, maintain security and audit integrity, resolve disputes, enforce agreements, and meet legal obligations.

Talqen has not yet approved a final category-by-category retention schedule. Retention will depend on factors such as:

• whether an account or workspace remains active;
• the type and sensitivity of the information;
• customer instructions;
• whether the information forms part of an audit or operational record;
• whether deletion would affect the rights of another person;
• security and abuse-prevention needs;
• backup expiry cycles;
• contractual requirements; and
• applicable legal limitation or recordkeeping periods.

Deleting a Talqen account may not automatically erase every workspace-controlled record concerning that user. A customer workspace may retain information where it has an independent, lawful, and documented need, such as completed activity records, audit history, moderation decisions, or dispute records.

Where possible, Talqen may delete or anonymize unnecessary profile information while preserving limited audit details, timestamps, affected records, or pseudonymous internal references.

Information subject to litigation, a regulatory request, a security investigation, or another valid legal hold may be retained until preservation is no longer necessary.

Backups may retain isolated copies temporarily until they expire through the applicable provider or Talqen backup cycle.

Talqen uses administrative, technical, and organizational measures designed to protect personal information against unauthorized access, loss, misuse, alteration, and disclosure.

Current measures include:

• encrypted HTTPS/TLS communications;
• managed authentication through Supabase;
• role-based access controls;
• workspace permissions;
• selected audit records;
• separated deployment environments;
• protected service credentials and environment variables;
• provider-managed infrastructure; and
• database backup capabilities where available.

Access to personal information is intended to be limited to authorized people who require it for service operation, support, maintenance, security, or legal purposes.

Authorized developers may access limited production records or logs where reasonably necessary to troubleshoot a reported problem, restore functionality, investigate an integration or security incident, or comply with an obligation. They should not routinely browse workspace content and should use staging or sanitized information where practical.

No system can be guaranteed to be completely secure. Some security processes, including formal incident-response documentation, comprehensive internal-access logging, access reviews, penetration testing, and provider-specific encryption and backup details, remain under development or confirmation.

Talqen is not currently aware of a confirmed personal-data breach. If Talqen becomes aware of a breach, it intends to investigate, contain, document, and provide notifications where required by applicable law or contractual obligations.

Depending on the user’s location and applicable law, a person may have the right to:

• request access to their personal information;
• correct inaccurate information;
• request deletion;
• request restriction of processing;
• object to certain processing;
• receive qualifying information in a portable format;
• withdraw consent where processing relies on consent;
• appeal or request reconsideration of a decision concerning a privacy request; and
• complain to an applicable data-protection authority.

These rights are not absolute. A request may be limited where disclosure would affect another person’s rights, information must be retained by law, the request concerns another controller’s records, or another lawful exception applies.

Talqen may verify identity through an authenticated account, the registered email address, or other proportionate information already held. Additional identification should be requested only where reasonably necessary.

Requests should normally be handled without charge. Talqen may refuse or charge a reasonable administrative fee for a manifestly unfounded or excessive request where legally permitted.

Requests involving workspace-controlled data

Requests concerning application answers, disciplinary records, moderation records, shifts, activity, attendance, rank history, reviewer notes, or other customer-controlled workspace information should ordinarily be directed to the relevant workspace administrator.

Talqen may forward a request to the workspace administrator and provide reasonable technical assistance, including locating, exporting, correcting, restricting, deleting, or pseudonymizing eligible records.

Talqen will generally not alter customer-controlled records without the customer’s instructions unless Talqen has an independent legal obligation, needs to correct a Talqen-caused technical error, must address an urgent security issue, or has another valid authority.

Talqen’s dedicated privacy-request contact and final response procedure will be published once established.

Talqen is intended for users aged 13 and older.

Talqen does not knowingly:

• permit children under 13 to create accounts;
• direct the service to children under 13; or
• maintain workspace profiles for children under 13.

Users aged 13–17 may create Talqen accounts, own or administer workspaces, participate in workspaces, submit applications, and have staff, activity, moderation, disciplinary, and other operational records stored about them.

Talqen does not currently collect dates of birth, conduct age verification, require age confirmation, or operate a parental or guardian consent process.

Because privacy and consent requirements for teenagers differ between countries, Talqen’s age position requires legal review before worldwide publication. Workspace administrators should take particular care when collecting information about users aged 13–17 and should avoid requesting unnecessary or highly sensitive information.

A capable user aged 13–17 may be entitled to exercise privacy rights directly. Talqen will not automatically disclose a teenager’s information to a person claiming to be a parent or guardian without considering authority, confidentiality, safety, applicable law, and the user’s rights.

Talqen may disclose limited information as part of a proposed or completed financing, restructuring, merger, acquisition, sale of assets, or similar transaction.

Information may be shared with investors, lenders, advisers, prospective buyers, successors, or counterparties where reasonably necessary and subject to suitable confidentiality protections.

Talqen may also preserve or disclose information where it reasonably believes this is necessary to:

• comply with a valid court order, warrant, subpoena, regulatory request, or binding legal process;
• establish, exercise, or defend legal claims;
• investigate fraud, abuse, or unauthorized access;
• enforce Talqen’s agreements;
• protect the rights and security of Talqen, customers, users, or third parties; or
• respond to a genuine emergency involving a credible threat to life, physical safety, or serious harm.

Talqen may challenge requests that appear invalid, excessive, or outside the requesting authority’s powers where appropriate.

Talqen may update this Privacy Notice as the platform, providers, integrations, legal structure, or privacy practices change.

The updated notice will include a revised “Last updated” date. Where a change materially affects how personal information is used, Talqen may provide additional notice through the platform, by email, or through another appropriate method.

Changes will apply from the date stated in the updated notice unless another date is specified.

Questions, complaints, and privacy requests should be directed to:

Talqen
Privacy email: privacy@talqen.net
Support email: support@talqen.net
Legal notices email: legal@talqen.net

Talqen’s final legal name, legal structure, jurisdiction, and applicable supervisory authority will be added before publication.