1. Overview and acceptance
This page combines the Zividax Developer Policy, Privacy Policy, API Terms and Conditions, OAuth requirements, Zividax Pay payment terms, and refund rules. It applies to developers, businesses, organizations and individuals using Zividax developer products, API keys, AI services, OAuth Login, payment APIs, dashboards, documentation and related services (“Services”).
“Zividax,” “we,” “us” and “our” refer to Zividax Inc and/or Rx4Store Android Org as the operator of the relevant service. “You” means the account holder, developer, organization or person using the Services. If you use the Services for an organization, you confirm that you are authorized to bind that organization to these terms.
If you do not agree, do not use the relevant Services. You are responsible for checking that your use complies with applicable laws, platform rules and the policies shown in your Developer Console.
2. Privacy policy
Information we may process
- Account and contact details: name or username, registered email address, phone number, account identifiers and verification status.
- Developer information: app or website name, domain, redirect URLs, API key identifiers, OAuth configuration, integration status and support correspondence.
- Usage and technical logs: API requests, timestamps, usage totals, error reports, IP address, browser/device information, security events and rate-limit activity.
- Wallet and payment records: credit balances, transactions, fees, payment request details, refund/dispute status and records needed to prevent fraud and reconcile payments. We do not intend to collect or store your wallet password or email MFA code as plain text.
- Verification information: phone verification status and, if a future risk review requires it, identity/KYC information submitted through an official secure verification process.
- Cookie and preference data: session identifiers, security settings, consent choices and limited analytics where enabled.
How we use information
We use information to provide and maintain the Services; authenticate accounts; issue and manage API keys; calculate usage and charges; operate OAuth and payment flows; process support requests; detect abuse, fraud and security incidents; meet legal obligations; enforce these terms; and improve reliability.
Sharing and retention
We may share the minimum necessary information with infrastructure, hosting, messaging, payment, identity-verification and security providers that help operate the Services, or where legally required, needed to protect users, or necessary to investigate suspected fraud or abuse. We do not promise that information is never shared with service providers. Access should be limited to the purpose for which it is needed.
We retain information for as long as reasonably needed for account operation, security, accounting, dispute resolution and legal compliance. Retention periods can vary by record type and applicable law. When information is no longer needed, we will take reasonable steps to delete or de-identify it, subject to lawful retention requirements and backup cycles.
Your choices and rights
Depending on your location and applicable law, you may request access, correction, deletion or a copy of certain personal information, or raise a privacy concern by contacting [email protected]. We may need to verify your identity before acting. Some records may need to be retained for fraud prevention, legal compliance, transaction accounting or security.
3. Developer account, phone and identity verification
- You must provide accurate, current registration details and keep your email address and phone number up to date.
- Phone-number verification may be required through the official Telegram and WhatsApp verification flows presented by Zividax. Availability can depend on region and service status.
- We may request additional verification if we detect a critical security concern, inconsistent account details, suspicious activity, suspected fraud, payment risk or a mismatch between account ownership and the integration.
- Government identity documents are not required by this policy for every developer at launch. In the future, Zividax may require KYC through a secure official verification link for particular accounts, risk reviews, payment functions or legal requirements.
- For KYC-related contact, the only Telegram account handle specified by this policy is @accounts. Verify the account carefully. Do not send identity documents to lookalike accounts or unsolicited contacts.
- We may limit API access, suspend payments or restrict the Console while a reasonable verification review is pending. We will provide an explanation where appropriate and legally permitted.
You are responsible for protecting your login credentials and notifying us promptly if you suspect unauthorized access.
4. API keys, limits and developer responsibilities
API key limits
- One user account may create up to 5 API keys, subject to Console limits and security checks.
- You may use one API key across multiple apps or websites that you own or are authorized to operate, provided each integration follows these terms. Separate keys per production app are recommended for easier revocation and auditing.
- Keys are account credentials. Keep secret keys on your server; do not embed secret keys in public websites, browser JavaScript, mobile apps, repositories, screenshots or public issue trackers.
- Use the appropriate key type and environment. In particular, protect keys beginning with
zx_live_and never expose them to end users. - You must not sell, rent, publicly share, sublicense or transfer API keys, bypass quotas, rotate keys to evade enforcement, or use another user's credentials without written authorization.
Responsible integration
Build secure, maintained apps and websites with valid HTTPS, proper authentication, input validation, rate limiting and safe error handling. Do not make the Zividax API available as an unrestricted relay for unknown third parties. Monitor your usage and wallet balance, set spending controls where available, and revoke a compromised key immediately.
We recommend that a production website have an established operating history of approximately 3–6 months before requesting access to higher-risk or sensitive capabilities. This is a risk-review guideline, not a guarantee of approval or an absolute eligibility rule. New apps may be reviewed individually.
We may set or change request limits, supported models, features, quotas and access levels to protect reliability, prevent abuse or manage provider constraints. Do not use the Services for unlawful activity, spam, credential theft, malware, harassment, unauthorized surveillance, or content and activity that violates applicable law or third-party rights.
5. OAuth Login and user data
OAuth Login lets an app or website request permitted access to a user's Zividax account. Developers must:
- Register accurate app details and only use approved redirect/callback URLs.
- Request only the permissions and user information necessary for the feature described to users.
- Keep client secrets server-side, validate OAuth state and tokens, use HTTPS, and protect sessions against CSRF, replay and account-linking attacks.
- Explain clearly why access is requested and provide a working way to disconnect the integration or delete user data.
- Never impersonate Zividax, mislead users about who operates an app, or use OAuth data for unrelated advertising, resale, profiling or surveillance without a lawful basis and required consent.
- Delete or stop using OAuth data when the user disconnects or requests deletion, except for limited records that must be retained for legal, fraud-prevention or security reasons.
OAuth approval does not mean Zividax endorses your app. We may suspend an OAuth client if it presents a security, privacy, fraud or policy risk.
6. AI services, API credits and pricing
Some Developer Console features, including AI APIs, consume usage credits charged to or funded through your Zividax Wallet. If you use a credit-consuming feature, you authorize the applicable usage deduction shown in the Console or pricing information. You are responsible for activity performed with your account or API keys, including unauthorized use where reasonable security precautions were not taken.
Zividax may increase, decrease or otherwise change AI model pricing, API credit rates, quotas, available models and related fees. We will announce pricing changes through Zividax, such as the website, Developer Console or official notices. Unless a notice or law requires otherwise, new rates apply from the stated effective time and do not retroactively change completed usage charges.
AI output may be inaccurate, incomplete, biased or unsuitable for a particular purpose. You must review output before relying on it, disclose AI use where required, respect third-party rights, and avoid using AI output as the sole basis for high-impact decisions without appropriate human review. Do not submit highly sensitive or confidential information unless the service explicitly supports that use and you have the necessary rights.
We may suspend or restrict API keys for policy violations, security concerns, fraud indicators, legal obligations, non-payment, abusive traffic or other legitimate operational reasons. Where appropriate and legally permitted, we will send the reason to the email address registered to your account. Some security details may be withheld to protect detection systems or other users.
7. Zividax Pay — Payment Gateway
Zividax Pay allows an integrated website to display a “Pay with Zividax Pay” button. Your server creates a payment request using an active zx_live_… key. The customer opens Zividax Pay, reviews the developer/company, service description and amount, then accepts or rejects the request.
Customer approval and settlement
- Acceptance requires a fresh email multi-factor authentication (MFA) code. The code is valid for 5 minutes and should be used only by the intended customer.
- After successful MFA approval, the payment amount is deducted from the customer's Zividax Pay wallet immediately, subject to transaction processing and security checks.
- Zividax retains a 3.25% platform fee. The developer's net share is 96.75% of the gross payment.
- The developer's share is credited to the Console wallet after a 15-day hold. Holds may be extended where a transaction is under review, disputed, suspected to be fraudulent, reversed, or subject to legal or provider requirements.
- Payment requests must accurately describe the product or service, merchant identity and total amount. Do not use the gateway for prohibited goods, misleading charges, unauthorized recurring billing or transactions you are not entitled to collect.
| Example payment | Amount |
|---|---|
| Customer's gross payment | $1.0000 |
| Zividax platform fee (3.25%) | $0.0325 |
| Developer share (96.75%) | $0.9675 |
| Expected developer wallet credit | After the 15-day hold, subject to review |
Developers must keep transaction references and service-delivery records, provide customer support, and cooperate with reasonable payment reviews. Do not claim that a payment is final if it remains subject to a refund, dispute, reversal or compliance review.
8. Refunds, returns and payment disputes
Developers are responsible for publishing a clear return, cancellation and refund policy for the products or services they sell through Zividax Pay. Before payment, customers should be able to understand what they are buying, delivery timing, cancellation rules, refund eligibility and how to contact the merchant.
- Refund request window: If a customer requests a refund within 7 days of payment, the transaction may be reviewed under the developer's disclosed refund policy and applicable law. A request does not guarantee approval.
- Wallet adjustments: If a refund is approved or a payment is reversed, the relevant amount may be deducted from the developer's available Console wallet balance. If the balance is insufficient, the account may show a negative or recoverable balance, and further payouts or payment features may be paused while the issue is resolved.
- 15-day hold: The hold is a settlement risk-control period, not a promise that every payment becomes irreversible after day 15. Refunds, disputes, charge corrections and legal obligations can still affect a transaction.
- Review timing: Wallet balances, payment analysis, transaction status or risk assessments may change after review. Allow approximately 24–48 hours for routine updates where possible; complex cases may take longer. This is an estimate, not a guaranteed resolution time.
- Fraud and abuse: We may freeze or adjust disputed funds, request evidence of delivery, or restrict the merchant account while investigating suspicious transactions.
Contact support with the payment reference, date, amount and a concise explanation. Never include passwords, full payment credentials or MFA codes in a support request.
9. Security, enforcement and prohibited activity
You must keep your app, website, server, dependencies and API integrations reasonably secure and up to date. You must not:
- Attempt unauthorized access, exploit vulnerabilities, interfere with the Services or evade rate limits, bans, verification or payment controls.
- Use stolen, deceptive, fake or mismatched identities, domains, business details, phone numbers or payment information.
- Use the Services for scams, phishing, malware, credential harvesting, spam, unlawful surveillance, illegal content or infringement of intellectual property or privacy rights.
- Expose API keys, misuse OAuth data, manipulate payment amounts or statuses, fabricate transactions, or attempt to avoid platform fees.
- Misrepresent your service, conceal material charges, or collect payments for goods/services you cannot lawfully provide.
Zividax may warn, rate-limit, disable a feature, revoke a key, suspend an OAuth client, hold a payment, or suspend/terminate an account when reasonably necessary for security, abuse prevention, compliance or service integrity. Where appropriate and legally permitted, the registered email address will receive the reason and any available next steps. You may contact support to request a review.
10. User data deletion and app review requirements
If your app or website collects or accesses end-user information through OAuth or a Zividax API, you must provide a straightforward way for users to request deletion of their account or data. The method must be easy to find, functional and explained in your privacy policy or settings.
- Provide an in-app deletion flow or a clearly labelled deletion page/form with a working contact route.
- Explain what data is deleted, what is retained and why, and the expected processing time.
- Delete data from active systems within a reasonable period after a valid request, subject to identity verification, technical limits and legal retention requirements. Explain any exceptions to the user.
- Remove or revoke OAuth tokens and stop future collection when access is withdrawn.
- Do not make deletion unreasonably difficult, require unnecessary personal information, or route users through broken links.
- Before applying for sensitive APIs or higher-risk access, ensure the website is functional, has meaningful content, uses HTTPS, includes a privacy policy and terms, identifies the operator, and offers working user support.
Developer Console access may be denied or suspended if the app's data-deletion process is missing, misleading, broken or inconsistent with the permissions requested. We may test the deletion route and verify your policy claims as part of a review.
12. Availability, warranties and liability
The Services are provided on an “as available” basis to the extent permitted by law. We aim to keep services reliable but do not guarantee uninterrupted availability, error-free operation, permanent model availability, or that every request will succeed. Maintenance, provider outages, network failures, security incidents or legal requirements may affect access.
To the maximum extent permitted by applicable law, Zividax is not liable for indirect, incidental, special, consequential or punitive losses, loss of profit, loss of data, business interruption, third-party claims, or losses caused by your integration, your users, compromised credentials or your failure to follow security guidance. Nothing in these terms excludes liability that cannot lawfully be excluded, including any mandatory consumer rights or liability for fraud where exclusion is prohibited.
You are responsible for your own app, website, customer relationships, legal disclosures, taxes, regulatory obligations, data protection compliance and the services you sell. You should maintain backups, monitor usage, and test critical flows before deployment.
Indemnity
To the extent permitted by law, you agree to be responsible for claims and costs arising from your unlawful use of the Services, your breach of these terms, your products or services, or your infringement of another party's rights. This does not apply where prohibited by applicable law.
13. Changes to this policy and service terms
Zividax reserves the right to update, amend or replace this policy, developer terms, API pricing, usage limits and service features at any time, subject to applicable law. We will provide notice of material policy changes through Zividax, the Developer Console, the website, or the registered email address, as appropriate. Notices will state the effective date where relevant.
Changes will generally apply from their stated effective date and will not retroactively alter completed transactions unless required by law or necessary to correct fraud, error or an invalid transaction. If you continue to use the affected Services after the effective date, that continued use constitutes acceptance where legally permitted. If you disagree, stop using the affected feature and revoke or delete your integrations as appropriate.
14. Contact and support
For developer access, privacy requests, API key reviews, OAuth issues, wallet questions, payment disputes or policy clarification, contact the official channels below. Include your registered email and relevant request or transaction ID, but never send passwords, secret API keys or MFA codes.
Published by Zividax Inc · Rx4Store Android Org. Effective date: 13 October 2026.