Recto

Privacy & data

Understand Recto’s service, data handling and purchase rules.

Updated: 2026-11-10

Operator and scope

This notice is provided by Yihua Zheng (郑义骅) for the Recto website, account and plugin cloud service. Use the contact details below to request access, correction, deletion or account closure.

Documents sent for processing

Starting a conversion uploads your selected PDF to the Recto backend. Translating an already converted document sends structured text; translating existing Markdown sends the text of the selected file. Selecting a file does not automatically upload the rest of your vault.

Content may be passed through Recto to third-party services for parsing, summaries or translation. Providers may change, and processing may occur outside your country. This notice does not promise zero retention or exclusion from training by third parties. Contact us to check processing conditions before sending documents with special confidentiality requirements.

Accounts, payments and website visits

Account and service data includes email, sessions, task type and status, page or character counts, credit use, processing times, orders and payment status. It supports authentication, billing, delivery and support. Passwords are entered on the browser account page, not in the plugin. Payments use third-party payment services; the plugin does not collect or store card numbers.

If you sign in with Google or GitHub, we request only the minimum sign-in permissions and receive that account's unique ID, verified email address and display name to identify you. If the email matches an existing Recto account, you sign in to that account. We do not store access tokens issued by Google or GitHub and do not read your other data on those services. Sign-in sets a strictly necessary cookie that prevents forged sign-in requests and expires within 10 minutes.

These public pages do not set analytics or advertising cookies or load third-party tracking scripts. Website requests transmit your IP address and browser request information; hosting infrastructure may retain access logs for operations and security. Account sessions and payment services involve their own necessary processing.

Operation diagnostics and feedback

After cloud processing is enabled and while signed in, the plugin silently sends structured diagnostics for conversion, translation and recovery. These include associated task IDs, versions, operating system, timings, numeric sizes and stable error codes. They exclude document text, PDF copies, filenames, local paths, passwords, tokens and raw request content. They are not forwarded to processing providers and do not track reading activity.

The feedback form stores the message, category, account and time you submit. It does not automatically attach papers or logs. Do not include secrets, payment credentials or unnecessary personal information in feedback.

Retention and deletion

Task files include uploaded documents, structured text, intermediate files and result packages. They remain available for 24 hours after completion or failure; downloading or acknowledging a result does not extend that window. Files are private. Authorized administrators may download them during the window for support verification, with a stated reason and an audit record.

File access stops at expiry. Scheduled cleanup retries failed deletions, so physical deletion may be delayed during outages. Cancellation requests immediate cleanup. Uploads never started expire after 24 hours; active processing is not deleted simply because of upload age. Retrying within the failure window starts a new retention window when the attempt ends.

  • Diagnostics are retained for 30 days, then become unavailable on the server and are removed by scheduled cleanup. Local pending reports also expire.
  • Account records, credit ledgers, orders and necessary service metadata are retained for billing, verification and support. Records that must be kept by law may remain after account closure.
  • Feedback is kept while needed to resolve the issue and improve the service; it is deleted when its associated account is deleted.

Your choices and requests

You can leave cloud processing disabled and keep reading locally saved documents. There is currently no self-service account deletion button. Contact support for account closure, access or deletion requests. We verify account ownership and explain the available action and any necessary retention.

This notice does not replace third-party services’ policies. Updates are dated. You control files already saved in your local vault.

Contact support

Yihua Zheng (郑义骅)

j4756237@gmail.com

Do not submit account, order or document information in public GitHub issues.