Privacy Policy

Последње ажурирање: 20. 10. 2026.

Овај документ је доступан на енглеском језику. Преводи служе само ради лакшег разумевања; меродаван је енглески текст.

This policy explains what SeekInflu collects, why, who it is shared with, how long it is kept, and what it deliberately does not collect. SeekInflu is an independent service and is not operated by, endorsed by, or affiliated with YouTube or Google.

Contact for privacy questions and complaints

Operator: 比嘉 正茂 (sole proprietor).

Postal address: 〒150-0043 東京都渋谷区道玄坂1丁目10番8号 渋谷道玄坂東急ビル2F-C.

For questions or complaints about privacy, or to request access, correction, deletion or account closure, contact the operator by phone or post using the details here. We respond within 7 calendar days.

Phone: 050-6865-9267

Who is responsible for your data

The operator of SeekInflu is the data controller for the personal data described here. Our legal name, address and contact details are published on the Operator Information page, which also serves as our disclosure under the Japanese Act on Specified Commercial Transactions.

For any privacy question, correction, deletion or complaint, contact the operator by phone at 050-6865-9267 or at the postal address published at https://seekinflu.com/operator. We answer privacy requests within 7 calendar days.

What we collect about you

We collect only what the service needs in order to work, to bill you correctly, and to keep the service secure.

  • Account: your name, email address, a hashed password, and — if you sign in with Google — your Google account email, name and profile picture. We never receive your Google password.
  • Usage: the search sentences you type, the filters you choose, your saved channel ids, your own notes, your search history, and monthly counters for searches and CSV exports.
  • Billing: a payment-provider customer and subscription identifier, your plan, billing period and subscription status. Card numbers are entered on the payment provider’s own hosted page. We never see, receive or store them.
  • Operational logs: request metadata such as IP address, timestamp, user agent and the route called, used to detect abuse, enforce rate limits and diagnose faults.
  • Support correspondence: what you write to us and our replies.

Why we use it, and on what legal basis

Under the Japanese Act on the Protection of Personal Information, these are our purposes of use. Where the GDPR or UK GDPR applies, the legal basis is given in brackets.

  • To provide the service you asked for: running searches, saving channels, exporting CSV files, keeping you signed in [performance of a contract].
  • To meter and enforce plan allowances, and to bill you [performance of a contract].
  • To keep the service secure and available: rate limiting, abuse detection, fault diagnosis [legitimate interests].
  • To send transactional email: email verification, password resets, billing notices, and replies to your enquiries [performance of a contract].
  • To meet tax, accounting and other legal obligations [legal obligation].

What we never collect

These are product decisions, not just policy statements — the code contains no path that would produce this data, and automated tests fail the build if one is introduced.

  • Email addresses or phone numbers of YouTube creators. We do not extract them from channel descriptions even when they appear there, and we ignore mailto: links. There is no email column in the CSV export.
  • Scraped content. We do not fetch YouTube channel pages, About tabs, watch pages, videos, audio or captions. Every result comes from the official YouTube Data API v3.
  • Inferred personal attributes. We do not estimate, store or display anyone’s age, gender, race, ethnicity, religion, political affiliation, health or sexual orientation, and we refuse searches that ask us to.
  • Proprietary scores. We do not compute a "suitability", "influence" or "PR fit" rating for any person.
  • Advertising or cross-site tracking identifiers. We run no advertising network and no third-party analytics that profile you across sites.

YouTube API Services

SeekInflu is an API Client of YouTube API Services. It uses them to search for videos and to read publicly available channel and video metadata. By using SeekInflu you are also agreeing to be bound by the YouTube Terms of Service.

Google’s Privacy Policy explains how Google handles personal data provided in connection with YouTube API Services. You can review, and at any time revoke, SeekInflu’s access to data in your Google account through the Google security settings page.

Google sign-in is used only for your basic identity (openid, email and profile). SeekInflu does not request YouTube authorization scopes, access private YouTube account data, or upload, like, comment or subscribe on your behalf. Public YouTube searches use our server-side API key independently of Google sign-in.

YouTube thumbnails and channel images are served to your browser by Google. Loading them sends technical information such as your IP address and browser request to Google. The official attribution artwork is hosted by SeekInflu. Following a YouTube link opens YouTube, where Google may collect data and use cookies under its own Privacy Policy. SeekInflu does not embed a video player or automatically start playback.

YouTube-derived data — video titles and ids, thumbnails, publish dates, channel titles, subscriber and video counts, channel descriptions and latest-upload timestamps — is held only in a short-lived cache and is then refreshed from the API or discarded. Our cache expires within 24 hours, well inside the 30 calendar days that the YouTube API Services Developer Policies allow, and we make reasonable efforts to keep what we show consistent with what the API currently returns.

