Skip to content
ultra endpointsBack to the API ↗

YOUR DATA, EXPLAINED

Privacy policy

How Ultra Endpoints handles website information, API data and payment metadata.

Last updated 15 October 2026

ON THIS PAGEPrivacy contactInformationPurposeProvidersRetentionYour rightsData processing policy ↗

Privacy contact and hosting

Privacy requests
biznesafterbiznessa@gmail.com
API hosting location
United States (USA)

1. Information involved

The website delivers pages and static assets. Our application does not include advertising trackers, analytics scripts or advertising cookies. Hosting and access providers may process connection information or use essential cookies to deliver and protect the service.

The browser demo processes records on your device. CSV imports are previewed and converted to JSON locally. API mode and direct API requests send the submitted records, schemas and transformation instructions to the API. Providing these records is necessary to produce the requested transformation.

Paid requests also involve wallet addresses, the amount, network, transaction identifiers and payment authorizations. A private wallet key is not required by the API; never include private keys or recovery phrases in your records.

2. Why information is processed

Records and instructions are used to validate and perform your requested transformation and return its result. This service runs a SQL transformation engine; submitted records are not sent to an AI model for inference or training by the application.

Connection and diagnostic information may be processed to operate the service, investigate errors and prevent misuse. Payment information is used to verify and settle the requested payment.

Where the operator acts as a controller and GDPR applies, providing the requested service and payment processing rely on performance of the service contract; proportionate security and diagnostics rely on legitimate interests in operating a reliable service. Applicable legal obligations may require keeping transaction records.

3. Providers and public payment records

Hosting and network providers necessarily handle traffic to deliver the website and API. The configured payment facilitator receives payment requirements and authorizations, including wallet and resource metadata. The application does not send your submitted JSON records or SQL text to that facilitator.

Blockchain payments create public, persistent records. Wallet addresses, amounts and transaction details can remain publicly visible after temporary API files are deleted. Deleting a file does not erase a blockchain transaction.

The API hosting location is listed in the operator details above. Payment and network providers may operate in other countries. Appropriate provider terms and any required international-transfer safeguards must be confirmed before personal data is submitted.

4. Retention and deletion

If processing is not started, uploaded data is normally deleted within 15 minutes of upload, including when you do not pay. Input working files are removed once processing finishes.

Paid results remain available to download for 10 minutes and are normally deleted within 15 minutes of creation. Processing already in progress or a service interruption may delay removal.

Connection logs, infrastructure records and public payment records are separate from temporary payload files. These deletion times do not apply to them. Their retention depends on the operator and provider configuration and applicable legal requirements.

5. Your choices and rights

Use the browser demo when you want to keep sample input local. Remove unnecessary personal data before sending an API request, and only submit data you are entitled to process.

Where GDPR applies, you may request access, correction, erasure, restriction or portability, and object to processing based on legitimate interests, subject to the applicable conditions. You can also complain to your competent data protection authority. Contact the operator using the privacy address above; verification may be needed to protect other users’ data.

If you send personal data on behalf of another person or organisation, you remain responsible for your lawful basis and instructions. Agree any necessary data processing terms with the operator before using the API for that purpose.

Read the European Commission’s explanation of individual data protection rights.

ULTRA ENDPOINTS / YOUR DATA, EXPLAINED.
Privacy policyData processingHome ↗