Privacy policy
Last updated: 19 November 2026
Who we are
TaskHistory (“we”) is made by Vladyslav Vasylovych Krot (ФОП Крот Владислав Васильович), a sole proprietor (FOP) registered in Chernihiv, Ukraine. We are the controller of the personal data described below. Contact: [email protected].
TaskHistory is a Google Sheets™ add-on that copies tasks from Asana into a spreadsheet you choose and keeps their history. It is not affiliated with Asana, Inc. or Google LLC.
The short version
- Your task data never reaches our servers. Tasks, names, notes, custom fields and everything else from Asana go straight from Asana’s API to Google Apps Script, which runs the add-on inside your Google account, and from there into your spreadsheet.
- Our backend (on Cloudflare) relays the Asana sign-in without storing tokens, and stores your plan status under a random ID. It holds no email address for add-on users.
- Payments are handled by Paddle, our merchant of record. We never see your card details.
- We use no advertising, no analytics trackers and no cookies.
Google user data: what the add-on accesses and why
The add-on asks Google for these permissions and uses them only for the features below.
| Permission | What we do with it |
|---|---|
See, edit, create and delete only the spreadsheet the add-on runs in
(spreadsheets.currentonly)
|
Writes the synced tasks, the History, Changes and Report tabs and two hidden helper tabs, and reads them back to update rows. It cannot open your other files. |
Connect to an external service (script.external_request) |
Calls Asana’s API (read-only) and our backend (sign-in relay and plan check). |
Allow the add-on to run when you are not present (script.scriptapp) |
Creates one hourly time-driven trigger per spreadsheet for scheduled syncs, and a one-time state token for the Asana sign-in callback. |
Display and run third-party web content in prompts and sidebars (script.container.ui)
|
Shows the menu and sidebar. |
Send email as you (script.send_mail) |
Sends you an email when a scheduled sync fails twice in a row (at most once a day per sync) or when Asana needs reconnecting. |
See your primary Google Account email address (userinfo.email) |
Finds the address for those emails. We do not store it or send it to our servers. |
Data these permissions reach stays in your Google account: in the spreadsheet, in the add-on’s Apps Script storage (below), and in the emails sent to you. We do not copy it to our servers, sell it, use it for advertising, or use it to train AI or machine-learning models.
Limited Use. TaskHistory’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of information received from Google Workspace APIs will also adhere to the Google Workspace API User Data and Developer Policy.
Asana data: what the add-on reads
When you connect Asana, the add-on asks only for these read-only permissions. It never creates, changes or deletes anything in Asana. What it reads stays in your Google account (the spreadsheet, the add-on’s storage and the emails described below) and never reaches our servers.
| Permission | Used for |
|---|---|
workspaces:read |
Listing your workspaces to pick one |
projects:read |
Listing projects, a team’s projects and each project’s custom fields |
portfolios:read |
Portfolios you own and their projects, as sync sources |
teams:read |
Your teams, as sync sources |
tasks:read |
The tasks and subtasks of the projects you chose, and which changed since the last sync |
custom_fields:read |
Custom-field names, types and values for their columns |
users:read |
The assignee’s name and email for the Assignee columns |
Where the add-on keeps data inside your Google account
| Place | What | Who can see it |
|---|---|---|
Your spreadsheet: the sync’s data tab and <sync> History,
<sync> Changes, <sync> Report
|
The tasks and fields you chose, daily snapshots, logged changes and report formulas | Everyone you share the spreadsheet with |
Hidden tabs _taskhistory_keys_<id> and _taskhistory_state_<id>
|
Task IDs seen in the current pass; per task the last known values of the fields you track and a hash, used to detect changes | Same as the spreadsheet (hidden, not protected) |
| Document properties (stored with the spreadsheet) | Each sync’s settings (name, workspace and selected project/portfolio/team IDs and names, columns, schedule, history options, a random owner ID), sync progress (page positions, last run time), and status (last success, row count, duration, last error and hint, skipped sources), the column catalog (field names and types) | Editors of the spreadsheet, through the add-on |
| Your user properties (only your Google account) | Your Asana access token, refresh token and expiry; a temporary sign-in verifier (deleted after connecting); a random owner ID; a random account key; your cached plan status; a short note when a Sync now was refused | Only you, through the add-on |
| Your user cache (only your Google account) | Workspace, project, portfolio, team and custom-field names while you edit a sync | Only you; deleted after at most 10 minutes or when read |
| Emails to you | Sync name, spreadsheet name and link, error message and fix hint | You |
Error reports. When the add-on hits an unexpected error, Google Apps Script records the error message and technical details in our Google Cloud project’s logs (Cloud Logging). These messages can contain names of projects or fields, but never your tokens. We read them only to fix problems. They are deleted after Google’s default log retention (<30 days — confirm in the Cloud console>).
What our backend stores (Cloudflare Workers and D1)
| Data | Purpose | Retention |
|---|---|---|
| Licence: random account key (not your email), plan, status, trial end, current period end, past-due date, Paddle customer ID and Paddle subscription ID, time of the last billing event, created/updated times | Know which plan applies to your add-on | While you use TaskHistory; <DECIDE, e.g. deleted 24 months after the trial or the last subscription ended>, or on request |
| Billing event IDs: Paddle event ID, event type, time received | Process each Paddle notification only once | 30 days (deleted automatically every day) |
| Abuse protection: a salted one-way hash of your network address (IPv6: its /64 prefix), a counter and a time window | Rate-limit public endpoints | About 1 day (deleted automatically every day). We never store your IP address itself. |
| Waitlist (website only): email, answers (Asana plan, number of projects, current tool, would-pay), consent, sign-up and update times | Tell you about the launch; plan the product from totals | Until the launch email, at most 12 months after sign-up |
| Service logs (Workers Logs): event names, status codes, error types | Run and debug the service. Logs are filtered: no emails, tokens, request bodies or account keys | 3 days (Cloudflare Workers Free) |
Asana sign-in relay. Asana requires an app secret to issue tokens, so the add-on sends the one-time sign-in code, the verifier and later the refresh token through our backend, which adds the secret and forwards them to Asana. The backend keeps nothing of this, neither in its database nor in its logs. Tokens are stored only in your Google user properties.
Plan check. At most every 12 hours, and when you click “refresh plan”, the add-on sends your random account key to our backend and gets back your plan. No other data is sent. The first check starts your 7-day trial.
Cloudflare, Inc. hosts the backend and the website as our processor. It may process IP addresses in its own operational logs. See https://www.cloudflare.com/privacypolicy/.
Payments (Paddle)
Paddle.com Market Limited is the merchant of record for TaskHistory Pro. Paddle sells the subscription to you, runs the checkout, collects your payment details, email, country and tax information, issues receipts and handles VAT/sales tax and refunds. Paddle processes that data as an independent controller under its own privacy policy: https://www.paddle.com/legal/privacy. The checkout page loads Paddle.js from Paddle’s servers and passes Paddle only your random account key, so Paddle can tell us which add-on account paid. From Paddle we receive and keep only the items in the licence row above.
Website
The website sets no cookies and uses no analytics or tracking scripts. Only the checkout page loads a third-party script (Paddle.js). <If Cloudflare Web Analytics, which is cookieless, is switched on later, say so here.>
Waitlist
If you joined the waitlist on our homepage:
- What we store: your email address; your answers (Asana plan, number of projects, what you use today, whether you would pay); that you gave consent, and when you signed up or last updated your answers. Signing up again with the same email updates your answers instead of adding a second entry.
- Why: to email you once when TaskHistory launches, and to decide whether and how to build it, using totals only (for example, how many people use Asana Starter). The legal basis is your consent. We never sell or share the list.
- Where: in our database on Cloudflare (Workers and D1), which processes it on our behalf. Spam protection uses the salted network-address hash described above, which holds no email or answers.
- How long: until we send the launch email or stop the waitlist, and at most 12 months after you sign up.
- Deleting it: email [email protected] from the address you signed up with and ask us to delete your waitlist entry. We delete it within 30 days and confirm by email. You can also ask what we hold about you or correct it the same way.
Legal bases (EU/UK GDPR and similar laws)
- Contract: running the add-on and your subscription (licence row, sign-in relay, plan check, failure emails).
- Legitimate interests: security and abuse prevention (rate-limit hashes, logs) and fixing errors (error reports).
- Consent: the waitlist. You can withdraw it at any time.
- Legal obligation: records Paddle keeps for tax purposes (Paddle is responsible for them).
Sharing
We do not sell or rent personal data and do not share it for advertising. Recipients: Cloudflare (hosting, as a processor), Paddle (payments, as an independent controller), Google and Asana (they run the services the add-on connects, under your own agreements with them), and authorities when the law requires it.
International transfers
Cloudflare and Paddle may process data outside your country, including in the United States and the United Kingdom, under their own safeguards (for example, standard contractual clauses). <Legal review: confirm the transfer basis.>
Your choices and rights
- Disconnect Asana: sidebar → Disconnect Asana. The add-on asks Asana to revoke the connection and deletes your Asana tokens from your Google account. You can also remove the app in Asana’s settings.
- Delete a sync: sidebar → Edit → Delete. Its settings, status and hidden helper tabs are deleted. The visible tabs stay in your spreadsheet until you delete them.
- Remove Google access: Google Account → Security → Third-party apps with account access → TaskHistory → Remove access. Uninstalling the add-on does not delete data inside your spreadsheet, and Google may keep the add-on’s user properties until access is removed. Disconnect Asana first.
- Subscription: cancel or update payment details in Paddle’s customer portal (link in your receipt).
- Your rights: depending on where you live, you can ask for access, correction, deletion, restriction or portability of your data, object to processing, and complain to a data-protection authority. Email [email protected]. To find your licence row, include your Paddle receipt or the account key shown in the checkout link. We answer within 30 days.
Children
TaskHistory is a business tool and is not directed at children under 16.
Changes
We will post changes on this page and update the date at the top. If a change affects how we use Google user data, we will ask for your consent where required.
Contact
Vladyslav Vasylovych Krot (FOP), Chernihiv, Ukraine · [email protected]
Google Sheets™ is a trademark of Google LLC. Asana is a trademark of Asana, Inc.