NAVIGATOR.

Privacy Policy

1. Operator

Lam Binh Nguyen
Einzelunternehmen
Gorkistr. 20
13507 Berlin
Deutschland

E-mail: info@hunterall.com. Use this address for privacy and deletion requests. VAT identification number (Umsatzsteuer-Identifikationsnummer) according to § 27a of the German Value Added Tax Act: DE326520426. Responsible for content: Lam Binh Nguyen, address as above.

2. What this notice covers

Hunter Navigator is a separate web service. Invited account holders can search and fetch public web pages, and can connect their own TikTok, Facebook Page, Instagram professional, Google Business Profile, YouTube and Pinterest accounts and their WordPress websites so Hunter Navigator can schedule and publish posts on those accounts and read analytics for them. This page describes that connected-account processing. Hosting, invite access, Google sign-in to Hunter Navigator itself, usage counters and the cloud browser are described in the German privacy notice. Hunter Navigator does not share accounts, data or runtime with other HUNTER-family products.

3. Connected accounts

You connect an account only by signing in at that platform and approving access. Hunter Navigator then stores the tokens the platform returns, the account name and the platform’s account id. A connected AI application that you authorize may schedule posts and read analytics. It does not receive platform tokens.

An account holder can also send a connect link to someone else (for example a client or a team member). The person who opens it connects their own accounts the same way, on each platform’s approval page, without a Hunter Navigator login. The link is stored only as a SHA-256 hash, expires after at most 30 days and a set number of uses, and can be revoked. Accounts connected through a link belong to the account holder who created the link.

TikTok

The TikTok connector requests these scopes: user.info.basic, user.info.profile, user.info.stats, video.publish, video.upload and video.list. TikTok returns an access token, a refresh token, an open id and an expiry. The user-info call asks for open id and display name. Statistics stored are follower count, following count, likes count and video count. A video-list call asks for id, view count, like count, comment count, share count and create time for up to 20 recent videos. Hunter Navigator stores the summed view, like, comment and share counts for that set. It does not store each video’s id or create time. Publishing asks TikTok to pull the media from Hunter Navigator’s short-lived address. If TikTok allows only a private draft for this app, the draft id is stored on the post result.

Meta (Facebook Pages and Instagram professional accounts)

The Meta connector requests these permissions: pages_show_list, pages_manage_posts, pages_read_engagement, read_insights, business_management, instagram_basic, instagram_content_publish and instagram_manage_insights. If a Facebook Login for Business configuration id is set on the server, the authorize request sends that configuration id instead of this permission list, and the permissions are then the ones on that configuration. The connector’s defined list is the eight permissions above.

From that access Hunter Navigator receives the Facebook user id, each granted Page’s id, name and Page access token, and the id and username of an Instagram professional account linked to the Page. Stored Page statistics, where the platform still returns them, are followers count, fan count, page impressions unique, page post engagements, page daily follows unique and page views total. Stored Instagram statistics are followers count, media count, reach, views, accounts engaged, total interactions, likes, comments, shares, and follows and unfollows. A metric Meta has retired is skipped.

Google Business Profile

The Google Business Profile connector requests this scope: https://www.googleapis.com/auth/business.manage. The request asks for offline access and a fresh consent, and it uses a one-time PKCE verifier. Hunter Navigator stores the access token, refresh token and expiry, the Google account resource name, and each location’s resource name and title. A local post sends the text you wrote, and, when you add them, one photo URL and a link.

The daily statistics sync reads the 14 days ending yesterday in one call. The metrics are desktop and mobile map impressions, desktop and mobile search impressions, call clicks, website clicks and direction requests. A number Google returns is stored for that day. Google omits the value when the count is zero, and the numbers often appear only after a delay, so a missing value is stored as zero once 5 days have passed, or 10 days for direction requests. Inside that delay a missing value is left unset, and a later sync can fill it in. Days already stored are updated. Days older than this 14-day window stay until the account is disconnected or a deletion request removes them.

Signing in to Hunter Navigator with Google is a different connection. It is described in the German privacy notice: Hunter Navigator receives a signed confirmation of the invited e-mail address and does not store that e-mail address or a Google token for the sign-in.

YouTube

The YouTube connector is a separate Google OAuth client from Google Business Profile. It requests these scopes together: https://www.googleapis.com/auth/youtube.readonly and https://www.googleapis.com/auth/youtube.upload. The request asks for offline access, a fresh consent, and a one-time PKCE verifier. Hunter Navigator stores the access token, refresh token and expiry, the channel id, and the channel title. At connect it also stores, inside the encrypted token, that channel’s subscriber count, view count and video count. The daily statistics sync stores those same three counts for the previous day.

A video is uploaded from the file on the server to YouTube, in chunks. The video’s privacy status is private unless the server is configured for public or unlisted. Any other configured value is treated as private. The title is the first line of the post text, up to 100 characters, and the description is the post text, up to 5000 characters.

By connecting YouTube you also agree to the YouTube Terms of Service. Google’s handling of the data is described in the Google Privacy Policy.

Pinterest

The Pinterest connector requests these scopes: boards:read, boards:write, pins:read, pins:write and user_accounts:read. Pinterest returns an access token, a refresh token and their expiry. Hunter Navigator reads the account username and the list of boards, and stores each board’s id and name as a separate connected account. A Pin sends one image from Hunter Navigator’s short-lived address, a title (the first line of the post text), the description (up to 800 characters) and, when you add one, a link. Stored board statistics are pin count, follower count and collaborator count.

