Privacy policy
CalGantt runs in your own Google account. We have no server and we never receive your calendar, your tasks or your spreadsheet.
In short
- CalGantt runs in Google Apps Script, with your Google account. Your data goes directly between Google Sheets, Google Calendar and Google Tasks.
- The CalGantt web app (app.calgantt.com) works without Google Sheets: your browser talks directly to Google Calendar and Google Tasks, and the app keeps its working copy in your browser (see section 12).
- In Google Calendar, CalGantt only shows a card in the side panel, with buttons that open CalGantt in a new tab: it reads no calendar data there (see section 2).
- We have no server and no database. We cannot see your events, your tasks or your spreadsheets. Only technical error reports reach us, without the content of your calendars or tasks.
- CalGantt keeps in your spreadsheet a hidden copy of what it shows. This copy is not private: anyone who can open the spreadsheet can read it (see Shared spreadsheets).
- We do not sell, rent or share data, we show no ads, and we never use your data to train AI models.
- CalGantt never sends emails to the guests of your events.
- How your data is protected (least privilege, no transfer outside Google, encryption in transit and at rest, access control, incident notification): see section 11.
1. Who we are
CalGantt (the Google Sheets add-on, its card in Google Calendar, the web app app.calgantt.com and the website calgantt.com) is published by a private individual based in France (see the legal notice). In this policy, “we” means the publisher of CalGantt.
Contact for any privacy question: [email protected].
2. Google data CalGantt uses, and why
When you install CalGantt, Google asks you to allow these permissions (in Google’s own words below). CalGantt uses each one only for the purpose described, and only while you use it.
| Permission | What CalGantt does with it |
|---|---|
View and manage spreadsheets that this application has been installed inspreadsheets.currentonly | Keeps CalGantt’s working tabs in the open spreadsheet (see section 3) and creates an export or templates tab when you ask. When you import a table from a tab, it reads that tab. It reads the list of people who can open the spreadsheet only to count them and warn you; it keeps nothing of it. It cannot open any other file in your Google Drive. |
Display and run third-party web content in prompts and sidebars inside Google applicationsscript.container.ui | Shows the CalGantt menu and window inside Google Sheets. |
See the list of Google calendars you’re subscribed tocalendar.calendarlist.readonly | Lists your calendars (name, color, time zone, whether you can edit them) so you can choose which ones to show. |
View and edit events on all your calendarscalendar.events | Reads the events of the calendars you chose, to draw them. Creates, moves, changes, marks as done or deletes an event only when you do it in CalGantt. When you create a deadline, it adds a pop-up reminder; all-day tasks are marked “free” so they do not block your schedule. |
Create, edit, organize, and delete all your taskstasks | Reads the names of your task lists and the tasks of the lists you chose. Creates, changes, moves or deletes a task only when you do it in CalGantt. |
See your primary Google Account email addressuserinfo.email | Checks that a license key belongs to your account (or to your company domain), and gives your tabs and settings a short code derived from your address, so that each person’s data stays apart in a shared spreadsheet. Apart from error reports (section 4), CalGantt does not send your address anywhere. Once online payment opens, it will be passed to the payment page only if you choose to buy (section 5). |
CalGantt has no permission to connect to outside services: it cannot send your calendar or your tasks to an outside server. Only technical error reports reach us (section 4). It cannot read your email, your contacts or your other files.
In Google Calendar. CalGantt also shows a card in the side panel of Google Calendar. For this card, Google asks for two more permissions: “Run as a Calendar add-on” (calendar.addons.execute), to show the card in Google Calendar, and “View your country, language, and timezone” (script.locale), to show it in your language. The card reads no event, no calendar and no account data, and saves nothing. Its buttons only open pages in a new tab: the web app (section 12), a new Google Sheets file, or this website.
3. What CalGantt saves, and where
CalGantt saves data only in Google (in your Google account and in the spreadsheet you open it in) and in your browser. If someone else owns that spreadsheet, the hidden tabs are in their file.
- In your Google Calendar events: the category at the start of the title, between brackets, and private event fields (Google “extended properties”, not shown in Google Calendar) with the planning details: status, type, whether it is a task, priority, estimate, people, blocked state, dependencies, parent task and baseline dates. If you turn on “Write the state in Google Calendar titles” in Calendars and settings, the status, type, priority, estimate, people and blocked state are written in the title instead. CalGantt only uses its own private fields: it ignores the “shared” fields that the organizer of an invitation can set.
- In Google Tasks: Google Tasks has no private fields, so the category and state are written in the task title (for example “[Design] Mock-ups !! @Ana”), and for a task that lasts several days, its start date is written in the notes (“Start: yyyy-mm-dd”).
- In the spreadsheet, in hidden tabs (one set per person, named
GanttData_…andGanttHabits_…): a copy of the events and tasks shown (calendar and event IDs, calendar name and color, title, dates, category, status, priority, estimate, people, dependencies, and the description shortened to 400 characters), and your habit check-ins. For meetings with guests, the description is not copied (unless you mark the meeting as a task) and only the number of guests is kept, never their addresses. The copy also includes the calendars that other people share with you. Note that the ID of your main calendar is your email address. Each row of the copy is signed with a key that only you have: CalGantt ignores a row that someone else added or changed, and reads it again from Google, so another editor cannot make CalGantt change an event of their choice. Someone who can edit the spreadsheet can still delete rows or put back older ones; this only changes what you see until the next full read from Google (at least once a day). The signature protects the copy against changes, but it does not hide it (see “Shared spreadsheets” below). - In your private Google cache for CalGantt (the Apps Script cache, private to your Google account): the history of your recent changes, so that you can undo them with ↶ (within a size limit: the oldest are dropped first). For each item you change or delete, it keeps its state before the change (for example the title, dates and description; never the notes of meetings with guests). It is deleted automatically at the latest 6 hours after your last change (Google may empty this cache earlier). Earlier versions of CalGantt kept this history in a hidden tab (
GanttLog_…): this tab is now removed automatically. - In the spreadsheet settings (document properties): your choices (calendars to show, options, category colors) and technical sync data, saved under your code.
- Tabs you create on purpose: “Gantt export” (a visible copy of your plan) and “Gantt templates”, only when you use these features. The “Gantt export” tab can be seen by everyone who can open the spreadsheet and replaces the previous export, so CalGantt asks you before exporting. Text that Sheets would read as a formula is written there as plain text.
- In your Google account’s storage for CalGantt (user properties): your language, the start date of your trial, your license key, the 2 calendars or task lists registered for the free plan, and a random key used to sign your copy.
- In your browser (local storage): display preferences, such as open panels, zoom, collapsed groups and hidden or reordered calendars (these keep calendar IDs, category and people names, and task IDs), and which messages you have closed or already seen once (saved without your email address).
- Rating message (in your browser’s local storage too): CalGantt may invite you once to rate it on Google Workspace Marketplace. So that this message appears on one day only, after a few days of use, it keeps for each account the number of days you used CalGantt (up to 5), the last of them and the day the message was shown, under a code computed from the account, not your email address. Once you answer or that day has passed, only “done” is kept. This is never sent to us.
4. What we receive
We receive no data from your use of the add-on. There are only three exceptions:
- Error reports. When the add-on hits an error, Google Apps Script records in our Google Cloud project the error message, the place in the code and the time. These reports contain no content of your calendars or tasks. Rarely, a technical identifier can appear in them, such as a calendar ID (note that the ID of a main calendar is an email address). We read them only to fix bugs, and they are deleted automatically after 30 days.
- Install statistics. Google shows us the total number of installs. It does not tell us who you are.
- What you send us yourself: your emails to support and, once online payment is open, the purchase details if you buy a plan (section 5).
Nothing else reaches us: CalGantt has no permission to connect to outside services.
5. Purchases
Online payment is not open yet: no plan can be bought for now. When it opens, payments will be handled by our payment provider, which will receive your name, email address and card details under its own privacy policy. We will never see your card number. We will receive your name, email address, country, the plan, the amount and limited card details (card type, last 4 digits), to create your license key and send it to you by email. We will keep this license record while the license is valid and up to 3 years after it ends. Invoices and accounting records are kept for 10 years, as French law requires.
6. Emails to support
Messages sent to [email protected] are forwarded by Cloudflare Email Routing to a mailbox hosted by Google. We keep them as long as needed to answer you, and at most 3 years after our last exchange.
7. The website calgantt.com
The website is hosted by Cloudflare Pages. It sets no cookies, shows no ads and has no tracking. We use Cloudflare Web Analytics, which counts visits without cookies and without identifying you (not in the web app, see section 12). The home page and the guide page can show a video hosted on YouTube: it is loaded from youtube-nocookie.com only when you click play, and YouTube’s privacy policy then applies. Cloudflare processes technical data such as your IP address to deliver and protect the website.
8. Google API Services User Data Policy
CalGantt’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.
In particular: we do not transfer Google user data to third parties, except, once online payment is open, your email address to the payment page when you choose to buy; we do not use it for advertising; no person reads it; error reports, which contain no calendar or task content, are read only to fix bugs; and we do not use it to develop, improve or train generalized artificial intelligence or machine learning models.
9. Legal bases
Under the GDPR, we rely on: the contract, to provide the add-on you installed or the web app you use and any plan you buy; our legitimate interest, for error reports, security and visit counts; and our legal obligations, for invoices.
10. Your choices and your rights
- Remove CalGantt’s data from a spreadsheet: in CalGantt, open “Calendars and settings” and click “Remove my data from this spreadsheet” (you need edit access to the spreadsheet). Your hidden tabs, your history of changes and your settings in this spreadsheet are deleted. Not deleted: the “Gantt export” and “Gantt templates” tabs (delete them like any other tab), and older versions of the spreadsheet in File › Version history, which its editors can see. To remove those, make a copy of the spreadsheet (a copy has no version history) and delete the original, or ask its owner. Your language, trial date, license key, the 2 calendars or task lists registered for the free plan and your signing key stay with your Google account, so that the trial and the free plan are not restarted.
- Events and tasks: they stay in Google Calendar and Google Tasks. The private planning fields are not shown in Google Calendar and are deleted with the event; the category and state written in titles can be edited like any text.
- Uninstall: in Google Sheets, Extensions → Add-ons → Manage add-ons → CalGantt → Uninstall. Uninstalling deletes nothing: first use “Remove my data from this spreadsheet” in each spreadsheet where you used CalGantt.
- Web app: “Remove my data from this browser” and “Sign out”, see section 12.
- Remove access: at myaccount.google.com/permissions, choose CalGantt and remove its access (this removes it for the add-on, its card in Google Calendar and the web app at once).
- Your rights: you can ask to access, correct or delete the data we hold about you (support emails and purchases), to limit its use, to object to it or to get a copy. Write to [email protected]; we answer within one month. You can also complain to the French data protection authority, the CNIL (www.cnil.fr).
11. How we protect your data, and how long it is kept
Your calendar events and tasks can be sensitive (they may reveal your schedule, your work or your projects). CalGantt protects them with these measures:
- Least privilege. CalGantt asks only for the permissions listed in section 2.
spreadsheets.currentonlylimits it to the spreadsheet you open it in: it cannot open your other files, your Google Drive, your email or your contacts. It reads only the calendars and task lists you choose, and changes an event or a task only when you do it yourself in CalGantt. - No transfer outside Google. CalGantt has no server, no database and no permission to connect to outside services. Your events and tasks go only between Google Calendar, Google Tasks, your spreadsheet and your private Google cache for CalGantt, inside Google’s Apps Script environment. They are processed in memory while a request runs, and we never receive or keep a copy. In the web app, they go directly between your browser and Google (section 12).
- Encryption. All exchanges between your browser, Google Sheets, Apps Script, Google Calendar and Google Tasks are encrypted in transit (HTTPS/TLS). What CalGantt saves (in your events and tasks, in the hidden working tabs and in the settings) and the error reports are stored by Google and encrypted at rest by Google’s infrastructure. The website calgantt.com and the web app app.calgantt.com are served only over HTTPS.
- Access control. Only the developer can access CalGantt’s code, its Google Cloud project and its error reports, through a single Google account protected by 2-step verification. No one at CalGantt can open, read or export your calendars, your tasks or your spreadsheets.
- Separation between people. In a shared spreadsheet, each person’s copy of their planning and their settings are kept apart, under a code derived from their own account, and “Remove my data from this spreadsheet” deletes them. Each row of the copy is signed with a key that only its owner has: a row added or changed by someone else is ignored and read again from Google. This keeps each person’s data apart and protects it against changes; it does not hide it (see “Shared spreadsheets”, section 3). The history of changes is not kept in the spreadsheet. The email addresses of your events’ guests are never stored, and the description of a meeting is not copied (unless you mark it as a task).
- Minimal technical data. Error reports keep only the error message, the place in the code and the time, contain no calendar or task content, are visible only to the developer and are deleted automatically after 30 days. License keys are checked inside the add-on with a cryptographic signature; the signing secret is kept in the project’s protected settings, never in the code.
- Security incidents. If a security incident affecting personal data ever occurred, we would notify the CNIL within 72 hours where required, and inform the people concerned without undue delay when the risk is high.
How long data is kept. Apart from the history of changes, which is deleted automatically at the latest 6 hours after your last change, what CalGantt saves in Google stays there until it is removed as described in section 10. Uninstalling CalGantt or removing its access stops it from reading or writing anything, but deletes nothing. Error reports are deleted after 30 days and emails to support at the latest 3 years after our last exchange. Once online payment is open, license records will be kept up to 3 years after the license ends, and invoices 10 years. What the web app keeps in your browser stays there until you remove it, except the history of changes and the sign-in key, which are deleted automatically (section 12). Your data is also protected by the security of your Google account: we recommend 2-step verification. As we keep no copy of your planning, there is no database of ours that could leak.
12. The CalGantt web app (app.calgantt.com)
The web app shows the same Gantt chart in a web page, without Google Sheets. It is a test version. Its demo works without an account and without signing in (the page still loads Google’s sign-in script).
- Permissions. When you sign in with Google, the web app asks for
calendar.calendarlist.readonly,calendar.events,tasksanduserinfo.email. It uses them as described in section 2: to list your calendars, to read the calendars and task lists you choose and change their events and tasks only when you do it, and to know which Google account is signed in, so that each account’s data stays apart in your browser. If you do not allow Google Tasks, the web app works without it. It asks for no access to Google Sheets or Google Drive. - No server. The page runs in your browser and connects directly to Google’s servers (Google Calendar, Google Tasks and Google sign-in). Apart from loading its own files from app.calgantt.com, its security policy allows no connection outside Google. We have no server and no database: we never receive your events, your tasks or your email address, and the web app sends us no error reports.
- Sign-in. Google gives the page an access key that is valid for about one hour. So that reloading the page or opening it in a new tab does not ask you to sign in again, the page keeps this key in your browser’s local storage, with the email address and the permissions it was given for, until it expires. Closing the page or the browser does not delete it. After one hour at most the key no longer works: the page deletes it a few minutes before that if it is open, otherwise the next time it opens. The key is sent only to Google. “Sign out” (More menu) deletes it at once and forgets the remembered account, but deletes nothing else stored in this browser and does not sign you out of Google. To withdraw CalGantt’s access completely, use your Google account (section 10).
- What it keeps, and where. In your browser (IndexedDB), for each Google account used, stored under its email address: a copy of what it shows (the same information as the hidden tabs of section 3, with the description shortened to 400 characters), your settings, your language, your time zone and technical sync data, the start date of your trial, the calendars or task lists registered for the free plan, a key that signs the copy, and the history of your recent changes for ↶ (for each item changed or deleted, its state before the change, including its full description, except for meetings with guests). The history expires 6 hours after your last change and is deleted the next time you open the web app with that account. Your browser also keeps, in local storage, the access key of the last sign-in (see “Sign-in”), the email address of the last account used and the display preferences of section 3, which are shared by all accounts used in this browser (except the closed messages and the rating message, kept for each account). In Google Calendar and Google Tasks, the web app writes exactly what the add-on writes (section 3). It writes nothing in Google Sheets or Google Drive.
- Remove it. In the web app, open “Calendars and settings” and click “Remove my data from this browser” (this link is not on the first welcome screen). For the Google account that is signed in, it deletes from this browser the copy, the history, the settings, the trial date, the free-plan choices, the signing key, the display preferences (with the closed messages and the rating message of every account used in this browser), the remembered account and the kept sign-in; the page then restarts signed out. Apart from that, what other Google accounts left in this browser stays. Clearing the site data of app.calgantt.com in your browser deletes everything. On a shared computer, also sign out of your Google account in that browser.
- Protection. The web app has its own address, separate from the website. Apart from its own code and Google’s sign-in script, no script runs on it: no analytics, no ads, no video. A strict security policy blocks any other script, and any connection other than to Google and to the app’s own address (which only serves its files). What it keeps in your browser is protected by your device and your browser profile, not by us: anyone who uses the same browser profile could read it. On a shared computer, click “Sign out” when you finish: until it expires, the kept sign-in lets anyone who uses the same browser profile open CalGantt with your account.
- Hosting. The files of the web app are served by Cloudflare Pages, which processes technical data such as your IP address to deliver them. Your calendars and tasks never go through Cloudflare.
13. Transfers outside the EU
Google and Cloudflare may process data in the United States. They rely on the EU-U.S. Data Privacy Framework and on the European Commission’s standard contractual clauses.
14. Children
CalGantt is not intended for children under 15.
15. Changes
If this policy changes, we update the date at the top of this page. Important changes are also announced on this website.