Important Notice
This is a technical API testing tool that provides a convenient graphical interface for API calls. This tool does not provide the underlying AI model capability; outputs are produced by the third-party API services you choose and their upstream model providers. To complete a call, request content and the relevant API Key are either sent directly from your browser to the third-party API service or temporarily relayed through YingTu endpoints, depending on the selected route. When a relay route is used, the relay layer does not independently archive live requests as a content library or manually review them. History and experience-analytics handling are described below.
1. Information We Collect
YingTu collects minimal information to provide API testing functionality:
1.1 Information You Provide
- API Key: Your third-party API service API Key (stored only in browser localStorage)
- Test Inputs: Test parameters you enter (used temporarily during API calls)
- Reference Files: Files you upload (used temporarily during API calls)
- Google Account Information: When you choose to sign in, the account identifier, name, email, and profile image provided by Google are used to establish your session
1.2 Automatically Collected Information
- Test History: In the current release, your API test history is stored in browser IndexedDB
- Language Preference: Stored via NEXT_LOCALE cookie
- Experience and Diagnostic Data: Microsoft Clarity may process page visits, clicks, scrolling, device, and performance information to help identify experience issues
2. How We Use Information
We use collected information to:
- Send test requests directly to the selected third-party API service or temporarily relay them through YingTu endpoints, depending on the route
- Maintain your test history in your browser
- Remember your language preference
- Analyze aggregate usage and diagnose page-experience issues
3. Data Storage
Important: API Keys are persisted only in your browser; in the current release, generation history stays in the current browser; call data is transmitted temporarily while a request is running.
- API Key is stored in localStorage
- Test history is stored in IndexedDB
- Language preference is stored in a cookie
- When you generate content or query a task, the relevant API Key, test input, and reference files are sent directly from your browser to the third-party API service or temporarily relayed through YingTu endpoints, depending on the route
- Account cloud history is not enabled in the current release. When a relay route is used, the relay layer does not independently persist API Keys or live request bodies in a server-side database
4. Third-Party Services
This tool involves the following third-party services:
- Third-party API Services: Depending on the selected route, this tool requests the configured third-party API service directly from your browser or forwards the test request through YingTu endpoints. This includes services such as laozhang.ai. These services may further call their upstream providers. Please review the privacy policy of the third-party service you use.
- Vercel: Website hosting. Vercel may collect standard server logs.
- Microsoft Clarity: Used for aggregate analytics, heatmaps, and session-experience diagnostics. It may process device, page, and interaction information and use analytics-related browser storage. Microsoft's privacy statement governs its processing.
5. Cookies
We use cookies or similar browser storage required for language, sign-in, and experience analytics:
- NEXT_LOCALE: Stores your language preference
- Authentication cookies: Maintain your session after you choose Google sign-in. The Google sign-in flow may also use Google's required cookies or FedCM capabilities
- Microsoft Clarity: May use first- or third-party cookies to connect page visits and produce aggregate analytics. Behavior can vary by region, browser settings, and Microsoft consent mode
YingTu pages do not display third-party targeted ads. Clarity-related browser storage is handled by Microsoft under its privacy statement and is used for product-experience analytics.
6. User Rights
You can at any time:
- Access Your Data: View stored data in your browser's developer tools
- Delete Your Data: Clear browser data or use the "Clear All" feature on the history page
- Remove API Key: Delete it from the settings dialog
- Manage Analytics Storage: Manage or clear related cookies and site data through your browser privacy settings
7. Data Security
Security measures we implement:
- All transmissions are encrypted via HTTPS
- API Keys are sent only when you start the corresponding call and are used only to request or temporarily relay to the selected third-party API service
- Account cloud history is not enabled in the current release, and API Keys are not persisted in a YingTu server-side database
8. Children's Privacy
This tool is not intended for children under 13 years of age. We do not knowingly collect information from children under 13.
9. Changes to This Policy
We may update this privacy policy from time to time. Updated policies will be posted on this page with an updated "Last updated" date.
10. Contact Us
If you have any questions about this privacy policy, please contact us:
- Email: [email protected]
- Telegram: @laozhang_cn