Websites (WordPress)

A WordPress website is connected through WordPress’s own “Authorize Application” page: you approve the connection in your site’s admin area and WordPress sends an application password directly to Hunter Navigator’s server. Alternatively you can paste an application password you created. Hunter Navigator checks that the user may publish posts and upload media, then stores the site address, the WordPress username and the application password, encrypted like the platform tokens above. It never asks for your WordPress login password. A post uploads the images you added to your site’s media library and creates a post with the first line as title and the rest as text. The stored statistic is the number of published posts. Revoke access any time in WordPress under Users → Profile → Application Passwords.

4. Purpose

Connected-account data is used to schedule and publish posts you create for the accounts you connect, and to read and show analytics for those accounts. Post text, an optional link, the target accounts, the scheduled time, references to uploaded media, and the publish result (including the platform post id) are stored for that purpose. Images and videos you upload or import are stored so the platform can download them when the post is published.

5. Where it is stored, and how tokens are protected

Hunter Navigator runs on a server of Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, in a data centre in Falkenstein, Germany. Connected-account records, posts and statistics are in the service database on that server. Media files are in a media directory on that server. Hetzner processes this data for us (Art. 28 GDPR).

Platform access tokens and refresh tokens are encrypted at rest with AES-256-GCM. A separate key is derived for each connected account from a master key that remains on the server. The ciphertext is bound to that account and platform. Tokens are not shown in the product and are not returned to you or to a connected AI application. Account names, platform ids and post text are stored in the database without that token encryption. Media files are stored so the platform can fetch them from an unguessable address; that address is not listed in a directory.

6. How long it is kept

Uploaded and imported media can be fetched from the unguessable address for at most 7 days. After that the address stops working. The file and its database row are removed on the next purge. A purge runs when new media is created and once a day with the statistics sync, from 03:00 UTC. An unfinished upload older than one hour is removed in the same purge.

Daily statistics are not deleted by age. They are deleted immediately when you disconnect that account. Disconnecting an account also deletes its stored token. It does not delete post records, and it does not delete media that has not yet reached the 7-day purge. Cancelling a post that has not been published marks it cancelled and keeps the record. Post records stay until we delete them on a deletion request.

For each provider, Hunter Navigator stores the latest connect error, and a statistics error that is not an authentication failure, together with the time it was recorded. An authentication failure while reading statistics marks that account as needing a reconnect and does not write this error record. A successful connect clears the stored error. A successful Google Business statistics sync clears the Google Business error. Disconnecting an account does not delete this error record. It stays until a later success clears it, or until a deletion request.

The one-time value used during a connect expires after 15 minutes. For Google Business Profile, YouTube and TikTok that value also holds a one-time PKCE verifier. Usage counters for quotas, which do not contain post content, are covered by the German privacy notice and are deleted after 90 days.

7. How to disconnect

In Hunter Navigator, sign in, open Social, and choose Disconnect on the account. That deletes the stored token and that account’s statistics immediately.

Also remove Hunter Navigator in the platform’s own settings, so the platform stops accepting the token. TikTok: in the TikTok app, Settings and privacy → Security → Apps and services. Facebook and Instagram: Facebook Apps and websites. An Instagram professional account connected through Facebook is removed with that Facebook login. Instagram’s own settings may also list the app under Security → Apps and websites. Google Business Profile and YouTube are separate Google apps: remove each one under Google Account third-party access. Pinterest: in your Pinterest account settings, remove Hunter Navigator from the list of connected apps. WordPress: Users → Profile → Application Passwords, revoke “Navigator by Hunter”.

8. Deletion requests

E-mail info@hunterall.com to request deletion of the personal data Hunter Navigator holds about you. That request covers tokens, account records, statistics, post records and media that are still stored.

Meta can also call the data-deletion callback at /v1/social/meta/data-deletion. A valid signed request deletes the Facebook Page and Instagram professional account records for that Facebook user id, including their tokens and statistics. The callback does not delete post records, media files, or the provider error record. The confirmation address returned to Meta is the German privacy notice. There is no data-deletion callback for TikTok, YouTube or Google Business Profile; use the e-mail above, and disconnect the account in Hunter Navigator and in the platform’s settings.

9. No sale and no advertising use

Hunter Navigator does not sell connected-account data and does not share it with advertisers, advertising networks or data brokers. Data is sent to the platform that issued the account (Meta Platforms Ireland Ltd., Google Ireland Ltd., TikTok Technology Ltd. or Pinterest Europe Ltd.), or to your own WordPress website, when a post you scheduled is published, when a YouTube video is uploaded, and when statistics are read. The hosting provider processes the stored data as described above.

Google user data. Hunter Navigator’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features you see in Hunter Navigator (publishing your posts and videos and showing your statistics). It is not used for advertising, not sold, not used to train generalized AI or machine-learning models, and not read by humans except with your consent, for security, to comply with law, or in aggregated, anonymized form for internal operations.

10. Your rights, and the German notice

You have the rights of access, rectification, erasure, restriction, portability and objection under the GDPR, and the right to complain to a supervisory authority. Contact info@hunterall.com. The German privacy notice states the same rights and names the Berlin supervisory authority. It is the notice for the rest of the service.