Overview
Nexynto Tools is a document productivity product by Nexynto Technologies. The repository does not establish a final legal-controller identity, registered address, jurisdiction, or data-protection officer. Those details require management and legal confirmation.
Local where supportedFiles selected in a browser-local workflow are designed to remain on the device.
Server when requiredConversions and security operations may upload files temporarily.
AI clearly identifiedRelevant content is sent to configured backend and AI services.
Retention by workflowExpiry and cleanup behavior depends on the feature and deployment.
Data we process and why
| Data category | When it is used | Purpose |
|---|---|---|
| File content and document metadata | When you select or upload a file | Run the chosen tool and produce the requested output. |
| Job and transfer metadata | Server conversion, security, AI and Transfer workflows | Track processing state, authorize access, deliver results, enforce expiry or revocation, and troubleshoot. |
| AI instructions, extracted text and results | Only in clearly identified AI-assisted features | Generate the requested analysis, summary, answer, mapping or suggestion. |
| Network and diagnostic information | When requests reach application or hosting infrastructure | Operate, protect and troubleshoot the service. Exact production logging and retention require deployment review. |
| Analytics events | When production analytics is enabled | Understand aggregate product usage and performance. |
| Support or privacy request information | When a user submits information through an approved contact channel | Respond to the request and maintain necessary correspondence. No public inbox is currently configured. |
Nexynto does not currently present a general user-account system in this frontend. If accounts are introduced, this policy must be updated before account data is collected.
Where processing occurs
Browser-local
Tools labelled “Runs in your browser” process the selected file with browser code or a browser worker and are designed not to upload document content to the Nexynto conversion API. The browser still requests application code and supporting resources.
Temporary server processing
Some Office, conversion, repair, extraction and PDF-security operations require the backend. These workflows upload input data, create job records and may store input/output artifacts until expiry and cleanup run.
Hybrid processing
A hybrid tool performs part of the work on the device and may send another part to the backend. Follow the disclosure shown on the exact tool rather than applying a platform-wide assumption.
AI-assisted processing
AI-assisted tools send relevant file content, extracted text, instructions and contextual evidence to Nexynto backend services and, when configured, OpenAI. AI is not described as local processing.
Inputs should be minimized to what the task needs. Generated output can be incomplete or inaccurate and must be reviewed before important employment, legal, financial, security or operational decisions.
Backend code contains temporary Nexynto-side expiry settings for AI artifacts. Provider-side retention, regional processing and contract terms are not established by this frontend and remain subject to deployment, contract and legal review. See the Subprocessors page.
Transfer and visual signing
Transfer
Transfer uploads files to server-managed storage and creates a public token plus sender-management credentials. The sender can select a supported expiry period, optional password, download limit and preview policy, and can revoke a transfer. Passwords are represented by a hash in backend evidence rather than stored as plaintext. Expired or revoked transfers depend on cleanup processes for artifact removal; limited tombstone records may remain temporarily.
Signing
The current Sign PDF workflow adds visual signatures, initials, dates and stamps in the browser. It does not represent certificate-based, identity-verified, or qualified electronic signing.
Retention and deletion
| Data / feature | Observed setting or behavior | Important qualification |
|---|---|---|
| Conversion and security jobs | Backend default expiry: 60 minutes | Expiry makes records/artifacts eligible for cleanup; it is not proof of deletion at an exact minute. |
| Nexynto AI artifacts | Backend defaults reference 60 minutes | Provider-side handling is separate and requires contract/configuration review. |
| Completed Transfer files | Sender selects 1, 3, 7 or 14 days | Revocation and expiry restrict access; cleanup must run to remove stored artifacts. |
| Incomplete Transfer uploads | Backend default cleanup threshold: 24 hours | Deployment configuration can change the default. |
| Transfer tombstones | Backend default: 30 days after cleanup | Used for bounded lifecycle records; production operation requires verification. |
| Analytics, logs and metrics | No complete retention schedule established | Operations and legal review required. |
| Support/privacy correspondence | No approved public channel or retention schedule established | Operations and legal review required before collecting requests. |
| Browser storage | Until cleared, overwritten or expired by the feature/browser | Users can clear site data through browser controls. |
Service providers and international processing
Confirmed source integrations are OpenAI for configured AI workflows and Vercel Web Analytics when the frontend runs in the relevant production environment. The active hosting, CDN, storage, database and conversion-provider inventory cannot be confirmed from this repository alone.
Provider processing may occur outside a user’s country. The applicable contractual transfer mechanism and provider regions have not been confirmed, so no specific safeguard or location is promised here. Deployment owners must complete the provider inventory and legal review.
Your choices and rights
Depending on applicable law and the role of the confirmed legal entity, you may have rights to request access, correction, deletion, restriction, objection, or portability of personal information. These rights are not identical in every jurisdiction and may be subject to legal exceptions.
You may also choose a browser-local tool where available, avoid AI features, revoke an active Transfer using sender credentials, or clear browser storage.
The site does not yet publish an approved privacy-request inbox or request portal. The Contact page records this operational gap and will provide the approved route once configured. Do not submit sensitive personal information through an unverified channel.
Security and limitations
Repository-visible safeguards include file/type validation, bounded processing, server-side secrets, hashed Transfer passwords, expiring access tokens, human approval for AI redaction, and result-verification steps in selected tools. Security also depends on deployment, access control, logging, monitoring and operational processes not proven by frontend source.
No internet service can promise absolute confidentiality, availability, accuracy or immediate deletion. Choose a workflow appropriate for the sensitivity of the document and keep an authoritative source copy.
Contact and policy changes
Use Contact Nexynto Tools to identify the support, privacy, legal or security request category. A monitored public submission channel still requires operations approval and is not simulated by this site.
This policy will be revised when verified providers, retention behavior, contact channels or legal-entity information changes. The effective date above is static and tied to this editorial version.
Need another trust document?