Our own database never stores YouTube content. A saved channel is stored as its YouTube channel id plus the note you wrote; the channel’s title, subscriber count and other details are fetched again when you look at it.

Who we share it with

We do not sell personal data, and we do not share it for anyone else’s marketing. We use the following processors, each only for the purpose stated. Because they operate outside Japan, using SeekInflu involves a transfer of personal data to the countries named.

  • Google LLC (United States) — YouTube API Services. Your search terms are sent to the API as a query. Your account details are not.
  • Cloudflare, Inc. (United States, processing in any region where Cloudflare operates) — hosting, database, cache and bot protection.
  • Stripe, Inc. and its group companies (United States, Ireland, Japan) — payment processing and subscription management.
  • Sendinblue SAS, trading as Brevo (France, European Union) — transactional email delivery.
  • A third-party language-model provider, only when query expansion is enabled. It receives the sentence you typed and nothing else — never YouTube data, never your account details. This feature can be disabled, in which case a rule-based planner is used and no data leaves our infrastructure for this purpose.

International transfers

Where personal data is transferred out of the European Economic Area or the United Kingdom, the transfer relies on the European Commission’s Standard Contractual Clauses or an adequacy decision, as applicable to the processor concerned. Japan holds an adequacy decision from the European Commission.

Where the Japanese Act on the Protection of Personal Information applies, the processors above are named so that you know which countries your data may reach before you provide it. On request we will tell you what protective measures the processor concerned has in place.

How long we keep it

  • Account records: while your account is open; deletion requests are handled as soon as possible and within 7 calendar days, except records we must retain by law.
  • Saved channels, notes and search history: while your account is open. Search history is also capped by your plan, and older entries are deleted automatically as new ones arrive.
  • Billing records: seven years after the transaction, because Japanese tax and accounting law requires it. This is the one category we cannot delete on request.
  • Operational logs: up to 30 days.
  • Cached YouTube data: at most 24 hours.
  • Support correspondence: up to two years.

Your rights

You may ask us to give you a copy of your personal data, correct it, delete it, export it in a machine-readable form, restrict or object to a particular use, or withdraw consent where we relied on it. Exercising these rights is free and will not lead to worse treatment.

Deleting your account removes your saved channels, notes, search history and usage counters. Billing records are retained for the period stated above because the law requires it.

You can delete saved channels, private notes and search history yourself at https://seekinflu.com/account using “Delete saved data”. These records and their cached search snapshots are removed when that request succeeds. This leaves your account, subscription and monthly allowance in place. Other temporary public API caches and replay records expire within 24 hours; a deleted search cannot be reopened through a replay record.

Deleting data in SeekInflu does not delete or change data held by YouTube or Google. To manage or delete data there, use the controls in your YouTube or Google account. Revoking Google sign-in access is separate from deleting saved SeekInflu data; you can request account closure using the contact details above.

We act on a deletion request as soon as possible and in any case within 7 calendar days, which is also what the YouTube API Services Developer Policies require of us.

If you are in the European Economic Area or the United Kingdom you may also complain to your local supervisory authority. If you are in Japan you may contact the Personal Information Protection Commission. We would rather you came to us first so we can put it right.

How we protect it

We maintain administrative, technical and physical controls appropriate to the risk, and review them as the service changes.

  • All traffic is served over HTTPS with HSTS. Session cookies are HttpOnly, Secure and SameSite=Lax, and state-changing requests from another origin are rejected.
  • Passwords must be at least 10 characters and are stored only as hashes. Sign-in attempts are rate limited.
  • API keys, signing secrets and database credentials are stored as encrypted environment secrets and are never sent to the browser.
  • Database access is exclusively through bound parameters. Access to production systems is limited to the operator.
  • Payment card data never touches our systems; it is handled on the payment provider’s own PCI-DSS compliant pages.

Cookies

We use essential cookies for sign-in, session verification and secure authentication flows. Session cookies are HttpOnly, Secure and SameSite=Lax. We do not set advertising cookies or use third-party analytics that track you across other sites. Google content and links are described in the YouTube API Services section above.

Children

SeekInflu is a business tool and is not directed at children. We do not knowingly create accounts for anyone under 18. If you believe a child has registered, contact us and we will delete the account.

Changes and contact

We will update this page when the service changes and revise the date above. If a change materially reduces your rights, we will tell you in the product or by email before it takes effect.

For any privacy question or request, contact us at the address published on the Operator Information page.