Privacy Policy

This privacy policy applies to axopedia by Aetherisz, covering encyclopedia search, article retrieval, cited answers and the AXO model family. The information involved depends on the features you actually choose to use.

The following chapters explain the general practices and the product-specific context. A statement about a feature that is not yet available does not mean information is already being collected for it.

This policy describes personal information involved in the identified Aetherisz service and its enabled features. It distinguishes account information, content, operational records and optional interactions so that you can understand the purpose of each category.

Product-specific chapters apply when you use that product. A planned feature is not a statement that collection is currently taking place. Third-party websites and independently operated applications have their own policies.

You may provide account details such as a name, email address and profile image, together with the content or preferences needed for a requested feature. Support messages, feedback and transaction references are additional information you choose to submit.

Only provide information you are entitled to share. Avoid entering passwords, API secrets, payment-card numbers or unrelated sensitive records into prompts, chat boxes or general support messages.

A sign-in provider can supply the identity information and authentication result needed to establish your account, depending on the method and permissions you select. We may process account identifiers and session information to maintain access.

The provider also processes information under its own notice. Removing a provider account does not necessarily remove an Aetherisz account, and signing out does not by itself delete records previously submitted.

The content needed for a feature may include prompts, documents, images, code, queries and generated results. Some content can contain personal information about you or other people even if the feature is not designed specifically for personal records.

Review the selected feature and sharing settings before submitting material. Uploading a file can expose hidden metadata or embedded personal information in addition to what is visible on screen.

Operating the service involves technical records such as request times, route or feature identifiers, response status and browser or device characteristics. Network infrastructure may process an IP address when receiving a request.

These records support delivery, diagnostics, access control and abuse investigation. They should not be understood as an assertion that every device signal is collected on every request or that every raw value is kept indefinitely.

Purchases can generate transaction references, amounts, currency, billing details and payment status. A payment processor handles the financial information required for the payment method and may perform its own fraud or legal checks.

Do not send full card details to Aetherisz support. We need appropriate transaction records to reconcile balances, investigate disputes and satisfy applicable accounting requirements; payment records are distinct from the contents of your prompts.

Information is processed to provide the feature you request, manage your account, handle payment and support, maintain reliability and protect users against misuse. The information needed for one purpose may not be necessary for another.

A materially different purpose should be explained and supported by an appropriate lawful basis or required permission. General acceptance of terms is not unlimited consent to unrelated processing.

Processing must have a lawful justification under the rules applicable to the activity. Depending on the context, this can involve the permissions you give, permitted uses connected with a requested service or compliance with a legal requirement.

We consider applicable Indian data-protection requirements, including the Digital Personal Data Protection framework as relevant provisions take effect, alongside other laws that may apply. A policy citation is not a certification or a claim that every regulatory requirement applies identically to every feature.

Cookies, browser storage or similar mechanisms may be needed for authentication, session continuity, security and remembering essential preferences. Blocking or clearing them can prevent sign-in or remove a saved choice.

A browser session record is different from stored account content. Clearing your browser does not delete server-side records, and closing a tab does not necessarily end an authenticated session.

Where optional analytics or marketing choices are offered, the related permissions should be explained separately from storage required to operate the service. Review the choice presented to you rather than assuming all technologies have the same purpose.

You can use available preference controls or contact support about withdrawing an optional permission. Withdrawal may not affect processing that already occurred lawfully or information that must be kept for another lawful reason.

Protection can involve challenge responses, interaction timing, session identifiers, request outcomes and browser characteristics. Relevant security records may be associated with an account or integration key to evaluate repeated abuse or investigate a false positive.

A hashed identifier can still permit correlation and may remain personal information. Challenge expiry and event retention are different: a token can expire quickly while an event remains necessary for security review.

Automated risk evaluation can require a challenge, limit a request or refuse access. These are technical protection decisions rather than statements about a person’s identity, honesty or eligibility for a legal benefit.

If a genuine interaction is blocked, contact support with the browser, approximate time and a non-secret reference. We may need context to review the problem, and cannot disclose details that would undermine the protections.

Running the service can require hosting, identity, email, payment, model-processing and support providers. Relevant information is shared where needed for the function being delivered, subject to applicable arrangements and duties.

A provider’s participation does not authorise unrelated publication of your content. We do not describe personal information as a product for sale; disclosure for operations or a legal request is different from selling an audience list.

When you request an AI feature, selected prompts and context may need to be sent to the model provider used by that feature. Provider processing can vary by offering and agreement, so do not infer a blanket training exclusion or confidentiality guarantee from this policy alone.

Minimise private information, assess the feature before submitting regulated data and obtain permissions required for information about others. A free demo is not an appropriate place to test confidential credentials or sensitive case files.

