Privacy at a Glance
| Your question | APIONE's rule |
|---|---|
| Are API bodies stored? | By default they are processed only for as long as needed to complete the request, and stored only if you turn on request history or debugging. Routes labeled ZDR never persist full bodies |
| Is web chat stored? | It is kept in your session history until you delete it; chats in private mode are not saved to history |
| Is it used for training? | We do not train models on identifiable original content without your authorization; we may use anonymized, de-identified or aggregated data to improve the Service |
| Do you sell personal information? | No, and we do not share it for cross-context behavioral advertising |
| How long are call records kept? | The most recent 90 days are viewable in the console; we keep them for up to 13 months for billing, reconciliation and security audits |
| Who is it shared with? | Upstream model providers, necessary cloud, network, payment and support providers, and competent authorities when required by law |
| Where is it stored? | Account, billing and support data is stored mainly in the United States; call content is sent to the region of the upstream provider for the model you select |
| How do I delete it? | Delete sessions and keys in the console or close your account, or email us to request deletion or export |
| How quickly do you respond? | Within 45 days of receiving a privacy request |
1. Scope and Data Controller
This Policy applies to the processing of information by NICECLOUD LLC ("APIONE", "we" or "us") when you visit the website, register an account, use web chat, generate images or video, create an API Key, call the API, configure a client, top up, subscribe, view bills or contact support. APIONE is the controller of this information.
Where an enterprise customer submits data to us on behalf of its end users, the enterprise customer is the controller of that data, and APIONE processes it on the customer's instructions and under the data processing agreement.
Third-party models, payment institutions, sign-in platforms and clients may act as independent controllers subject to their own privacy policies.
2. Information We Collect
| Context | Information | Purpose | Retention |
|---|---|---|---|
| Registration and sign-in | Email, verification codes, account identifier, and the account identifier, name and email provided by Google, GitHub or Apple when you sign in with them | Account creation, sign-in and security | For the life of the account; handled under Section 10 after closure |
| Account profile | Nickname, avatar, language, time zone, workspace and member information | Display, preferences and organization management | Until you delete it or close your account |
| API Keys | Name, key hash, permissions, limits, allowlists, status, last used time | Authentication and key security | 13 months after the key is deleted |
| Call metadata | Model, time, tokens, status code, latency, request ID, IP, Key identifier, cost and routing | Routing, billing, security and troubleshooting | Viewable in the console for 90 days; kept for up to 13 months |
| API inputs and outputs | Prompts, code, files, parameters and model output | Completing inference, and the request history or debugging features you turn on | Not stored by default; see Section 3 when those features are on |
| Web chat and creation | Inputs, outputs, session titles, attachments, generated images and video, selected model | History and restore | Until you delete it; not saved in private mode |
| Client information | Version, operating system, connection status and necessary diagnostics | Configuration, compatibility and troubleshooting | Diagnostics 90 days; local data is under your control |
| Payments and billing | Orders, amount, currency, payment channel, status, balance, refunds and invoice details | Payment, refunds, reconciliation and accounting | 7 years after the transaction, to meet tax and financial regulations |
| Points and referrals | Points earned and redeemed, referral relationships, masked emails and order amounts of referred users | Issuing points and rewards, preventing abuse | For the life of the account; forfeited on closure |
| Support tickets | Contact details, descriptions, attachments, communications and request IDs | Support and dispute handling | 2 years after the ticket is closed |
| Security and risk control | Sign-in records, device information, abnormal calls, failed authentication and enforcement records | Preventing fraud, attacks and account takeover | Up to 2 years; kept until a related dispute ends |
| Cookies | Session, security, language, theme and, with your consent, analytics | Sign-in, security, preferences and analytics | See Section 8 |
| Agreement records | Agreement version, time of consent, account and source page | Proving which version you agreed to | During the contract and 3 years after it ends |
We do not collect sensitive personal information unrelated to the Service. Please do not send full API Keys, sign-in credentials, bank card details, verification codes or sensitive information unrelated to your request to support.
3. API Content, Web Sessions and Clients
3.1 API Content
By default, APIONE processes API inputs and outputs only for as long as needed to complete the request and does not keep the full bodies afterwards; only the call metadata listed in Section 2 is kept. We keep the necessary content in the following cases:
| Case | When it applies | Maximum retention |
|---|---|---|
| You turn on debugging | You explicitly turn it on in the console or authorize it in a ticket | 7 days after debugging is turned off or the ticket ends |
| You save request history | Your own choice | Until you delete it |
| Serious security or illegal incidents | A real risk or a legal requirement exists, and the content is still being processed when the incident occurs | The period needed for security investigation, cooperation with law enforcement and dispute handling |
On routes labeled ZDR in the product, the third case applies only to call metadata, and we will not keep full bodies because of it.
3.2 Web Chat
Web chat is kept in your session history so you can return to it, until you delete it; chats in private mode are not saved to history. After you delete a session, we remove it from active systems within 30 days, and copies in backups are cleared within 90 days as backups rotate.
3.3 Clients
Local client sessions and configuration are stored on your device and managed by you. Third-party tools may store keys in plain text, so protect your devices, file permissions and backups. The client uploads necessary diagnostics only with your consent.
Before using one-click configuration, confirm which applications and configuration files will be changed and back up important data.
4. How We Use Information and Legal Bases
We use information to provide accounts, the API, web chat and creation, model routing, client configuration, billing, refunds and support; to protect system and account security; to handle disputes and unlawful conduct; to meet legal obligations; and to improve performance and the product using de-identified or aggregated data.
Our legal bases include performing our contract with you; our legitimate interests in security, fraud prevention and improving the Service; complying with legal obligations; and your consent where applicable law requires it. Marketing emails and non-essential website analytics are used only with your consent, which you can withdraw at any time.
5. Upstream Providers and Sharing
| Recipient | Data | Purpose |
|---|---|---|
| Upstream model providers | Inputs, files, parameters and necessary technical information | Model inference and content safety |
| Cloud, CDN and security providers | Encrypted data, IP and infrastructure logs | Hosting, delivery, protection and backup |
| Payment institutions | Orders, amount, currency and payment status | Collection, refunds and reconciliation |
| Email and support providers | Contact details, notifications and tickets | Service notices and customer support |
| Analytics providers | Consented page events and pseudonymous identifiers | Website analytics, never collecting prompts or full keys |
| Professional advisers | Information needed for disputes and audits | Legal, financial and security support |
| Competent authorities | Information within the scope of a lawful request | Meeting legal obligations |
APIONE does not sell personal information and does not share it for cross-context behavioral advertising. We bind the service providers that process information on our behalf through contracts, least-privilege access and audits. In a merger, acquisition or asset transfer, we will notify you and require the recipient to continue protecting your information under this Policy; if the purpose of processing changes, we will notify you again and obtain consent where required.
6. Team Workspaces and Referrals
- Once you join a team workspace, its Owners and Admins can see your usage, call logs, the keys you create and your administrative activity within that workspace. This does not make the content of your chats visible to them.
- After you leave a workspace, the records above remain with that workspace.
- When you take part in the referral program, the referrer can see the referred user's masked email, sign-up date and order amounts on the points page, and nothing else about them.
7. Where Data Is Stored and Cross-Border Transfers
APIONE's operating entity is located in the United States. Account, billing, support and call metadata is stored mainly on servers in the United States. When you call a model, inputs, files and necessary technical information are sent to that model's upstream provider and may be processed in the United States or other countries and regions; we disclose upstream providers and their main processing regions on the model pages.
If you are located outside the United States, your information will be transferred to the United States and to the locations of upstream providers for processing. For regions whose laws require a specific transfer mechanism, we use the appropriate mechanism, such as standard contractual clauses, or obtain your consent as required.
Where the product offers the relevant features, you can choose routes limited to specific regions, ZDR or no training. If no route meets your conditions, we will reject the request or ask you to adjust your settings.
8. Cookies and Similar Technologies
| Type | Purpose | Duration and control |
|---|---|---|
| Necessary cookies | Sign-in, security, replay protection and load balancing | For the session or up to 30 days; required for the basic service |
| Preference cookies and local storage | Language, theme and interface settings | Up to 12 months; can be deleted in your browser |
| Analytics cookies | Page visits, clicks and performance | Up to 13 months; used only with your consent, which you can withdraw at any time |
| Marketing cookies | Promotion attribution and ad effectiveness analysis (if used) | Used only with your consent, which you can withdraw at any time |
Declining analytics and marketing cookies does not affect the basic functions of your account, the API or web chat.
9. Data Security
APIONE uses measures such as HTTPS encryption in transit, password and key hashing, least privilege, access approval, operation auditing, environment isolation, vulnerability management, backups, disaster recovery and security incident response.
A full API Key is shown only once, when it is created, and is not displayed to staff in the everyday back office. Staff may access related content only to the minimum extent necessary, with authorization and an audit trail, when you request support, in a serious security incident, in a dispute or as required by law.
If a security incident may affect your rights, we will take remedial action and notify you and the relevant authorities within the period required by applicable law.
10. Retention and Deletion
- Retention periods for each type of information are set out in Sections 2 and 3. When they expire, we delete or anonymize the information.
- When you close your account, its API Keys stop working immediately. We delete or anonymize your account data and user content from active systems within 30 days, and copies in backups are cleared within 90 days; financial, tax, security and dispute records that must be kept by law are deleted when the relevant period ends.
- Unused top-up balances are handled under the refund rules of the APIONE Terms of Service.
11. Your Rights
| Right | How to exercise it |
|---|---|
| Access and obtain a copy | Account settings in the console, or a privacy request |
| Correct and complete | Account settings in the console, or a privacy request |
| Delete | Delete sessions, keys or profile data, or send a privacy request |
| Data portability | Send a privacy request; we provide it in a common machine-readable format |
| Withdraw consent | Cookie settings, communication preferences or unsubscribe links; takes effect immediately |
| Opt out or restrict processing | Send a privacy request, including opting out of targeted advertising, sale, and profiling for decisions with significant effects |
| Close your account | Account settings in the console |
| Appeal a refusal | Reply to our refusal email with "Privacy appeal" in the subject line |
Send privacy requests to support@apione.ai with "Privacy" in the subject line. We will respond within 45 days of receipt; for complex requests we may extend this by another 45 days and will tell you why. You may make a request through an authorized agent, and we will verify the agent's authorization and your identity.
We will carry out reasonable identity verification. If we refuse a request, you may appeal, and we will respond in writing within 45 days of receiving the appeal with the outcome and our reasons; if you are not satisfied, you may complain to your state attorney general or data protection authority. We will not deny you service, charge you a different price or provide a lower quality of service because you exercise these rights.
12. Minors
The Service is not directed at individuals under 18 or under the age of majority where they live, and we do not knowingly collect their personal information. If we discover that we have collected it by mistake, we will stop processing and delete it promptly. Parents and guardians can contact us at support@apione.ai.
13. Additional Information for Specific Regions
- European Economic Area, United Kingdom and Switzerland: you have the rights provided by the General Data Protection Regulation and local law, including the rights listed in Section 11 and the right to lodge a complaint with your local data protection authority. Our legal bases are set out in Section 4, and cross-border transfers rely on lawful mechanisms such as standard contractual clauses.
- California, Colorado and other U.S. states with consumer privacy laws: you have the rights listed in Section 11. We do not sell personal information, do not share it for cross-context behavioral advertising, and do not use it for automated decisions that produce legal or similarly significant effects.
- Users in mainland China: when you call models outside mainland China, your information is transferred to the United States and the locations of upstream providers. To the extent required by law, we will inform you of the overseas recipient's name and the purpose and method of processing, and obtain your separate consent.
14. Updates and Contact
We may update this Policy and will update the version number and effective date on this page. For material changes involving the types of information collected, purposes, sharing, cross-border transfers, training, retention or your rights, we will notify you by email or in-product message at least 30 days in advance; where the law requires renewed consent, we will obtain it again. Previous versions are available on request at support@apione.ai.
| Matter | Contact |
|---|---|
| Data controller | NICECLOUD LLC |
| Registered address | 1500 N GRANT ST STE R DENVER CO 80203 |
| Privacy officer | APIONE Privacy Team |
| Contact email | support@apione.ai (for privacy requests, security incidents and general support; please note the category in the subject line, such as "Privacy" or "Security") |
See also APIONE Terms of Service