1. Overview and developer
LocaleArc is a macOS application offered by Anatolia Apps. It helps a channel owner load YouTube video metadata, prepare localized titles and descriptions, review drafts, and publish only approved localizations.
LocaleArc has no developer-operated account system, analytics service, advertising SDK, or cloud backend. Anatolia Apps does not receive your Google credentials, YouTube API data, project files, or AI provider keys. Network requests go directly from the app on your Mac to the service you choose.
2. Google and YouTube data
LocaleArc uses the YouTube Data API v3 and requests this sensitive OAuth scope:
https://www.googleapis.com/auth/youtube.force-ssl
Google describes this scope broadly because it can permit an authorized client to see, edit, and permanently delete YouTube videos, ratings, comments, and captions. LocaleArc limits its actual use to the product functions described here:
- identify the YouTube channel connected by the user;
- read the channel’s uploads and video metadata, including video IDs, titles, descriptions, language information, thumbnails, publication dates, categories, and existing localizations;
- add, update, or remove localized video titles and descriptions only after a user starts the relevant publish or remove action.
LocaleArc does not upload or delete videos, post comments, change ratings, or change a video’s visibility. Google authentication occurs in the system authentication session; LocaleArc never sees your Google password.
LocaleArc’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Use of YouTube API Services is also subject to the YouTube API Services Terms of Service and YouTube API Services Developer Policies.
3. Information stored on your Mac
- OAuth credentials. Google access and refresh tokens are stored as generic-password items in macOS Keychain under the service
com.localizer.app.secrets. - YouTube workspace data. Imported metadata, channel identity, localization state, and translation drafts are stored in the app’s local project state.
- Activity history. A local operation log can contain operation results, error messages, and video titles. It does not intentionally contain OAuth tokens, AI API keys, or Google passwords.
- Recovery copies. LocaleArc keeps a local backup of project state to protect drafts from file corruption. The backup is covered by the same retention and deletion rules as the primary state.
- Preferences and purchases. App settings and trial state are stored locally. App Store purchases are processed by Apple; LocaleArc receives only StoreKit entitlement information, not payment-card details.
In sandboxed App Store builds, project state is inside the app container under Library/Application Support/YouTubeLocalizer/. Existing non-App-Store builds use ~/Library/Application Support/YouTubeLocalizer/. The legacy folder name is retained so updates do not hide existing drafts.
4. AI providers and other third parties
When you request a translation, LocaleArc sends the source title, source description, target languages, and any translation instructions directly from your Mac to the AI provider selected in Settings: Google Gemini, OpenRouter, or Ollama Cloud. Requests use the API key you provide for your own account. Anatolia Apps does not proxy or receive these requests.
Those providers process information under their own terms and privacy policies. Google and YouTube process OAuth and YouTube API requests under Google’s Privacy Policy. Apple processes App Store purchases and refunds under Apple’s policies.
LocaleArc does not sell Google user data, use it for advertising, transfer it to data brokers, or use it to build advertising profiles. It does not share Google user data with Anatolia Apps or unrelated third parties.
5. Retention, refresh, revocation, and deletion
A successful full channel refresh records a local refresh date. YouTube metadata and related drafts may remain available for up to 30 calendar days. On the next app launch, LocaleArc removes YouTube metadata, related drafts, channel identity, and related activity history that have not been fully refreshed within that period before using or displaying them.
Choosing Disconnect in LocaleArc asks Google to revoke the OAuth token and immediately removes the local OAuth credential, cached YouTube metadata, channel identity, unpublished drafts, related activity history, and recovery copies. App preferences and StoreKit purchase state remain. Content already published to YouTube is not deleted by clearing LocaleArc’s local data.
If Google’s revocation endpoint cannot be reached, LocaleArc still removes local credentials and YouTube data and warns you that Google access may remain active. You can revoke access from Google Account permissions. If access is revoked outside LocaleArc, the app detects an unusable token on the next refresh or API operation and removes the related local YouTube data.
6. Your choices
- Do not connect Google or configure an AI provider if you do not want LocaleArc to access those services.
- Use YouTube Settings → Disconnect to revoke access and delete locally stored YouTube data.
- Use Google Account permissions to review or revoke Google access independently.
- Delete LocaleArc and its application container or legacy Application Support folder to remove the remaining local project and preference data. Keychain Access can remove any remaining
com.localizer.app.secretsitems.
7. Security and children
LocaleArc uses HTTPS for service requests, PKCE with the OAuth authorization-code flow, a random state value for callback validation, macOS Keychain for credentials, and App Sandbox network-client access. No method of storage or transmission is completely risk-free.
LocaleArc is intended for YouTube channel owners and is not directed to children under 13. Anatolia Apps does not knowingly collect personal information from children through LocaleArc.
8. Policy changes
The current version is published on this page. Material changes will be identified by the “Last updated” date and, when appropriate, in app release notes before the changed handling takes effect.
9. Contact
Privacy questions and deletion support: anatolianapps@gmail.com