Oqera · Legal & purchase
Privacy Policy
How Oqera handles account, workspace and subscription data, and how to contact us about your rights.
On this page
Effective date: 2 November 2026
1. Who is responsible
Oqera supplies the service at https://oqera.org and https://app.oqera.org. Business contact address: 20 E-652 Street, Astana, Kazakhstan. Legal form: Individual entrepreneur (ИП). Operator country: Kazakhstan. Postal code: Z00A6M4.
Oqera's and the AI providers' data flow and roles: Oqera processes account and workspace information to supply the service. The selected AI provider receives the task context needed for a requested run through the user's current BYOK connection. Provider-specific processing roles, retention and training terms depend on the provider agreement and settings; supplying a key alone does not determine those legal roles.
Privacy contact: kasymkannurasyl@gmail.com
Public operator details are on the supplier information page. The Purchase terms describe the Free and Founder offers and availability.
2. What we collect
2.1 Application and account data
The application collects your name, email, company/product name, optional URL, role, team size, what you are building, current manual AI coordination, AI tools and desired delegation. The founder uses it to review requests for a limited cohort and contact selected participants. Submission does not create an account or access.
Invited account authentication is handled by self-hosted GoTrue on the operator's infrastructure. Authentication stores password hashes; Oqera does not store your password in plaintext. Admission applications, decisions and access grants are persisted by Oqera.
2.2 Content you create ("Your Content")
- Business knowledge (canon) — company profile, glossary, policies and processes you author. This is business information you supply and may contain personal data if you choose to put it there.
- Task boards — tasks, statuses, agent reports and run history.
- Working memory — summaries agents and supervisors produce during runs, stored as vectors for later recall.
- Workspace files — files agents read and write while working.
- Agent configuration — roles, prompts, model selection, tool grants.
- Workflow inputs and decisions — evidence you supply, typed outputs and human checkpoint decisions in Customer Discovery, Product Decisions, Founder Sales, Market, Content Engine, Marketing, Design, Finance and qualified Coding.
2.3 Credentials you connect
- AI provider API keys if you use a supported BYOK connection, as current Free and early access do. Your own key is not a requirement for the upcoming Founder offer’s included AI. Connected keys are stored encrypted at rest using authenticated encryption with a key-derivation function. Used only to execute runs you initiate.
The Apps catalog and connection configuration are part of the service. An actual connection or OAuth flow requires its own setup and consent; the catalog alone does not authorize external actions or establish connected-service readiness.
We do not display these values back to you in full after saving, and they are not included in API responses.
2.4 Technical data
IP address, browser and device information, timestamps, and request logs, collected for security, abuse prevention and debugging. Error diagnostics if you have consented to error reporting.
2.5 Payment data
Free remains free. The updated Founder offer — US$19/month with platform access and AI usage included within the plan’s limits — is preparing for launch. Paid checkout is not yet enabled and its trial terms are not confirmed. A Free account does not automatically become Founder. Current BYOK usage is paid separately to your provider; separately paid connected services are not included. See the Purchase terms.
If you place a paid order through Paddle, Paddle collects and processes the checkout information needed for the payment, invoicing, tax and fraud controls. Its Privacy Policy describes that processing. Paddle is the Merchant of Record for the transaction; it is not the provider of Oqera's AI workspace.
Oqera receives the payment-service identifiers and subscription information needed to manage software access: customer, subscription and price identifiers, subscription status, billing-period dates, cancellation state and payment-event metadata. Payment event records include identifiers, time and a payload hash for duplicate detection. Oqera's billing adapter does not store full card numbers or card security codes.
Billing-record retention and its legal basis: Oqera keeps subscription identifiers, status, billing-period dates and duplicate-prevention event records separately from workspace content. They are not removed by the workspace-erasure action. They are retained while needed to manage the subscription, reconcile payments, address disputes or fraud, and meet applicable accounting, tax and other recordkeeping obligations. The applicable purpose, outstanding dispute or legal hold determines the retention period; records no longer needed for those purposes are handled through a verified privacy request. Paddle retains its own transaction records under its own legal obligations and privacy policy. Oqera does not store full card numbers or card security codes..
3. Why we process it, and on what legal basis
| Purpose | Data | Basis |
|---|---|---|
| Provide the Service | Account data, Your Content, credentials | Performance of a contract |
| Execute agent runs | Task context, canon, memory, files | Performance of a contract |
| Review Closed service applications | Application details and review decisions | Basis subject to approved publication review |
| Security, abuse prevention, fault diagnosis | Technical data, logs | Legitimate interests |
| Service communications (outages, changes to terms) | Email address | Performance of a contract; legitimate interests |
| Marketing email | Email address | Consent — opt-in, withdrawable at any time |
| Manage a paid software subscription, when purchased | Payment-service identifiers and subscription state | Performance of a contract; applicable recordkeeping obligations |
We do not sell personal data. We do not use Your Content to train AI models.
The updated Founder offer with included AI is preparing for launch. Its supported AI providers and processing arrangements must be disclosed before activation; the current BYOK data flow is described below.
4. Sending your data to AI providers
For current BYOK runs, we send the relevant task context — which may include canon entries, task board content, workspace file contents and conversation history — to the AI providers used through your supported BYOK connection. The selected provider receives the context needed for the operation and charges your own provider account under its terms.
This is the core function of the Service and cannot be disabled while using agents.
The actual providers, purposes, processing roles and applicable arrangements are identified in the service list below. Their retention and training conditions depend on the provider, your account agreement and the actual configuration. Providing a key does not by itself establish the provider's legal role. Review these disclosures before adding sensitive business information. The service does not promise support for every provider or local runtime.
5. Service providers and data-processing roles
Services that process data, their purposes, roles and locations: Service inventory: Oqera operates the application, databases and GoTrue authentication on its own infrastructure in Kazakhstan. Cloudflare supplies public-site delivery, API tunneling and host-injected Web Analytics for aggregate traffic and page-performance metrics; its global network can process request metadata. Google supplies optional sign-in and the configured encrypted Drive offsite destination. Exa supports enabled web-research operations; Composio supports enabled app connections and authorized tool execution. Paddle processes subscription checkout and payments as Merchant of Record when enabled. Your selected current BYOK AI provider and connected apps receive the context needed for operations you request. Processing roles and locations depend on the actual service agreement and configuration; an Apps listing alone does not transmit your content.
Hosting provider: Self-operated Oqera application server on the operator's computer; hosting region: Kazakhstan. Authentication hosting: Self-hosted GoTrue authentication on the operator's infrastructure in Kazakhstan; authentication is not hosted in a managed Supabase project..
AI-provider data flow and role: Oqera processes account and workspace information to supply the service. The selected AI provider receives the task context needed for a requested run through the user's current BYOK connection. Provider-specific processing roles, retention and training terms depend on the provider agreement and settings; supplying a key alone does not determine those legal roles.. The description must cover the supported BYOK connection and any other service actually used. The legal roles follow the actual flow and relationship, rather than who supplied a key alone.
Paddle processes buyer transaction information under its own buyer terms and privacy notice when you use a Paddle checkout. The confirmed inventory above must describe each actual relationship; a payment reseller is not automatically an Oqera subprocessor for all of its processing.
Services you choose to connect may receive the content needed for an authorized operation. Their processing is governed by the relevant service relationship and notice. A listing in the Apps catalog alone does not transmit your workspace content to that app. Actual research services used by enabled workflows are identified in the service list above.
6. Where your data is stored
Primary infrastructure: Self-operated Oqera application server on the operator's computer, Kazakhstan. Backup storage location: Primary backup storage is on the operator's infrastructure in Kazakhstan. An encrypted Google Drive destination is configured for offsite copies; the Google service does not provide a separately verified Kazakhstan-only storage region for this deployment.. Offsite backup status: Encrypted Google Drive offsite copying is configured. This statement does not certify a recovery time, a particular cloud storage region or the successful completion of every scheduled copy..
Intended customer markets: The primary intended market is the United States and international customers. Kazakhstan may also be served. Actual availability depends on supported buyer locations.. Applicable international-transfer arrangements: Primary application and authentication storage is in Kazakhstan. Public traffic passes through Cloudflare; optional Google sign-in, the configured encrypted Google Drive offsite destination, enabled Exa research, Composio connections, Paddle payments and your chosen AI-provider account can process relevant data outside Kazakhstan under the applicable service relationship and account terms. Only the context needed for an operation is sent to the relevant service; configured offsite backups are encrypted before upload. This offer does not promise a particular country of processing for external services. Contact the privacy email before supplying data that requires a specific transfer agreement or residency restriction. Applicable mandatory privacy rights are not waived by using a BYOK connection.. The application host's country does not establish where every service provider processes your data.
7. How long we keep it
| Data | Retention |
|---|---|
| Account data | While your account is active |
| Your Content | While your account is active |
| Working content after a closure request | 30 days for export, then deleted under the process below |
| Service logs | Production service logs rotate by stored volume: up to three local log files of 10 MiB per service. No fixed day-based expiry is configured for those logs. Durable workflow, security and billing records are distinct from rotating service logs and follow their own retention purposes. |
| Source records and workflow history | Workspace source records, generated results and workflow history follow the workspace's retention and supported deletion scope. Ordinary closure provides a 30-day export period before working-content deletion. Explicit erasure can be requested separately. Account, billing, access-decision and other records retained by the erasure preview are separate; their specific purpose and applicable legal obligations still govern them. |
| Backups | Backups are encrypted. Pruning currently requires operator review; automatic day-based deletion is not enabled. The configured 14-day pruning rule is a dry-run, and protected recovery points can remain longer. Deleted live content can remain in backup copies until those copies are removed. Backup access is restricted to recovery and authorized operations; a privacy request is assessed separately against recovery and legal-record obligations. |
Deletion process and timing: Request account closure or personal-data erasure at the privacy contact email; account ownership is verified before action. For ordinary closure, working content remains available for an export request for 30 days and is then deleted. A separate erasure request is handled under applicable law without requiring the export period to elapse. The in-app workspace erasure action previews its scope and requires explicit confirmation; it removes supported workspace content, not the authentication account, billing records or connected provider credentials. Ask separately for closure and credential removal. Subscription cancellation is separate, and retained backup copies follow the disclosed backup policy.. Backup expiry and billing record retention follow their separate policies. Cancelling Founder renewal does not close an account or begin the content-export period. A specific lawful deletion request is handled separately; the export period does not require you to wait before requesting erasure.
8. Security
The application stores AI-provider credentials encrypted and scopes stored records to authenticated users. Server admission checks additionally require an active service grant. Workflow review checkpoints require the user's decision where specified.
Access controls and encryption reduce risk; they are not a guarantee against every unauthorized access, loss or incident.
No system is perfectly secure. We will provide incident notifications where required by applicable law.
9. Your rights
Depending on where you live, you may have the right to access, correct, delete, export, restrict or object to processing of your personal data, and to withdraw consent where processing is based on consent.
To exercise a right, contact kasymkannurasyl@gmail.com. We may ask you to verify your identity before providing account data or acting on the request.
Data export process: Use the workspace export action in account settings to download the supported workspace archive while your account has access. The authenticated export covers supported workspace records and optional files; it excludes provider credentials and payment-card data. For a broader personal-data access request or an inaccessible account, contact the privacy email and verify account ownership..
Data deletion/closure process: Request account closure or personal-data erasure at the privacy contact email; account ownership is verified before action. For ordinary closure, working content remains available for an export request for 30 days and is then deleted. A separate erasure request is handled under applicable law without requiring the export period to elapse. The in-app workspace erasure action previews its scope and requires explicit confirmation; it removes supported workspace content, not the authentication account, billing records or connected provider credentials. Ask separately for closure and credential removal. Subscription cancellation is separate, and retained backup copies follow the disclosed backup policy..
If you are in the EEA or UK and believe we have mishandled your data, you may complain to your local supervisory authority.
10. Children
The Service is not directed to anyone under 18, and we do not knowingly collect their personal data. If you believe a minor has provided us data, contact kasymkannurasyl@gmail.com and we will delete it.
11. Browser storage and analytics
Browser storage supports authentication, interface preferences and a submission receipt. The application receipt contains no email, application details or access decision and does not authorize access.
The app also keeps drafts of chat messages and selected business forms in this tab's session storage so they survive a reload or navigation. Drafts are separated by account, team and form, cleared at sign-out, and not shared with other tabs. Credentials, binary attachments and saved human approvals are excluded from this draft mechanism. Closing the tab ends that browser session; sensitive business notes may still be present while the tab remains open.
First-party product telemetry records allowlisted event categories with the account identity resolved by the server, build and time. Interface error observations contain a category and build, rather than exception text, stacks, URLs or task content. Diagnostic delivery is best effort. Authorized operators can inspect these observations and answer a participant's submitted report in the app. Reports and optional screenshots contain what the participant chooses to send; participants should remove passwords and keys before submitting them. Service-log retention: Production service logs rotate by stored volume: up to three local log files of 10 MiB per service. No fixed day-based expiry is configured for those logs. Durable workflow, security and billing records are distinct from rotating service logs and follow their own retention purposes.. Durable telemetry and reports are separate from rotating service logs.
Cloudflare delivery adds a Web Analytics beacon to the public website for aggregate traffic and page-performance metrics. Cloudflare describes this service as not using analytics cookies or localStorage. See its Web Analytics documentation for collection details. This hosting-provided measurement is separate from Oqera's authenticated in-app telemetry. Cloudflare is identified in the service list above.
12. Changes
We may update this policy. For material changes we will give notice by email or in-product notice before they take effect, and update the effective date above. Previous versions are available on request.
13. Contact
kasymkannurasyl@gmail.com — Oqera, 20 E-652 Street, Astana, Kazakhstan
