Privacy contact and hosting
- Privacy requests
- biznesafterbiznessa@gmail.com
- API hosting location
- United States (USA)
1. What you ask us to process
A transformation consists of your JSON records or CSV file, an input schema, SQL instructions and an output schema. The API checks the request, calculates its price and collects payment before running the SQL transformation. If payment cannot be confirmed, SQL does not start. If processing fails after payment, the payment remains collected; automatic refunds are not provided.
The application uses a SQL engine to transform records. It does not require access to your source systems or ask for your wallet’s private key. Use synthetic or anonymised examples when evaluating the service.
2. Where processing takes place
The browser demo runs on your device. Its input is held in page memory; the application does not save it to browser storage. Copying or downloading a result puts it in your clipboard or downloads, which you control.
CSV preview on the website stays on your device until you choose Import CSV. In API mode, importing then sends the converted JSON records to the demo API. Direct CSV uploads send the file to the transformation API for validation, pricing and temporary storage.
In API mode, valid edits are sent to the API automatically after a short pause. Direct API use also sends your records and configuration to the server. Input and results may be held in server memory and temporary disk files while the transformation is handled.
Your JSON records and SQL text are not part of the blockchain transfer. Payment metadata is processed separately by the payment facilitator and blockchain network.
3. Temporary storage and file lifetime
Small unpaid requests are handled for a price quote without retaining the input in the staged-upload store. Large prepared uploads are held temporarily so that you can authorize processing without uploading the same data again.
If processing is not started, uploaded data is normally deleted within 15 minutes of upload, including when you do not pay. After a large transformation prepares a result, its input files are removed.
Paid results remain available to download for 10 minutes and are normally deleted within 15 minutes of creation. Opening an upload or result does not extend these times. Processing already in progress or a service interruption may delay removal.
4. Access and handling
Stored uploads and results use randomly generated resource URLs. Processing a staged upload requires confirmed payment. Downloading its saved result requires the same payment signature, without another charge. These controls do not replace your own authentication or confidentiality requirements: keep resource URLs and payment authorizations private.
The application sets successful paid responses to Cache-Control: no-store. Use the HTTPS service endpoint to protect data in transit. A local HTTP development endpoint does not provide the same transport protection.
The service has input, storage and execution limits. Large operations can still use significant resources, and a failed request may require a new submission. Download any result you need before its temporary lifetime ends.
5. Personal and confidential data
Send only the fields needed for the transformation. Do not submit passwords, wallet keys or recovery phrases. Before using personal, highly sensitive or regulated data, confirm the operator details, hosting, required safeguards and any necessary processing agreement.
Where the operator processes personal data on your instructions, you determine the purpose and lawful basis of that processing. This operational policy explains the implementation; it does not itself replace a data processing agreement or a provider-specific assessment.
See the privacy policy for payment records, infrastructure information and individual rights. If implementation or providers change, this notice should be updated to reflect the deployed service.