SENDFU TECHNOLOGY PTE. LTD.
Privacy
This page describes the data SENDFU currently handles when operating its website, account and access-review system, API credentials, and inference service.
- Public catalog and status endpoints can be read without an account. Inference routes require a SENDFU-issued Bearer API key.
- Registering an account does not itself approve inference access. Requests are reviewed before an API key is issued.
- SENDFU does not sell customer data.
Information we handle
| Category | Current data | Purpose |
|---|---|---|
| Account | Email address, name, company, password hash, account status, timestamps, and login-security records such as failed-attempt count and temporary lock time. | Create and secure the account, authenticate the user, provide the dashboard, and administer account status. |
| Access review | Intended use, requested models, expected usage, billing contact, review status, reviewer record, notes, and timestamps. | Review eligibility, approve or reject access, configure allowed models, and support service administration. |
| API credentials | API-key identifier, non-secret prefix, cryptographic hash, status, allowed models, quota, creation and last-use timestamps, and revocation state. | Authenticate API calls, enforce authorization and quota, display credential state, and support revocation. The complete key is shown once when issued and is not stored in plaintext by the account store. |
| Inference requests | Request content, selected model, request parameters, and generated response content are processed to complete the requested inference. | Operate SENDFU inference. SENDFU does not use API request prompts or generated responses to train SENDFU models or third-party models, unless a customer separately agrees to a specific opt-in arrangement. The current account and usage store does not persist prompt or generated-response text; request content still passes through the systems needed to execute and return the request. |
| Usage and service records | Account/API-key association, key prefix, model, streaming flag, request timestamp, response status, uncached prompt, cache-read, completion, and total token counts, together with the applicable rate-card snapshot and rated amount. | Display usage, enforce quota, investigate service issues, produce rated usage exports, and prepare rated invoice drafts. |
| Website and communications | Normal HTTP request metadata and information voluntarily included in business, support, incident, or privacy communications. | Deliver and secure the website, respond to enquiries, investigate incidents, and process requests. |
Processing and access
SENDFU operates the service and limits account, review, credential, and usage administration to authorized personnel who need it for those functions. Inference requests are processed through the technical systems required to provide SENDFU-operated inference. Model developers retain their separate model ownership; that ownership does not make them the operator of the SENDFU account system.
Service-provider details that SENDFU publicly identifies are listed on the Subprocessors page. Public status history contains service-availability samples, not customer inference content.
Retention and deletion
SENDFU currently retains account, access-review, credential-state, and usage records while they are needed to operate the account, enforce access and quota, provide usage records, address security or support issues, and meet applicable legal or accounting obligations. The current service does not promise one automatic deletion period for all categories.
Revoking an API key prevents its continued use but does not automatically erase associated historical usage records. Account closure or a deletion request is reviewed against operational, security, legal, and accounting requirements. Where deletion cannot immediately be completed, SENDFU may restrict the data or explain the applicable retention basis.
Security
Passwords are stored as salted password hashes. API keys are stored as cryptographic hashes with non-secret prefixes and state metadata. Browser sessions use signed cookies, and administrative access is separated from ordinary account access. No internet service can guarantee absolute security; report suspected credential exposure promptly and do not email passwords, API keys, or inference content.
Your requests
You may request access, correction, account closure, deletion, or information about retention. Send the request from, or identify, the account email and describe what you need without including credentials or inference content. SENDFU may need to verify identity and may retain information where required for security, legal, accounting, or dispute purposes.
Changes
SENDFU may update this page as the service or its actual data practices change. The date above identifies the current published version. Contract-specific terms may add obligations but do not silently replace this public description.