Privacy Policy
How we handle the information you put into Blink, who else touches it, how long we keep it, and what you can ask us to do with it.
Last updated 19 November 2026.
Who we are
Blink is operated by Theta Advisory Corp., a corporation registered in Alberta, Canada. For the purposes of Canadian privacy law (PIPEDA) and, where it applies, the GDPR, Theta Advisory Corp. is the organization accountable for the personal information described on this page.
Where the GDPR applies, we rely on our contract with you, our legitimate interest in running and securing Blink and this website, and your consent where we ask for it.
Blink was previously offered as PostLedger by DanTron Inc. Responsibility for the data described here rests with Theta Advisory Corp., and nothing about how that data is handled changed in the transfer.
What we collect
Information you give us
- Your name and email address, when you register.
- Your organization’s name and the entities you configure.
- Billing details, handled by Stripe. We never see or store your card number.
- What you type into the chat on this website: your messages, and the name, email address and phone number you choose to give so we can reply.
- How you found this website: once per visit, the address of the page you arrived on (including any campaign tags in it), the page that linked you here, and a random visitor ID kept in your browser so a return visit is counted as one visitor.
Information created by using Blink
- Schedule configurations and the journal entries calculated from them.
- Approval records: who submitted, who reviewed, what they decided, and when.
- Workbook cell values referenced by a journal entry, captured at the moment of submission so the entry can be audited later.
- Supporting documents you attach to a journal entry.
- An audit trail entry for every calculation, change, approval and posting.
Information from your accounting system
- An encrypted OAuth token for each connection you authorise. We never store your Xero or QuickBooks Online password.
- The reports, accounts, contacts and transactions you choose to pull, and the details needed to post the journals you approve.
Information from Google
When you use Blink with Google Sheets, Docs or Slides, Google sign-in provides your Google account identifier, name, email address and, where provided, Workspace domain. We use these to identify you and your firm and manage your access to Blink.
With your authorisation, Blink reads and updates the open spreadsheet, document or presentation to insert and refresh reports, reporting tags and tables. This includes file contents and the metadata needed to keep those features working. If you grant file access for sign-off or version history, Blink also accesses file and revision information and can export a copy to retain with your review evidence.
Google-derived information and exported copies sent to Blink are handled under this policy. We do not use Google permissions to access unrelated files for advertising, profiling or training machine learning models.
We share Google user data only with the sub-processors listed below, as needed to provide Blink, or where the law requires it.
Blink does not create or keep aggregated or anonymized datasets from Google user data. Any figures derived from your files exist only in your own Blink records and files, and are handled exactly like the information described above.
How we use it
Solely to provide the service: authenticating you, pulling and refreshing reports, updating the files you work in, running your schedules, routing approvals, posting journals to your accounting system on your instruction, and keeping the audit trail that makes those actions reviewable.
We do not sell your data, share it for advertising, or use it to train machine learning models. We do not use it to build a product for anyone other than you.
Blink’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Where it is stored
Blink's application database and document copies retained by Blink are hosted in Canada. Everything is encrypted in transit (TLS) and at rest, and sessions expire after 30 minutes of inactivity.
Access to your firm’s data is limited to your firm’s users, by role, and each firm’s records are kept separate from every other firm’s at the database level. Your Google access tokens stay with Google Apps Script: Blink’s servers never receive or store them.
Your original Google Sheets, Docs and Slides files remain in Google Workspace. Their storage location and retention are governed by your Google account or your organization’s Google Workspace agreement and settings.
Some information is necessarily processed outside Canada by the sub-processors and connected services listed below — billing by Stripe in the United States, sign-in by Microsoft Entra and Google globally, website chat by Blastily, and whatever your accounting system handles in its own regions. Information processed in another country may be subject to that country's laws, including lawful access by its authorities.
Who else processes it
We use a small number of sub-processors. Each one is bound by contract to use the data only to deliver its service to us.
| Sub-processor | Purpose | Where |
|---|---|---|
| Microsoft Azure | Application hosting, database, document storage | Canada |
| Stripe, Inc. | Subscription billing and payment processing | United States |
| Blastily LLC | The chat on this website (your messages and the contact details you give in it), and, if you agree, measuring how visitors find the site | Canada (Calgary). Its own providers store or process data in the United States and other countries; see Blastily’s privacy policy |
Services you connect
Blink also exchanges information with services you choose to connect. Their handling of it is governed by your own agreement with each provider.
| Service | Purpose | Where |
|---|---|---|
| Microsoft Entra ID | Single sign-on, where your organization uses it | Global |
| Google sign-in and the Google Workspace files you authorise Blink to use | Global; Workspace file locations follow your Google agreement and settings | |
| Xero · Intuit (QuickBooks Online) | The accounting system you connect, at your instruction | Per vendor |
We will update this list before adding a sub-processor that handles personal information.
How long we keep it
- Supporting documents attached to a journal entry are uploaded to your accounting system as part of posting, then deleted from our storage. They live with the entry in Xero or QuickBooks Online from that point on, so they are not covered by export from Blink or by the retention periods below.
- Audit trail entries are kept for the life of your account plus 90 days. They are append-only by design — that is what makes them useful as evidence.
- Everything else is kept while your account is open, then for 90 days after termination so you can retrieve it, after which it is permanently deleted.
You can revoke Blink’s Google access through your Google Account connections. Revoking access stops future authorised access; it does not itself delete your Blink account or copies already retained by Blink. Contact us using the privacy details below to request deletion. Deleting Blink data does not delete your original Google files.
Your rights
You can ask us to show you the personal information we hold about you, correct it, export it, or delete it. Write to privacy@theblinkapp.co and we will respond within 30 days.
Deletion has one limit worth stating plainly: we cannot remove entries from an audit trail your organization is relying on for its own compliance obligations without that organization’s instruction. If that affects your request, we will tell you which records are involved and why.
If you are unhappy with how we have handled a request, you can complain to the Office of the Privacy Commissioner of Canada.
Cookies and tracking
This website sets no cookies of its own and runs no advertising or tracking pixels. Fonts are served from this domain rather than a font network.
Visit measurement, only if you agree. On your first visit we ask whether we may
count your visit. If you click Accept, a small script from Blastily runs once per visit. It
sends Blastily the address of the page you arrived on (including any campaign tags), the page
that linked you here, and a random visitor ID. The ID is kept in your browser’s local
storage (as __blvid) so return visits are recognised; it is not linked to your
name or email unless you also use the chat.
If you click Reject, or your browser sends a Global Privacy Control signal, the script is
never loaded and no ID is stored. Your choice is kept in your browser’s local storage
(as blink_consent) for 12 months, then we ask again. You can change it at any
time with Cookie settings, at the foot of every
page. Changing to Reject removes the ID from your browser; visits already counted are not
deleted from Blastily’s records by that step, but you can ask us to delete them
(see your rights).
The other script from Blastily is the chat. It loads on every page. Once you start a conversation, it keeps a token in your browser’s local storage so the conversation survives a page change. It sends what you type in it, with the address of the page you sent it from, to Blastily so we can read and answer it. Apart from loading the script itself, nothing goes to Blastily until you send a message; once you have an open conversation, each page you visit checks it for replies. Blastily’s servers may also set a cookie that protects their service from bots.
The Blink application itself uses a session token to keep you signed in. That is functional, not analytical.
Changes to this policy
We will post any change on this page and update the date above. If a change materially affects how we handle your information, we will tell you by email at least 30 days before it takes effect.
Privacy questions
Questions about this policy, or a request about your own data.
