All documents
Vantemio
Products
- Technical documentation
- Studio Home
- Studio Cloud
- Pilots and pricing
- Market: specification
- Market: AI agents
- Donations
Legal
- Terms of use
- Privacy policy
- 1. Operator and scope
- 2. Categories and purposes
- 3. Bases and separate permissions
- 4. Providers and international processing
- 5. Retention
- 6. Requests and rights
- 7. YouTube and future social connections
- 8. Cookies and safeguards
- 9. Changes
- 10. Future TikTok-connector data
- 11. Future Cloud and system improvement
- 12. Account sign-in
- 13. Application to help build Vantemio
- 14. Wallets and WalletConnect
- 15. Donations
- 16. Swaps, bridge and trading access
- 17. News, Telegram and advertising
- 18. Processing with AI
- 19. Cookies and browser storage: summary
- 20. Age
- 21. Revision history
- Data deletion
- Editorial policy
Academy
Documentation › Legal
Vantemio Privacy Policy
Revision 0.21 · 10 November 2026
↓ Markdown↓ Download all documents
1. Operator and scope
The Vantemio operator, a private individual, is responsible for the project and personal information. For processing, access, correction, deletion and overseas-provider enquiries: support@vantemio.com, subject “Privacy”.
This policy covers vantemio.com, account sign-in, correspondence, applications and processing for Vantemio official channels. Authentication data and retention are described in the account sign-in section. Connected product features use the purposes and separate user authorizations described below.
2. Categories and purposes
| Data | Purpose |
|---|---|
| Email, role, task description and contact language | Application assessment and response |
| Optional name, experience and public EVM address | Relevant scenario assessment; a wallet address does not authorize transactions |
| Date, application identity, consent and terms revision | Enquiry and conditions accounting |
| IP and technical request details; hashed IP in the rate limiter | Website protection and abuse prevention |
| Random identity and retry-request digest in the browser | Duplicate prevention without retaining form answers |
| Correspondence | Questions, corrections and rights requests |
| Permitted official-account information, credentials, media, metadata and statuses | Authorized publishing and analytics |
Generator information is requested only when external generation is needed. The form is not intended for voice files, identity documents, private keys, recovery phrases or other people's secrets.
3. Bases and separate permissions
Information is processed for disclosed purposes with required consent or another applicable lawful basis. Collection is limited to what is necessary. An ordinary application does not authorize marketing, model training, account connection, publication or spending funds.
Application information is not sold or used by Vantemio to train models. Production materials go to external AI providers only as necessary for the agreed scenario and subject to their terms. New purposes are disclosed before related processing.
4. Providers and international processing
Cloudflare provides website delivery and protection, D1 stores applications and Turnstile protects the form. The mail provider processes correspondence. Publishing platforms receive authorized material and necessary metadata. Providers do not receive unrestricted usage rights at Vantemio's discretion; their roles and own terms are disclosed for the relevant feature.
Provider infrastructure may be in different jurisdictions. Before using an overseas provider, the operator identifies and discloses applicable countries, purposes and safeguards in the processing register. That list and overseas-processing practices are available from the responsible operator on request.
Information may be disclosed to meet a binding legal requirement. Hashed IP data is treated as protected technical information, not guaranteed anonymous data. Further information: Cloudflare Privacy Policy.
5. Retention
Applications are retained for no more than 90 calendar days from receipt, then deleted or irreversibly anonymized. Vantemio undertakes to provide scheduled cleanup independently of website traffic. Continued consideration does not automatically extend retention: any subsequent separate service establishes its purposes, terms and retention.
| Category | Maximum duration / event |
|---|---|
| Application, text and confirmation | 90 days from receipt |
| Ordinary enquiry correspondence | 90 days from the last substantive message |
| Website technical logs | 30 days, excluding a separately recorded incident |
| Rate-limit and duplicate-request records | 24 hours from creation |
| Browser technical identity | 24 hours from creation or earlier user removal |
| Disconnected-account tokens | Use stops on disconnection; deletion within 7 days or a shorter platform deadline |
| API analytics data | Refresh or delete at least every 30 days; shorter applicable revocation rules take priority |
| Backups | Do not extend the relevant category's maximum retention |
These periods govern Vantemio-controlled information; independent platforms handle received information under their own policies. A published video is not automatically removed after 90 days with an application.
Where specific records are needed for a contract, mandatory accounting, legal claims or incident investigation, only necessary information is retained on that basis. The operator records the purpose and separate duration; records are not reused for unrelated purposes. Contract-production retention is disclosed before accepting the corresponding materials.
6. Requests and rights
Individuals may request processing information, access, a copy, correction, deletion or consent withdrawal, subject to applicable legal limits. Write from the application email and include its number if available. Identity verification must be proportionate; do not send a passport without a separately justified request.
Concerns may be referred to the applicable privacy supervisory authority.
7. YouTube and future social connections
The official YouTube channel uses permissions necessary for connected publishing and analysis features. The Google Privacy Policy and YouTube rules apply. Google access may be revoked in permission settings; contact the operator about Vantemio-held data. Revoking access and removing an existing publication are separate actions.
TikTok connection requires disclosure of permissions, data categories and recipients before authorization. OAuth establishes the connection; posting requires the prescribed creator confirmation.
YouTube deletion covers all associated user API data, not only tokens. A deletion request, connection removal or consent revocation through Vantemio triggers deletion without undue delay and within 7 calendar days; token revocation is communicated to Google immediately. For revocation through Google settings, Vantemio also adopts a stricter internal maximum of 7 days from revocation, with regular authorization checks. This internal standard does not replace the distinct deadlines in YouTube API policies. The general 30-day target does not apply to these records.
8. Cookies and safeguards
The website does not use advertising trackers. Necessary Cloudflare mechanisms and browser technical storage support security and request processing. Additional analytics receives advance disclosure and any required choice.
Access to personal information is limited to necessary authority. Credentials are protected and excluded from public logs. In an incident, the operator assesses risk, limits harm and meets applicable regulator and individual notification obligations.
The website also uses Cloudflare Web Analytics for visit and page-performance statistics. Cloudflare adds its beacon to public HTML. The provider states that Web Analytics does not collect or use visitors’ personal data; Vantemio does not use these metrics for advertising personalization. This is separate from network security and application processing. Web Analytics overview · Metric collection.
The website policy’s 90-day period applies to applications and its specified categories, not automatic deletion of projects on the user’s computer. Home users manage local projects and backups. Activation, diagnostics and support data, recipients and retention are disclosed separately before release. Sending source media or project history for support requires a separate clear user action; credentials and passwords are excluded from that export.
9. Changes
The current policy is available on the website. Material changes to purposes and processing are disclosed before new use; new consent is requested when required. The actual effective date is recorded upon publication.
10. Future TikTok-connector data
This section defines processing when the TikTok connector is connected. Connection processes account identity, permissions and tokens; transfer processes selected video, caption, settings, creator confirmation, publish_id and status. Necessary information goes to TikTok and storage/delivery providers within the operation. Advertising and model training need a separate basis.
A temporary copy without confirmed transfer authorization is deleted within 24 hours of creation. Delivery copies are deleted within 24 hours after cancellation or completed transfer. For every started transfer, the delivery-copy lifetime is capped at 7 days from the first attempt. If no final outcome is established by then, the operation closes as unresolved; the copy is then deleted, the operator notified and automatic retry remains prohibited. A minimal authorization/outcome record is retained for up to 90 days after closing the operation, including an unresolved outcome, unless shorter platform rules require earlier deletion. The source Studio project has a separate agreed retention period and is not a temporary delivery copy.
Token refresh does not extend consent to new purposes. Revocation stops new actions and tokens follow section 5 deletion deadlines. The connector description and deletion procedure are accessible without login. TikTok follows its own policy.
11. Future Cloud and system improvement
Cloud envisages transferring the task, selected assets, settings, permitted account information and results to an isolated workspace in the shared core. Actual providers, countries, retention and access are disclosed before launch. Different customers’ projects and tokens do not become public.
Permitted de-identified technical statistics may improve tools after assessing re-identification risk. Personal content and social-API data are not used for training by default. Such use requires a separately disclosed basis, necessary rights and consent, and compliance with platform restrictions. Declining optional training participation does not remove paid core functionality. Website applications remain excluded from training. Cloud scope.
12. Account sign-in
When account sign-in is available, Google authentication uses your Google account identifier to recognise your account; the server checks the identity token and email verification status. We do not request access to Gmail, Drive or YouTube for sign-in. Wallet sign-in records the public wallet address and verifies a one-time message. We never request your recovery phrase or private key. Authentication data is not used to train content-generation models.
A secure, HttpOnly session cookie lasts up to 12 hours; the server stores a hash of its random token. Sign-in challenges expire after five minutes and can be used once. Expired challenges and sessions are removed during subsequent authentication activity. Account identity records remain until deletion is requested. Signing out revokes the current session. Deleting an account removes its sign-in identity and all its sessions; separate applications and immutable blockchain records are handled as described in the data-deletion policy.
To prevent repeated unsuccessful sign-ins, we keep a keyed hash of the source IP and a consecutive-failure counter. Four failed identity checks in a row block new sign-ins for four hours. A successful sign-in clears the counter. The sign-in database does not store the raw IP for this purpose. Expired block records are removed on the next check; earlier failures remain until a successful sign-in or a completed block.
13. Application to help build Vantemio
The “Help build Vantemio” page collects your name, contact email, chosen role, skills, experience, proposed contribution, motivation and preferred language. Social profiles, portfolio and availability are optional. The application is linked to your internal account identifier and sign-in provider; wallet sign-in also records the public wallet address. You enter your contact email yourself; Google sign-in does not automatically verify that address.
The purpose is to get acquainted, review potential participation and contact you individually about your application. The project operator reviews applications. Visitors cannot access them; answers are not published or used for advertising or AI training. Cloudflare D1 stores the application and Turnstile protects submission. Your browser stores only a random request identifier and a digest for retry protection, for up to 24 hours.
This separate application has a review period of 365 days from submission or the operator’s latest status change. Expired applications are excluded from review and deleted during form-data cleanup. The operator also performs cleanup when reviewing applications. To withdraw, correct or request deletion, contact support@vantemio.com with your application number. If collaboration follows, its documents and processing periods are agreed separately.
Deleting the sign-in account revokes sessions and removes the application’s link to that account. Deleting the application itself requires a separate request to the operator. The 90-day period above applies to pilot applications and does not replace this contribution-application period.
14. Wallets and WalletConnect
When you connect a wallet through WalletConnect, your browser connects to WalletConnect (Reown) infrastructure: it relays requests between the site and your wallet, verifies the domain and shows the wallet list. If you choose Coinbase Wallet, a Coinbase service is used. These providers receive your IP address and technical connection data and process them under their own policies.
Vantemio stores the public wallet address, the sign-in method and the time. A wallet address is not anonymity: a public transaction history on the blockchain is linked to it.
15. Donations
| Data | Purpose |
|---|---|
| Creator profile: name, channels, payout address | Showing the creator page and receiving support |
| Donation record: network, transaction hash, sender and recipient addresses, token, amount, fee, time | Accounting and donation history for the creator |
| Optional donor message | Shown in the creator's alert; may be visible to stream viewers |
| Overlay access key | Showing alerts on stream; it expires and can be revoked by the creator |
A blockchain transaction is public and cannot be deleted. The record kept by the site can be deleted on request — see data deletion. Donations currently work on a test network only.
16. Swaps, bridge and trading access
To show a route and a quote, the Vantemio server sends the provider LI.FI the selected networks, tokens, amount and wallet address. The Vantemio DEX trading terminal is connected to the EVEDEX exchange through its API: terminal pages contact EVEDEX servers from your browser for market data and, once order submission opens, will pass the exchange your wallet address and the parameters of the orders you sign. EVEDEX then receives your IP address and technical request data and processes them under its own policy.
When you follow a referral link, the partner receives the code "vantemio" and processes your data under its own policy from then on. Vantemio does not receive your documents, balances or trade history from partners.
17. News, Telegram and advertising
You can read the news without an account. Discussions in the Telegram channel are moderated automatically: Telegram passes a message to our server, the server answers with a decision straight away and does not store the message. Telegram itself processes data under its own policy.
For an advertising placement request we process the advertiser's contact details, the ad material and payment information.
18. Processing with AI
News and analysis are prepared by AI from public sources; reader data is not sent to the models. Applications and forms are reviewed by a person and are not used to train models. Local models run on Vantemio hardware. Cloud models receive production material only, and only as much as the task needs.
19. Cookies and browser storage: summary
| What | Why | How long |
|---|---|---|
| Passport session cookie (HttpOnly) | Keeps you signed in | Up to 12 hours |
| Cloudflare and Turnstile technical cookies | Protecting the site and forms | Under Cloudflare's rules |
| Browser storage: interface settings and wallet connection state | Convenience and reconnecting your wallet | Until you disconnect the wallet or clear it |
| Repeat-submission identifier | Preventing a form from being sent twice | 24 hours |
The site has no advertising or cross-site trackers. Cloudflare Web Analytics works without cookies.
20. Age
A Passport account and the digital-asset features are for people aged 18 or over (section 24 of the Terms). Vantemio does not ask for your age or date of birth at sign-in and does not knowingly collect data from minors. If we learn that a minor has created an account, the account and its data are deleted. A parent or guardian can write to support@vantemio.com.
21. Revision history
- 0.21 · 10 November 2026. Added section 20 on age. Section 16 now states which data the EVEDEX exchange receives when connected to the Vantemio DEX terminal. The revision history moved from section 20 to section 21.
- 0.20 · 10 November 2026. The sections "Account sign-in" and "Application to contribute" received numbers 12 and 13; their text is unchanged. Added sections 14–20: wallets and WalletConnect, donations, swaps and trading access, news and Telegram, processing with AI, cookie summary. The text of sections 1–11 is unchanged.
- 0.19 · 16 October 2026. Previous revision.