Privacy policy
What data we process, how we use and retain it, and how to contact us about your rights.
1. Scope and responsible organisation
This policy covers the Get-Router and Get Run websites and related account, model API and support services operated by AxiLink Technology pte. ltd ("we", "us"). Independent third-party websites, payment services and model services have their own applicable privacy rules.
Send privacy questions, complaints and rights requests to getcodex001@gmail.com.
2. Data we process
- Account and authentication data: your email address or phone number, account identifier, site, password verification information, verification results, sessions and security records, for registration, sign-in, recovery and account protection.
- API and usage records: API Key management records, request identifiers, models, call times, interfaces, result statuses, usage, price snapshots and charges, for authorisation, service delivery, billing, reconciliation and troubleshooting.
- Payment and billing data: top-up orders, amounts, currencies, credit conversion information, payment references and statuses, balance changes and statements, for verifying payments, maintaining accounts and resolving disputes. Payment providers collect and process card and other payment details as described on their payment pages.
- Support and enterprise enquiries: names, roles, companies, email addresses, phone numbers, requirements and correspondence you submit, together with the source site, language, submission time and handling status, to respond to your enquiry.
- Operational and security data: IP addresses, request times, paths, statuses and security audit records needed to operate the service, prevent abuse and investigate incidents.
Only submit information needed for the service. Do not include passwords, complete API Keys, payment secrets or unnecessary sensitive personal data in enquiry forms, emails or logs.
3. Model request content
To fulfil a model call, prompts, messages, images and other request content pass through our service and are transmitted to the service provider for the selected model. We generally do not retain model request or response bodies. When a request is blocked by the cyber-security policy, we retain its request body, API Key name and IP address in a dedicated risk-control record so administrators can review possible false positives. Violations are counted, and reaching the suspension threshold disables the account. Administrators can reset the current count; lifetime totals and violation records are preserved. Risk-control bodies are not placed in logs or analytics or used to build training datasets. When an administrator enables capture for a specific API key for testing or troubleshooting, dedicated recordings retain complete request and response headers, bodies, IP addresses and connection metadata, including client credentials present in headers. Capture is off by default. Administrators can pause, resume and clear all recordings for a key; there is no automatic cleanup. Recordings are restricted to administrator inspection and export and are not copied to ordinary logs, analytics or training datasets. Request and response bodies outside risk-control records and enabled captures are not retained.
This does not mean content avoids network or in-memory processing, or that third-party model providers follow the same retention or training policies. Assess the relevant provider's data rules and your authority to submit the material before use. Remove or anonymise sensitive data that is not required.
4. Purposes and basis for processing
We process data as needed to provide the services you request, meet applicable legal obligations, and pursue security and operational purposes permitted by law. We obtain consent where required. Purposes include account management, model calls, billing and payment verification, support, abuse prevention and dispute resolution.
We do not sell personal data or use enterprise enquiries for advertising tracking. Our websites currently use no third-party analytics or advertising trackers. New purposes that differ from the original purpose will be subject to applicable notice and consent requirements.
5. Cookies and browser storage
The websites use necessary cookies for sessions and protection against cross-site request forgery, as well as language and theme preferences. Short-lived access credentials stay in browser memory. Local storage may hold pending top-up order identifiers, separated by site and account, to recover orders after a refresh or sign-in.
If an administrator explicitly chooses to remember Bailian query settings, the browser stores the region, workspace identifier and API Key required for those queries. The administrator can turn off remembering and clear the settings. Do not save this configuration on shared devices.
You can manage or clear cookies and local data in your browser. Disabling necessary cookies may prevent sign-in, payment recovery and other features from working correctly.
When a security check is required, the page loads Cloudflare Turnstile. Cloudflare processes browser and device signals needed for verification. Our server submits the verification token and client IP to validate the result. The token is held briefly in browser memory and is not included in ordinary logs.
6. Sharing and international processing
We provide relevant data to model, hosting and infrastructure, verification and communications, and payment providers only as needed to deliver the service, and restrict internal access. Necessary records may also be disclosed to authorised bodies or professional advisers where required by law, to protect accounts and service security, or to handle disputes.
Our operator is based in Singapore. Depending on the model, payment provider and infrastructure used, data may be processed outside your location. We take measures required by applicable law for international transfers. A "China" or "global" account identifies a separate business site; it is not a promise of storage exclusively in any country or region.
7. Retention and account closure
The current system retains account identities, usage, price and statement snapshots, payment and financial records, audits and notifications permanently, without automatic expiry or deletion. Closing an account disables the account and access; it does not automatically delete these historical records. Closing an enterprise enquiry does not delete its submitted data. Self-service historical deletion and data export are currently unavailable.
Records are retained for reconciliation, security, disputes and legal obligations. This technical arrangement does not remove legal requirements concerning the necessity or duration of retention. For access, correction or deletion requests, we will verify your identity, the record categories and applicable law, and explain available steps or lawful reasons for continued retention.
8. Your rights
Email us to request access, correction, withdrawal of consent, deletion or other rights available under applicable law, or to make a complaint. Include your account contact details, site and the scope of your request. We will seek only additional information needed to verify identity and handle the request, and respond under the procedures and time limits required by law.
Accounting, payment, security, dispute-related or other legal retention duties may limit some requests. Withdrawing consent to necessary processing may prevent us from continuing the relevant service. You may also complain to the competent data protection authority in your location.
9. Security and minors
We use access controls, authentication safeguards, transport security and auditing to protect information. No online service can eliminate all risk. If an account or API Key may be compromised, disable or replace the affected credentials and contact support. Personal data incidents will be assessed and notified where required by applicable law.
Users must have the capacity required to enter into a contract under applicable law. Minors should use the service with guardian consent and supervision. Guardians who believe a minor has improperly submitted personal data can contact us for verification and handling.
10. Policy updates
The date on this page identifies the latest update. We will revise this policy when the service or data handling changes, and provide additional notice or obtain consent for material changes where required by law. Updates do not remove your statutory rights.
