Privacy policy

Effective October 21, 2026. Applies to the Gantt Maker editor, MCP and plugin.

Controller and contact

Gantt Maker is published by Tomas Perrando (DataTomi). For questions about your data, email ganttmaker.support@gmail.com or visit Support.

Data and purposes

Projects include the project, group, task and person names you enter, dates, progress, dependencies and planning preferences. They are saved in your browser's storage to display and edit the board. Exported JSON copies remain wherever you choose to save them.

When you connect with OpenAI, Sites authenticates your account and provides the service with a verified user identifier. The service uses it to associate agent requests with your browser session. This connection allows reading and editing all projects in that browser while the original tab remains open and connected.

If you contact support, we receive your email address, message contents and any files you choose to attach in order to handle your request.

Basic traffic measurement

Page-visit measurement uses a random browser-local identifier, stored on the server as a hash together with the UTC day, public page and referring hostname. It also records a random visit ID per load or resumption after 30 minutes without signals, start and last-signal times, approximate active time, interaction, manual editing and observed exit signals. It does not record project contents or IDs, edited values, keys, pointer positions, IP addresses, full user-agent strings, referring URLs or query strings. No country is collected. The embedded chat preview does not send these visit signals.

Visit signals require JavaScript and browser storage. They are omitted when Do Not Track or Global Privacy Control is enabled, or storage is unavailable. Different devices or cleared storage can count again. Visible time stops accumulating after 60 seconds without interaction. A browser signal does not prove a human visitor, and exit signals can be lost.

From October 27, 2026, every HTTP request reaching the application is also counted in anonymous aggregates by UTC day, site hostname, normalized route, resource category, method, response status and declared browser/bot/automation category. These counts include API calls, assets, embedded chat requests, errors, redirects and requests without JavaScript, including DNT/GPC requests. They do not use visitor identifiers. Unknown routes are grouped without storing their path contents or queries. Full user-agent strings are classified in memory and are not stored. The application cannot observe traffic handled or blocked by the hosting platform before it reaches the Worker.

Records are stored in Sites D1 and reports are owner-only. Reports cover the last 30 days. Older rows are removed when traffic arrives, so deletion can be delayed without new requests. The random browser identifier remains until site storage is cleared. HTTP counts and JavaScript visit signals have different scopes and are not added together.

Transmission and providers

With AI connected, requests, changes and necessary data pass through the Gantt Maker remote service and your AI provider. The interactive chat component receives the data needed to display and edit the project. Projects are not automatically synced between devices.

OpenAI hosts the site through ChatGPT Sites. The service uses R2 storage provided by Sites for session records and operation messages. The platform processes HTTP requests and technical connection data. Gantt Maker code logs the path and status of failed requests without including project contents or credentials in those messages.

Support email is managed through Google's Gmail. These providers' processing depends on their terms and the configuration of the services used: OpenAI privacy policy and Google privacy policy.

Retention

• Projects and copies: remain in your browser and exported files until you delete them. The remote service does not keep a recoverable master copy of your projects.
• Session records and support email: are retained until manually deleted, with no automatic deletion period configured. Closing a tab does not delete these records.
• Operation messages: the service attempts to delete them when each operation ends, during expired-message cleanup or on disconnection. If execution is interrupted, stored objects may remain until a later cleanup or manual deletion; there is no guaranteed maximum period for physical deletion.
• Access expiry: session authorization expires after 60 seconds without renewal. Requests expire after 20 seconds and responses after 30 seconds. These periods limit their use but do not mean all stored data is deleted.

Records and copies retained by OpenAI, your AI provider and Google are also governed by their own policies. Disconnecting Gantt Maker does not delete conversations or data already shared with those services.

Your controls

You can disconnect AI from Gantt Maker, delete projects and clear site storage in your browser. Before clearing local data, save a copy if you want to keep your plan.

To access, correct or request deletion of session or support data managed by Gantt Maker, write to the contact above. For data stored by your AI provider, also use that service's controls.

Only share information you are authorized to use. Gantt Maker does not encrypt JSON copies. Do not send passwords, tokens or confidential information to support.