01 / Who operates ARCHER
ARCHER is operated by Jomari David Perez (Archer), Philippines. It is currently a personal desktop tool within VIRA for connecting the operator's own social accounts, uploading or publishing the operator's content, and viewing account and video analytics. It is not a public service for other creators. Contact: inquire@archerperezz.net.
02 / Information processed
- Account connection: platform account identifiers, display name, username and profile information; OAuth access and refresh tokens, expiry information and granted permissions. App credentials are stored in the desktop configuration.
- Content: selected videos and images, captions, local file paths, posting options, scheduled times, upload status, post identifiers, links and error records. Media imported or reframed by VIRA can create additional local copies.
- Analytics: account totals such as followers, following, likes and video counts; video titles or descriptions, covers, links, timestamps and available views, likes, comments and shares.
Available fields depend on the connected platform, permissions granted and API availability. ARCHER does not need the account's TikTok password; account authorization takes place through TikTok.
03 / TikTok permissions and purposes
The current implementation requests the following permissions. A request does not mean TikTok has approved or granted every permission.
user.info.basic: identify the connected account using basic profile information.user.info.profile: display additional profile details such as username.user.info.stats: display account statistics.video.list: retrieve the connected account's available video list and statistics.video.upload: upload selected videos to TikTok for completion through TikTok when available.video.publish: request direct publishing when TikTok permits it.
These data support account connection, authorized content uploads, scheduling, publishing status, troubleshooting and performance review. Actual use remains subject to TikTok's authorization, account settings and app restrictions.
04 / Storage and security
Connection credentials and account tokens are stored in local JSON files in VIRA's backend data directory. Posting records and cached analytics are also stored locally; media stays in the desktop's selected source, upload or output locations. The current storage writer does not provide application-level encryption for these JSON files. Protection therefore depends on the computer's account permissions, operating-system security and any disk encryption the operator has enabled. No system can guarantee absolute security.
ARCHER's social-management routes require an authenticated VIRA administrator. The public portfolio and these policy pages are separate from the desktop integration: publishing these pages does not upload the private credential store or expose a public account-connection service.
05 / Transfers and third parties
Connecting accounts, retrieving analytics and uploading content transmit relevant information to the connected platform over its APIs. TikTok handles that information under its own Privacy Policy. Other connected social platforms apply their own policies.
VIRA's optional AI-assisted workflows may send instructions, captions, analytics or other selected context to the model service used for that task. Desktop storage does not mean every workflow is offline. The operator should review what is included before using an external assistant. The public pages are delivered through Cloudflare, which processes ordinary network request information to provide hosting and security. Email enquiries are handled through the operator's email services.
06 / Retention
There is currently no fixed time-based automatic deletion schedule for tokens, cached analytics, posting records or local media. The analytics cache's refresh interval controls freshness, not deletion. Posting history is limited to the latest 300 records when that store is updated; notification events are limited to the latest 100 when added. Copies in backups, logs, chats, source media and generated files may remain independently.
Data remains until replaced, trimmed by those record limits or manually removed by the operator. This policy does not promise an automatic 30-day or other timed purge.
07 / Disconnect, revoke and delete
- In VIRA's Automate account controls, disconnect TikTok to remove its saved account connection, including the tokens in that account entry.
- Separately remove ARCHER's authorization in TikTok's connected-app permissions. The current disconnect operation does not itself call TikTok's token-revocation endpoint.
- Cancel pending scheduled posts separately. Disconnecting is not a queue-cancellation or full-data-erasure operation.
- For complete local removal, the operator must also remove relevant cached analytics, posting history, queued items, imported or generated media and any retained copies or backups. App credentials are separate configuration and are not removed by disconnecting an account.
For access, correction, deletion or privacy questions, email inquire@archerperezz.net with the subject “ARCHER privacy request”. Do not send passwords or tokens. Requests are reviewed and handled manually after appropriate identity checks; there is no automatic deletion portal or guaranteed completion deadline stated here. Legal obligations or information outside the operator's control may limit removal.
Disconnecting or deleting local data does not remove posts already uploaded to TikTok. Manage those posts in TikTok; TikTok controls its own retention and deletion process.
08 / Public website and changes
The portfolio may load external fonts, scripts and social video players. Those providers receive the requests needed to serve their content. Its contact form prepares an email in the visitor's email application; it does not automatically submit the brief. This notice primarily describes the ARCHER desktop social integration, not a promise that third-party websites use no cookies.
This notice reflects the current personal-only implementation. Material changes to access, storage or audience will require an updated notice. The effective date above identifies this version.