Site policies

LANCER / SITE POLICIES

Privacy Policy

Effective and updated: 2026-10-03

What this personal Site receives, why it is used, and how you can manage it.

On this page01 / Who operates this Site02 / Browsing and basic records03 / Likes and public comments04 / Cookies and browser storage05 / Research inputs and processing06 / Model providers and locations07 / Your API key08 / How long records remain09 / Uses and necessary disclosures10 / Requests and policy changes

01 / Who operates this Site

lansiyao.com is a personal Site operated by Siyao Lan (兰斯尧 / Lancer). This policy covers public browsing, likes, comments, view counts, and the research tools offered here. It was updated on 3 October 2026. Privacy enquiries can be sent to lancer20060105@gmail.com.

02 / Browsing and basic records

Public pages can be read without a Site account. The Site records aggregate views and uses a pseudonymous first-party identifier for deduplication. Hosting and media delivery providers receive request information such as an IP address and browser details and may retain operational or security logs under their policies. The Site does not use third-party advertising pixels or a third-party analytics service.

03 / Likes and public comments

The Site uses Waline for anonymous comments, reactions and reading statistics. Comment names, text, dates and replies are public. The server may retain an IP address and browser details for abuse prevention and administration; these details are not shown in the comment list. Nicknames and reaction preferences may remain in browser storage. Accounts are optional: registered users may provide an email address and have a password hash stored on the server. Administrators can moderate or delete comments. Older interaction records remain in a private migration archive; previous hosting-account ownership may not carry over to the new system.

04 / Cookies and browser storage

The necessary visitor cookie can last up to one year for preserved Site interactions. Theme and language preferences are saved in your browser. Waline stores comment preferences, draft text, reaction state and, for signed-in users, a login token. Article reading deduplication uses a 30-minute browser record. Research task identifiers use sessionStorage and a signed research guest cookie lasts seven days. Clearing these values can reset preferences, login state or access to a private task.

05 / Research inputs and processing

Research tools process the topics, excerpts, instructions and files you submit to perform the requested task. Selected topics or excerpts and necessary prompts are sent to your chosen model provider. The website and API are hosted on Vercel, persistent interaction and task records use Supabase, and the private execution service runs on Render in the United States. Public media uses Alibaba Cloud OSS/CDN. Private research inputs are not placed in the public media bucket or publicly showcased. Attachments use an authenticated temporary upload process before being passed to the private engine.

06 / Model providers and locations

Available providers include OpenAI, DeepSeek, GLM, Kimi, Anthropic, Gemini, and MiniMax. Your selection determines the provider receiving model requests; hosting and processing may involve China, the United States, or other regions. Hosts and providers may retain logs under their own policies. The webpage does not provide private backend source code. Model providers receive the prompts and context needed to perform a task, so consider their data policies before submitting confidential material.

07 / Your API key

Your API key is used only in memory and transmission for the requested task. It is not written to browser persistent storage, the Site database, staged attachment tables, or downloadable reports. Your chosen provider receives the credential required for authentication. Keep your key private, configure suitable spending limits and revoke it through that provider if you suspect exposure.

08 / How long records remain

Research tasks and results remain accessible for seven days from creation. Expired task records are cleaned up when new work is admitted. Temporary attachment contents and metadata expire within 15 minutes; confirmed admission shortens this period to one minute. Expired uploads are removed during subsequent upload activity. Keyed IP hashes and upload counts remain until the end of the UTC hour for abuse prevention and are then eligible for cleanup. The private engine’s filtered task cache lasts up to 24 hours, with raw processing files removed during cleanup. Expiry does not imply immediate physical deletion. Hosting and model-provider logs follow their respective policies.

09 / Uses and necessary disclosures

Information is used to provide requested features, maintain reliable operation, address abuse, and respond to enquiries. The Site does not collect website payments or operate advertising pixels or a marketing subscription list. Information may be disclosed where an applicable legal duty requires it or where necessary to address a concrete security incident. Submit only material you are entitled to process, and avoid unnecessary personal or confidential information.

10 / Requests and policy changes

Contact lancer20060105@gmail.com to request access, correction, or deletion, or to raise a privacy concern. Include the relevant page, comment, or task identifier and the outcome you seek. Only information reasonably needed to verify the request will be sought. Verified requests will be handled promptly. If applicable law requires retention or a technical constraint temporarily prevents deletion, the reason will be explained and further processing restricted as appropriate. Material changes will appear here with an updated date.

For privacy, copyright or policy questions, contact Lancer: lancer20060105@gmail.com