Information you intentionally share with teammates or publish through a public project may be seen, copied or retained by the recipients. Check access before sharing and remember that revoking permission cannot always remove independent copies.

External links, citations and payment pages lead to independently controlled services. Those services may receive ordinary browser request information and use their own cookies; their notices govern their separate processing.

Information may need to be preserved or disclosed in response to a valid legal requirement or to address a credible threat to users or the service. Requests should be evaluated for authority, scope and necessity rather than treated as unlimited access.

If an organisational transaction changes who operates a service, applicable notice and data-protection duties continue. This policy does not grant a future operator unrestricted rights to use information for unrelated purposes.

Service providers can operate infrastructure in more than one country. The processing location may depend on the feature and provider, and a Made in India statement is not a promise that all information stays within India.

Cross-border processing must be considered against applicable restrictions and safeguards. Do not use these public terms as evidence of a guaranteed country-specific hosting arrangement; such a commitment requires an expressly identified offering or agreement.

Security relies on appropriate access restrictions, protected connections, credential handling and operational controls suited to the information and feature. We seek to limit access to authorised systems and people with a legitimate need.

No online service can promise complete protection against every incident. This policy does not claim a particular audit certification, universal end-to-end encryption or a tested recovery capability that has not been expressly established.

Information is kept according to the purpose for which it is needed, applicable legal obligations and justified investigation needs. Account records, content, payment records and security events can therefore have different retention requirements.

We do not invent a single deletion deadline for every system. Where information is no longer needed, removal or appropriate de-identification should follow the relevant operational process. Material required for a dispute or legal hold may need to remain longer.

Deleting an account or a file can involve identity checks, shared-content ownership and records that must be retained lawfully. Backups and third-party systems may not be updated at the same instant as an active account interface.

A request should explain the record or account concerned so that its scope can be assessed. We will explain relevant limitations rather than promise immediate erasure of every copy or of records controlled by another organisation.

You may ask about information associated with your account, request correction of inaccurate details and seek deletion or another available remedy under applicable law. Where supported, account tools can help with straightforward changes.

Rights depend on the law and the type of information involved. A request may be limited where responding would disclose someone else’s information, compromise security or conflict with a lawful retention duty.

Before disclosing information or changing access, we may need proportionate evidence that the request comes from the account holder or an authorised representative. We should not request more identifying information than needed for that check.

Parents, guardians and business administrators may need to establish their authority. An email claiming to represent another person is not by itself permission to receive that person’s private records.

Children’s use must comply with the age, parental-permission and other protections required by applicable law. Adult eligibility, children’s consent and product-specific restrictions are not interchangeable requirements.

If you believe a child’s information has been submitted without the required authority, contact support with a minimal description. We will assess the circumstances before taking a deletion or access action that could affect the child or another account.

We may use account contact details for sign-in, billing, security and important service notices. Optional promotional communication is distinct from these essential messages. Support conversations can include the information you supply and the records needed to resolve the case.

An automated support assistant can be incorrect; verify consequential guidance with a human. Never submit secrets to support chat. Privacy complaints can be raised through the contact channel, with handling subject to the timelines and duties that actually apply.

A suspected information-security incident may require investigating affected records, restricting access and communicating with relevant parties. Whether a notice is required, and its content and timing, depends on the facts and applicable law.

We do not promise that every technical anomaly is a confirmed personal-data breach. If you suspect your credentials are exposed, revoke them where possible and contact support without including the secret itself.

Changes to features, providers or law can require revisions to this policy. The displayed update date identifies the published version. Material changes should be communicated as appropriate, and any new permission required by law must be obtained rather than assumed.

Send privacy questions, complaints and rights requests to supportaetheris@gmail.com. Use only enough information to identify the issue and ask for an appropriate channel before supplying sensitive documents. This contact is not a claim of a named statutory officer or professional certification.

Queries, article identifiers and contextual prompts can reveal interests or personal circumstances. Enter only the information needed for your question, and avoid using the search box to submit private case files or credentials.

Requests to external knowledge services may include the search terms or article identifiers required to retrieve a result. Public source content does not make a user’s private query public.

Opening a citation takes you to another publisher with its own cookies and privacy practices. Aetherisz does not control those sites or their collection of browser and network information.

Reports about incorrect articles may include the query, response and references you choose to send. Redact private information unrelated to the correction.

Key identifiers and request outcomes support abuse prevention and service diagnostics. Revocation affects future access; retained operational records are governed by the retention chapters of this policy.

Searches about health, politics or other sensitive subjects should not include identifiable details unless the feature genuinely requires them and you have authority to submit them.