Privacy Policy
Effective 21 November 2026 · 日本語版
This policy explains what Tokyo Brief Signals collects about you, why, who handles it, and the choices you have.
Signals is run by Dial-up Ventures Inc., a company incorporated in Ontario, Canada. We follow Canada's federal privacy law (PIPEDA) and, for people in Japan, Japan's Act on the Protection of Personal Information (APPI).
In short: your topics and matches are never public and are not shown to other customers. We do not sell personal information. Analytics and advertising tags run on our public pages, not on your account pages. No email address, hashed or not, goes from Signals to an advertising platform. The only advertising platform we use is Meta.
1. Who we are and what this policy covers
Tokyo Brief Signals ("Signals") is operated by Dial-up Ventures Inc.. Registered address: 106 Dovercourt Rd, Toronto, Ontario M6J 0G4, Canada. "Tokyo Brief" and "Tokyo Brief Signals" are brands of that company. In this policy, "we" means Dial-up Ventures Inc..
Our Privacy Officer is accountable for this policy and for how we handle personal information. Write to the Privacy Officer, Dial-up Ventures Inc., at [email protected] or at the address above.
This policy covers signals.tokyobrief.com: the public pages, the waitlist, your account and dashboard, the API, MCP and webhooks, and the emails Signals sends. The Tokyo Brief newsletter and tokyobrief.com have their own privacy policy.
If you use Signals as a member of someone else's account, such as your employer's, the owners of that account can see your email address, your name if you gave one, your role, and what you set up in the account.
2. What we collect
We collect what you give us, what Signals produces for your account, and a small amount of technical data.
| What | Details | Where it comes from |
|---|---|---|
| Waitlist | Your email address, the language of the page you joined from, and the time you joined. | You |
| Sign-in | Your email address, your sign-in credentials such as one-time codes, sign-in sessions, and your name if you add one. Our sign-in provider holds these. Our own database stores an identifier for you, not your email address. | You, through our sign-in provider |
| Account and team | Account name, members and their roles. For each invitation: the invited person's email address, the role offered, who sent it and when it expires. | You and your account's owners |
| Settings | Interface language, alert language, time zone, email schedules and unsubscribe choices. | You |
| Topics | Topic titles, statements, exclusions, the companies, places and agencies you watch, drafts, previews, reports, and whether you marked a preview result relevant or not. | You |
| Matches and delivery | Which documents matched your topics, when you last viewed your matches, and records of the emails and webhook deliveries we sent (time, language, status, the email provider's message id). | Produced by Signals |
| Billing | Your plan, billing periods, and identifiers for your customer record, subscription and invoices at our payment processor, including whether a payment was refunded or disputed. Card details go to the payment processor. We never see or store them. | You at checkout; our payment processor |
| API keys and webhooks | For each API key: a short prefix, a one-way hash of the key, its label and when it was last used. We do not store the key itself. For each webhook: the URL you gave us and a delivery log. | You |
| Messages | What you write when you email us. | You |
| Technical data | IP address, browser type, the pages requested and the time, in server and security logs. Error and performance reports with personal details removed. | Your browser |
| Analytics and advertising data | Described in sections 8 and 9. | Your browser |
| Audit records | A record of each change our staff make to an account. | Produced by Signals |
Please do not put passwords, payment details, health information or other sensitive personal information into a topic.
3. How we use it
We use personal information to:
- run your account and sign you in;
- find the official documents that match your topics, write summaries, and deliver them to your dashboard, by email, and through the API, MCP and webhooks;
- charge for your plan, handle refunds and prevent payment fraud;
- send service email: match emails and digests, reports you ask for, and notices about your account, plan or topics;
- send news about Signals to people who joined the waitlist or created an account (section 10);
- answer your questions and requests;
- keep Signals secure, find and fix faults, and prevent abuse;
- understand how our pages are used and whether our advertising works (sections 8 and 9);
- improve matching, using your relevance feedback and usage figures that do not identify you;
- meet our legal, tax and accounting duties.
We do not sell personal information. We do not use your topics to advertise to you. Your topics and matches are never published and are not shown to other customers.
By using Signals you agree to the collection, use and disclosure described in this policy. You can withdraw that agreement at any time by closing your account, unsubscribing, or writing to us, subject to legal and contractual limits. We may then be unable to provide all or part of the service.
We will ask for your consent before using personal information for a new purpose that this policy does not describe, unless the law allows or requires the use.
4. How AI models are used
Signals uses AI models from outside providers to read official documents, decide whether a document matches a topic, and write summaries and translations.
| Task | What the provider receives |
|---|---|
| Summaries and translations | The text of the official document. |
| Matching a document to topics | The text of the official document, and the statement and exclusions of each topic being checked, with an internal reference number for each topic. Topics from several accounts can be checked in one request. |
| Topic suggestions | The text you type when you ask Signals to suggest or refine a topic or a list of companies. |
We do not send your name, your email address or your account identifier to a model provider. Before text is sent, our software removes passwords, keys and similar credentials it finds in it.
Topic text is sent only to a provider and model that we have reviewed and approved for customer text, with a record of how long that provider keeps the data. A provider handles what it receives under its own terms.
Whatever you write in a topic is sent as written. If you name a person in a topic, that name reaches the provider.
5. Who handles information for us
These companies process information on our behalf so that we can run Signals. We remain responsible for it.
| Provider | What it does for us | Information | Based in |
|---|---|---|---|
| Clerk | Sign-in, sessions, invitation emails | Email address, name if given, sign-in and device data | United States |
| Stripe | Checkout, subscriptions, invoices, billing page | Name, email address, payment method, billing details | United States |
| DigitalOcean | Hosting, databases, file storage | Everything Signals stores | United States |
| Cloudflare | Network security in front of the site; the bot check on the waitlist form | IP address, request and browser details | United States |
| Resend | Sends match emails, digests, reports and notices | Email address, the content of the email | United States |
| MailerLite | Holds the waitlist and product-news list and sends that email | Email address, language, time of joining | European Union and United States |
| Sentry | Error monitoring | Error and performance reports with personal details removed | United States |
| AI model providers: OpenRouter (which passes requests to Anthropic and Google models) and OpenAI | Reading documents, matching them to topics, summaries, translations and topic suggestions | As set out in section 4 | United States |
| Google (Google Analytics) | Measures use of our pages | As set out in sections 8 and 9 | United States |
We may replace a provider with another that does the same job. We will update this list when we do.
6. When we disclose information to others
Apart from the providers in section 5, we disclose personal information only:
- to the other members of your account, who can see the account's topics, matches and member list;
- to Meta, the advertising platform we use, as described in section 8;
- when the law requires it, or to protect our rights, our customers or the service;
- to a buyer or successor if our business or part of it is sold or reorganised, under terms that keep this policy's protections;
- with your consent.
What we send to Meta never includes your email address, your name or your account identifier. Meta may connect what it does receive (your IP address, browser details and its own identifiers) with information it already holds about you. We say this on the waitlist and sign-up forms, and by completing them you agree to it.
7. Where information is handled
We are a Canadian company. Our hosting and most of our providers are in the United States, and some providers also process information in other countries. Your information is therefore handled outside Canada and, if you live elsewhere, outside your country.
Information held in another country is subject to that country's laws. Courts, law enforcement and national security authorities there may be able to obtain it.
By using Signals you agree to your personal information being provided to the providers in section 5 in these countries. You can ask our Privacy Officer about our practices for providers outside Canada.
8. Analytics and advertising measurement
We measure two things: how our pages are used, and whether our advertising brings people to Signals. We use the results to improve our pages and to decide where to advertise. This section says who receives what. Section 9 begins with how to opt out.
Public pages. On pages anyone can open (the home page, the developer documentation and pages like this one, in English and Japanese) we load Google Analytics. For visitors who are not signed in to Signals, we also load an advertising measurement tag from Meta. The Google and Meta tags run in your browser and send the company that provides them the address of the page, the page you came from, your IP address, details of your browser and device, and the identifiers in that company's cookies. If you have a Meta or Google account, that company may connect the visit to you.
Sign-in, sign-up and account pages. No analytics or advertising tag runs on the sign-in page, the sign-up page or anywhere in your dashboard. If you are signed in to Signals, the Meta tag does not load on any Signals page. Our own server still counts views of these pages, as described next.
Page views on sign-in, sign-up and account pages. So that we can count visits, each of these pages tells our own server that it was opened, and our server passes one line to Google Analytics. Google receives one of a fixed list of page types (for example /dashboard/topics/:id or /sign-up/:step), a fixed page title, a visitor number and a visit number. A page that is not on the list is not reported at all, and nothing typed into the address can be sent. Google does not receive the full address, the real title, your topics, your email address or your account. The visitor number is the one in Google Analytics' own cookie if your browser has it from our public pages, and otherwise a random number we set (the sg_cid cookie). The visit number is kept in our sg_sid cookie. It starts from Google's own visit number if your browser has a Google Analytics visit still under way, and otherwise from a new number. Where Google's own numbers are used, Google can connect these page views with your visits to our public pages.
Joining and signing up. When you join the waitlist or create an account, our server reports that this happened. Google Analytics receives a waitlist join under the same visitor and visit numbers as your page views. It receives a new account under a new random number, because that report reaches our server from our sign-in provider without your cookies. Meta receives the event with a random event number, your IP address, your browser's user agent and, for a waitlist join, Meta's own browser identifiers if your browser holds them. We do not send your email address in any form, and we do not send your account identifier. If you have opted out of advertising measurement, or your browser sends the Global Privacy Control signal, when you join the waitlist or create an account, we tell Meta nothing.
How to opt out is set out at the start of section 9.
9. Cookies and what your browser sends
How to opt out of advertising measurement. You can stop Meta's advertising tag, and our own reports to Meta, in either of two ways:
- Use "Opt out of advertising measurement" on this page. It sets the sg_noads cookie in your browser for one year. From then on the Meta tag does not load on Signals pages in that browser, and a waitlist join or new account from that browser is not reported to Meta. You can turn measurement back on from the same control. Clearing your cookies also removes the choice.
- Turn on Global Privacy Control in your browser. A browser that sends this signal is opted out in the same way, without a cookie.
Other choices:
- Google Analytics on public pages. Install Google's opt-out add-on. The add-on does not affect the page counts our own server sends for sign-in, sign-up and account pages. If you block cookies, each of those page views is counted under a new random number and cannot be linked to another. If you delete them, later views start again under a new number.
- Meta's settings. Meta lets you limit how it uses data about you, in its own ad settings.
- Your browser. You can block or delete cookies in your browser settings. If you block our sign-in cookies you cannot sign in.
Signals sets these cookies itself:
| Cookie | Purpose | Lasts |
|---|---|---|
| __session, __client_uat and related sign-in cookies | Keep you signed in. Set through our sign-in provider, Clerk. | Up to one year |
| signals_ui_locale | Remembers your interface language. | One year |
| signals_active_account | Remembers which account you are viewing. | Until you close the browser |
| signals_waiting_topic | Returns you to a draft topic after checkout. | 24 hours |
| sg_cid | A random visitor number, used to count visits to sign-in, sign-up and account pages in Google Analytics. Set only when your browser has no Google Analytics visitor cookie. | Two years |
| sg_sid | A visit number for the same purpose. Set on every view of a sign-in, sign-up or account page and renewed each time. It starts from Google's own visit number if a Google Analytics visit is under way, otherwise from a new number. | 30 minutes after your last page |
| sg_noads | Remembers that you opted out of advertising measurement. | One year |
Other companies' code on our pages sets cookies or receives information from your browser:
| Company | Where | What is sent | Why | More information |
|---|---|---|---|---|
| Google (Google Analytics) | Public pages | Page address, referring page, IP address, browser and device details, the _ga and _ga_<id> cookies (up to two years) | We measure use of our pages. Google provides the measurement. | Google's policy · opt-out add-on |
| Meta | Public pages, when you are not signed in to Signals | Page address, referring page, IP address, browser and device details, the _fbp and _fbc cookies (about 90 days) | We measure our advertising. Meta uses the data under its own policy. | Meta's policy |
| Clerk | Sign-in, sign-up and account pages | Sign-in details, session cookies, IP address, browser and device details | To sign you in and keep your session secure. | Clerk's policy |
| Cloudflare | All pages; the bot check on the waitlist form | IP address, request and browser details; Cloudflare may set its own security cookies | To protect the site and block automated sign-ups. | Cloudflare's policy |
| Sentry | All pages | Error and performance reports with personal details removed | To find and fix faults. | Sentry's policy |
Checkout and the billing page are on Stripe's own site, which sets its own cookies under Stripe's policy.
10. Email from us
- Service email. An email for each match or digests on a schedule, as you choose; reports you ask for; and notices about your account, plan or topics. Every match email and every digest has links to stop that kind of email or all Signals email. You can also change this under Delivery in your dashboard.
- Product news. When you join the waitlist or create an account, we add your email address to our Signals news list and may send you news about Signals. If you joined the waitlist, we send it because you asked us to. If you hold an account, we send it as part of our relationship with you as a customer, as section 4 of our Terms of Service sets out. Every message has an unsubscribe link, and unsubscribing does not affect your account or your service email. After an account ends we stop sending product news within the period the law allows, and in any case no later than two years afterwards.
- Invitations. When a member of an account invites you, our sign-in provider sends you the invitation at that member's request.
Match emails, digests, reports, notices and product news show our company name, a mailing address and how to contact us.
11. How long we keep it
- We keep account, team, topic, match and delivery information while your account exists.
- When you ask us to delete your information and we have confirmed who you are, we delete it or make it anonymous within 30 days, except what the law requires us to keep.
- We may delete the information of an account once 90 days have passed since its plan ended or the account was closed.
- We keep billing and tax records for as long as tax and accounting law requires.
- We keep your address on the waitlist and news list until you unsubscribe or ask us to remove it, and for an account holder no longer than two years after the account ends. We keep a record that you unsubscribed, so that we do not email you again.
- So that the same person is not counted twice, we keep a one-way code derived from the email address of each waitlist join, and the sign-in identifier of each new account, in our own database. They are not sent to anyone.
- Server and security logs are kept by our hosting and network providers for the periods those providers set.
Removing someone from an account, or deleting a sign-in, ends their access and revokes their API keys and webhooks at once. It does not by itself delete the account's topics and matches, which belong to the account.
12. Security
We protect personal information with measures that fit its sensitivity:
- customer data is held in a database separate from the one behind the Tokyo Brief news site;
- connections to Signals are encrypted in transit;
- sign-in is handled by a specialist sign-in provider, and our own database holds no sign-in credentials;
- API keys are stored only as a one-way hash, and card details never reach our systems;
- access inside an account is limited by role, and each change our staff make to an account is recorded;
- credentials found in text are removed before that text is sent to a model provider.
No system is perfectly secure. If a breach of our safeguards creates a real risk of significant harm to you, we will tell you and the regulators the law requires us to tell.
13. Your rights
You can ask us to tell you what personal information we hold about you and how it has been used and disclosed, to give you a copy, to correct it, to delete it, or to stop using it. Write to [email protected]. We will confirm who you are, then answer within 30 days. We do not charge for this.
If your information is held in an account owned by someone else, such as your employer, we may ask that account's owner to help with your request.
If you are unhappy with how we handled your information or your request, tell our Privacy Officer first. You also have the right to complain to a regulator:
- Canada: the Office of the Privacy Commissioner of Canada.
- Japan: the Personal Information Protection Commission. Under the APPI you may ask us to tell you the purpose of use, to disclose, correct, add to or delete the personal data we hold about you, to stop using it or stop providing it to third parties, and to disclose our records of providing it to third parties.
- European Economic Area and United Kingdom: Signals is not directed at these regions. If their data protection law applies to you, we rely on our contract with you, our legitimate interests in running and improving Signals, your consent where we ask for it, and our legal duties. You have the rights of access, correction, deletion, restriction, objection and portability, and you may complain to your local data protection authority.
14. People named in official documents
Signals reads documents that public bodies publish. Some of them name people: officials, licence holders, business owners, or people subject to an official decision. A summary or quoted passage may repeat such a name.
We use this information only to tell customers about the documents that match their topics. We do not build profiles of individuals, and our terms forbid customers from using Signals to monitor private individuals.
If you are named in a document that Signals shows and you believe our summary is wrong, or that we should stop showing it, write to [email protected]. We will review it and can correct or remove our summary or stop showing the document. We cannot change the publisher's original.
15. Children
Signals is for people aged 18 or over. We do not knowingly collect personal information from anyone under 18. If you believe a child has given us information, write to us and we will delete it.
16. Changes to this policy
We may change this policy as Signals changes. The current version is always on this page with the date it took effect. If a change materially affects how we use your personal information, we will tell account holders by email or in the product before it takes effect.
17. Contact
Privacy Officer, Dial-up Ventures Inc., 106 Dovercourt Rd, Toronto, Ontario M6J 0G4, Canada. Email: [email protected].
Questions, requests for access or correction, complaints and removal requests all go to that address.