Account access
Temirin workspaces are locked behind verified passwordless access. The Command Center, billing controls, sources, alerts, and team settings are available only after session verification.
Trust, data boundaries, and capital controls for serious Polymarket workflows.
Temirin is built around a simple operating promise: keep sensitive workflows gated, keep source and price context inspectable, avoid unnecessary secrets, and preserve an audit trail for the decisions that matter.
Clear boundaries for opportunity intelligence, account context, and controlled capital workflows.
The trust model emphasizes transparency: what is public, what is stored, what is delegated to providers, and which workflows require wallet proof, legal gates, geofence checks, price checks, policy limits, and explicit user control.
Polymarket boundary
Portfolio and history views use public wallet and market data. Temirin never asks users to paste private keys, seed phrases, mnemonics, or unsupported wallet secrets.
Credential handling
Connector secrets are designed for server-side encrypted storage, scoped access checks, explicit revocation, safe validation logs, and no secret echoing back to the browser.
Geofence posture
Venue-sensitive workflows are designed to respect blocked, close-only, sanctions, legal-review, and jurisdiction controls before any execution-sensitive action can progress.
Source transparency
RSS, web, Telegram, X, webhook, and market inputs are treated as evidence. Opportunity signals should show source context, market-match rationale, trigger price, current price, and confidence instead of relying on hidden model output.
Audit trails
Authentication, connector changes, billing events, source ingestion, opportunity decisions, policy acknowledgements, support actions, team changes, approval responses, funding events, and order workflow actions are recorded for operational review.
Capital controls
Controlled workflows depend on wallet proof, CLOB readiness, eligibility, acknowledgements, role permissions, source and category budgets, sizing rules, kill-switch posture, venue requirements, and explicit user controls.
Data controls
Authenticated users can export workspace data and request deletion of account-controlled records, subject to legal, billing, security, and audit retention needs.
Billing and reload safety
Payment providers handle hosted checkout, payment collection, and card data. Any future auto-reload path must use tokenized payment references, explicit mandates, caps, cooldowns, and audit records.