This Privacy Policy explains how Temirin collects, uses, discloses, retains, and protects information when you visit the public website, create or access a workspace, connect sources or accounts, subscribe to paid plans, contact sales or support, submit forms, use analytics preferences, or use controlled prediction-market workflows.
This Policy applies to Temirin-controlled processing. Third-party services such as Polymarket, wallet providers, Nuvei, email providers, social platforms, analytics providers, hosting providers, and source services process information under their own terms and privacy policies.
For privacy questions or data-rights requests, contact privacy@temirin.com or the support contact published on the Temirin website.
We may collect identifiers and account information such as name, email address, workspace name, organization name, role, invitations, authentication events, session metadata, support messages, demo requests, sales requests, newsletter preferences, communication preferences, and billing-provider identifiers.
We may collect workspace configuration such as plan selection, selected markets, watched categories, excluded categories, source labels, source URLs, RSS feeds, web links, social handles, Telegram or Slack configuration, webhook endpoints, public wallet addresses, alert rules, delivery destinations, investment policies, approval preferences, auto-reload preferences, decision notes, risk acknowledgements, paper orders, compliance records, and user settings.
Temirin may process public wallet addresses, public blockchain data, public Polymarket profile or portfolio data, market metadata, price observations, trigger prices, current prices, market-match candidates, opportunity signals, position snapshots, order workflow records, venue responses, and related analytics needed to display portfolio context, PnL context, risk views, journal history, attribution, and workflow state.
Public wallet and on-chain information may be visible to anyone with access to public networks or venue data. Connecting or entering a public wallet address may allow others with access to the workspace to infer trading activity, balances, positions, timing, and strategy.
Temirin is not intended to collect private keys, seed phrases, mnemonics, or raw wallet secrets. If such material is submitted, we may reject, block, delete, quarantine, or redact it for security and compliance reasons.
When you connect a third-party service, we may process account identifiers, scopes, tokens, bot credentials, API credential metadata, validation status, source-read results, delivery status, health checks, and safe diagnostics needed to operate the connection.
Connector secrets are designed for server-side storage and should not be returned to the browser after storage. Access to secrets is intended to be limited by role, system need, audit controls, and revocation processes.
You should not provide credentials unless the product expressly requests them in the relevant connection flow. Do not submit private keys, seed phrases, unsupported secrets, or credentials belonging to another person or organization without authority.
We may collect device, browser, IP-derived approximate location, time zone, language, referral URL, page activity, feature usage, click events, route changes, session identifiers, cookie preferences, error diagnostics, performance events, uptime signals, security events, and audit events.
Operational logs are designed to avoid unnecessary sensitive values. Where practical, logs use metadata, hashes, truncation, redaction, or structured diagnostic fields instead of raw tokens, raw secrets, raw DSNs, raw private credentials, or complete sensitive payloads.
If you contact Temirin or interact with support, sales, onboarding, or account-management workflows, we may process support tickets, contact forms, email messages, phone or WhatsApp metadata, notes, assigned representatives, status changes, response history, customer health, billing context, workspace diagnostics, and communication preferences.
We may maintain a customer history so support, sales, compliance, billing, and product teams can understand prior requests, issues, notices, alerts, account changes, and operational context.
The public website may use necessary storage for site functionality, authentication, cookie preferences, security, routing, and form operation. Optional analytics, attribution, and product-improvement scripts are loaded according to your consent settings or deployment-specific consent configuration.
You can manage preferences in the Privacy Center. Browser settings may also block cookies or tracking. Some features may not work properly if necessary storage is disabled.
We use information to provide, secure, authenticate, personalize, maintain, troubleshoot, support, bill, and improve the Services; create and restore sessions; maintain workspaces; enforce plan limits; process subscriptions; deliver alerts; ingest sources; match evidence to markets; capture trigger and current price context; route approval requests; display market and portfolio context; maintain audit records; prevent abuse; comply with law; and enforce our terms.
We may use information for security monitoring, fraud prevention, rate limiting, geofence controls, sanctions-related controls, provider troubleshooting, incident response, product analytics, quality assurance, administrative operations, and business reporting.
We may use contact information to respond to requests, send transactional emails, deliver configured alerts, send onboarding communications, provide product updates where permitted, and manage sales or support relationships.
Where data-protection law requires a legal basis, we process information as needed to perform a contract, take steps at your request before entering a contract, comply with legal obligations, protect vital interests, pursue legitimate interests, or rely on consent where applicable.
Legitimate interests may include operating and improving the Services, securing accounts, preventing abuse, maintaining audit logs, supporting customers, enforcing terms, analyzing product usage, and protecting Temirin, users, providers, and markets.
Where processing depends on consent, you may withdraw consent through available controls or by contacting us, subject to legal or contractual limits.
Temirin may use AI systems to summarize sources, classify evidence, extract entities, infer categories, match source events to markets, generate opportunity briefs, identify support and conflict, organize workflow data, assist support operations, and improve product experience.
AI processing may involve source text, market context, tags, notes, opportunity records, policy settings, support context, and other information needed to provide the requested feature. AI outputs can be inaccurate and should be reviewed by users before use in any legal, financial, compliance, or trading workflow.
We do not intend to use private keys, seed phrases, raw wallet secrets, or raw payment-card numbers for AI processing.
Checkout, payment collection, payment-method handling, card security, invoices, tax calculations, hosted billing interactions, and certain billing communications are delegated to the payment processor. Temirin stores billing identifiers, plan state, subscription state, invoice metadata, payment status, entitlement information, and related webhook records needed to operate the account.
If Auto-Reload or funding controls are enabled in the future, Temirin may store payment-provider tokens, reload policy settings, funding-route metadata, threshold values, reload ledger records, authorization records, and status diagnostics, but not raw card numbers, CVV codes, or full payment credentials.
Temirin is not intended to store raw card numbers, CVV codes, or full payment credentials. Payment-provider privacy and security practices apply to data submitted through checkout, payment-method setup, the billing portal, or funding-provider screens.
We may disclose information to service providers that host, secure, store, monitor, analyze, email, bill, support, communicate, automate, debug, or operate Temirin. These may include cloud providers, database providers, email providers, billing providers, analytics providers, error-tracking providers, support tools, CRM tools, communication providers, and automation tools.
Service providers are expected to process information for instructed business purposes and to maintain appropriate confidentiality and security measures. Actual provider lists may change as operations evolve.
We may disclose information if required or appropriate for law, regulation, subpoena, court order, sanctions screening, legal process, provider investigation, market-integrity inquiry, fraud prevention, security incident response, compliance review, tax or billing obligations, dispute resolution, or protection of rights, safety, and property.
We may preserve and disclose records relating to suspected prohibited use, credential abuse, geofence evasion, misuse of restricted information, fraud, manipulation, security threats, payment disputes, or violations of venue rules or Temirin terms.
Information may be disclosed or transferred in connection with a merger, acquisition, financing, reorganization, bankruptcy, sale of assets, due diligence, corporate transaction, or similar business event, subject to appropriate confidentiality and legal protections.
Temirin and its providers may process information in countries other than your country of residence. Those countries may have different data-protection rules.
Where required, we use contractual, technical, and organizational safeguards intended to support lawful cross-border transfers, such as data-processing terms, standard contractual clauses, access controls, and security measures.
We retain information for as long as needed to provide the Services, maintain accounts, enforce plans, satisfy legal, tax, billing, accounting, security, market-integrity, audit, dispute, fraud-prevention, and legitimate business needs, and maintain backups.
Retention periods vary by category. Billing records, compliance acknowledgements, security logs, audit trails, support history, and legal records may be retained longer than transient analytics events, temporary ingestion diagnostics, or cached market data.
Deletion requests may not remove information that must be retained for legal, tax, billing, audit, security, dispute, backup, market-integrity, or legitimate business purposes.
TEMIRIN uses administrative, technical, and organizational safeguards intended to protect information, including access controls, server-side credential handling, secret scanning, audit logging, rate limits, redaction practices, role permissions, and secure development practices.
No system is perfectly secure. You are responsible for your email account, devices, wallet security, browser extensions, team invitations, connected-service credentials, endpoint security, and operational security practices.
If you believe your account or workspace has been compromised, contact support promptly and revoke affected external credentials where appropriate.
Depending on your location, you may have rights to access, correct, delete, export, restrict, object to, or withdraw consent for certain processing. You may also have rights to opt out of marketing communications, certain analytics, certain sharing, or certain automated processing where applicable.
Authenticated users may use account export and deletion controls where available. You may also contact privacy@temirin.com. We may need to verify your identity, authority, workspace role, region, and request scope before acting.
We will not discriminate against you for exercising legally protected privacy rights, but certain requests may limit or prevent use of features that require the relevant data.
Users in certain regions may have additional rights under laws such as the GDPR, UK GDPR, California privacy laws, and similar data-protection laws. These rights may include access, portability, correction, deletion, objection, restriction, opt-out, and appeal rights.
Temirin does not intend to sell personal information in the conventional sense. If a deployment uses analytics or advertising technologies that applicable law treats as sharing or targeted advertising, controls should be provided through consent and privacy preferences where required.
Temirin is not intended for children or underage users. You may not use the Services if you are below the age required to enter binding contracts or below the minimum age required for the applicable product, market, venue, payment provider, or jurisdiction.
We may update this Privacy Policy as the product, law, providers, or data practices change. The updated version will be posted with a new effective date. Material changes may be communicated through the product or another reasonable method where required.
Privacy questions, access requests, deletion requests, portability requests, correction requests, consent withdrawals, and other data-rights inquiries may be sent to privacy@temirin.com or the support contact published on the Temirin website.