தனியுரிமைக் கொள்கை

Introduction

LoopGantt (“we,” “our,” or “us”) is a product of Loopends Studios. This Privacy Policy explains how we collect, use, store, and protect your information when you use LoopGantt at loopgantt.com.

We believe in transparency. This policy describes every category of data we handle and every third-party service involved, so you can make informed decisions about using our product.

What Data We Collect

Account Information

When you create an account, we collect your email address and an authentication credential managed by our identity provider. We do not store passwords directly—authentication is handled by Supabase Auth, an open-source service we run on our own server. If you sign in with Google, we receive your email address and basic profile from Google.

Project Data

All project data you create in LoopGantt—tasks, dependencies, durations, milestones, calendars, and baselines—is stored in our database. This data belongs to you and is necessary to provide the service.

Usage Analytics

We collect anonymized usage data through Google Analytics and Umami to understand how people use LoopGantt. This includes page views, feature usage patterns, device type, browser type, and general geographic region. We do not collect personally identifiable information through analytics.

AI Generation Data

When you use the AI project generation feature, the project description you provide is sent to our AI provider (Groq or Anthropic, see Third-Party Services) to generate a task structure. We do not retain these descriptions after generation is complete.

Anonymized Deletion Records

When you delete your account, we retain a single anonymized snapshot containing only aggregated, non-identifying information: your tier (free or pro), bucketed account age, bucketed engagement counts (projects, tasks, comments), bucketed AI usage, country code (if available), and your stated reason for leaving. This snapshot contains no email, no name, no user ID, no IP address, and no personal content; raw counts are replaced with ranges (e.g., “2–5 projects”) so individual users cannot be re-identified. We use this data exclusively to understand churn patterns and improve the product. This retention is permitted under GDPR Recital 26 (anonymized data falls outside the regulation’s scope) and complements the proof-of-deletion record kept under Article 17(3)(e).

How We Use Your Data

• Provide the service: Store and display your projects, calculate schedules, manage your account, and process AI generation requests.
• Improve the product: Analyze aggregated, anonymized usage patterns to identify bugs, improve performance, and prioritize new features.
• Communicate with you: Send account-related emails such as password resets or critical service notifications. We do not send marketing emails unless you explicitly opt in.
• Enforce our terms: Monitor for abuse, rate-limit AI generation requests, and maintain service integrity.

Third-Party Services

LoopGantt relies on the following third-party services to operate. Each service has access only to the data necessary for its function:

• Hostinger (hosting) — LoopGantt, its PostgreSQL database and its authentication service run on a virtual private server we rent from Hostinger, located in the United States. Your project data and account information are stored on that server. The database and authentication software is the open-source Supabase stack, operated by us; Supabase the company does not receive your data.
• Cloudflare (network and security) — All traffic to loopgantt.com passes through Cloudflare, which protects the site from attacks and speeds up delivery. Cloudflare processes request data such as IP address, browser user agent and the pages requested, in order to route and secure that traffic.
• Groq AI (AI project generation) — When you use AI-powered project generation, the project description you enter is sent to Groq’s API to generate a task structure using a large language model. Only the description text is transmitted—no account information or other project data is shared. Groq processes the request and returns the result; we do not have a data retention agreement with Groq beyond request processing.
• Anthropic (AI project generation) — AI project generation may also run on Anthropic’s Claude models. In that case the project description you enter (and, when you refine a plan, the plan being refined) is sent to Anthropic’s API to generate the task structure. No account information is shared. Anthropic processes the request under its commercial API terms and returns the result.
• Google Analytics (usage analytics) — We use Google Analytics (measurement ID: G-6YB8CF12LK) to collect anonymized usage data. Google Analytics uses cookies to track page views and user interactions. IP addresses are anonymized. You can opt out of Google Analytics by using a browser extension or disabling cookies.
• Umami (usage analytics) — A privacy-focused analytics tool we run ourselves at stats.loopends.com. It does not use cookies and records only anonymous, aggregated events (such as which plan or export format was used); no names, email addresses or project content.
• Resend (email delivery) — Sends LoopGantt’s notification emails you have enabled, project invitations and meeting invitations. Resend receives the recipient’s email address and the content of each email.
• Google (sign-in, calendar sync and Drive file picker) — Only if you choose to. When you sign in with Google, Google confirms your identity to us. When you connect Google Calendar, the projects you pick get their own calendars in your Google account. When you add a file from Google Drive to a task, Google’s file picker runs in your browser and LoopGantt keeps only the link and name of the files you pick. See “Google User Data” below for exactly what is sent and kept. You can disconnect at any time.
• Microsoft (Outlook calendar sync) — Only if you choose to. When you connect Outlook or Microsoft 365, the projects you pick get their own calendars in your Microsoft account; see “Microsoft (Outlook) User Data” below for exactly what is sent and kept. You can disconnect at any time.
• Zoom (meeting links) — Only if you choose to. When you connect Zoom and pick Zoom as a meeting’s video call, LoopGantt creates a Zoom meeting in your Zoom account for each meeting you organize and adds its join link to the meeting; see “Zoom User Data” below for exactly what is sent and kept. You can disconnect at any time.
• External calendar feeds — If you add a calendar feed link (for example from Outlook or Apple Calendar), LoopGantt fetches that feed from its provider to show your events. The link is stored encrypted and is only used to read the feed.
• Lemon Squeezy (payment processing) — If you subscribe to LoopGantt Pro, payment is processed by Lemon Squeezy (a Stripe-owned company). We do not store your credit card information. Lemon Squeezy handles all payment data in compliance with PCI DSS standards.

Google User Data

Connecting Google Calendar is optional. A connection works in one of two ways, depending on the permission it was made with.

• Project calendars (permission to create its own calendars and manage their events): LoopGantt creates one calendar per project you pick (its name, description, colour and your time zone) and, if you turn it on, a “LoopGantt · Meetings” calendar. It cannot see, change or delete your other calendars or their events.
• Primary calendar (permission to view and edit events on all your calendars; older connections): LoopGantt adds your tasks to your main Google calendar as all-day events. It reads that calendar only to find and remove the events it added itself, and never changes your own events.

• What we send to Google: an event for each dated task (its name, dates or times, and a link back to LoopGantt) and, with project calendars, for each meeting (its title, notes, time, repeat rule, place and join link). We add no guests, so Google sends no invitations on our behalf. With project calendars, a meeting you organise gets a Google Meet link unless you choose a different video option in Settings.
• What we read from Google: only the calendars and events LoopGantt created, to keep them in step with your projects, and the Google Meet link Google creates for a meeting.
• What we keep: the Google account’s email address and account ID, the access tokens (stored encrypted), the IDs of the calendars and events we created, and a meeting’s Google Meet link. The Meet link is saved as the meeting’s place when that is empty, so it appears in LoopGantt and in its meeting invitations. We keep nothing else from your Google account.
• Disconnecting:you can disconnect at any time in Settings → Integrations; with project calendars you can remove the LoopGantt calendars from Google at the same time. LoopGantt stops using the connection at once. To withdraw the permission at Google too, remove LoopGantt in your Google Account’s security settings (Third-party apps & services).

Google Drive files on tasks (permission to see only the files you pick with LoopGantt): adding files from Google Drive to a task is optional and separate from the calendar connection. Google’s file picker opens in your browser and shows your Drive; LoopGantt does not see your Drive, only the files you pick. For each picked file LoopGantt keeps its link and name, as a link on the task that people on the project can open (Google still decides who may open the file itself). The short-lived permission Google gives your browser for this is never sent to or stored on our server, and we do not read, copy or change the contents of your files. Removing the link from the task deletes what we kept; to withdraw the permission at Google, remove LoopGantt in your Google Account’s security settings.

LoopGantt’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. We do not use Google user data for advertising, do not sell it, do not use it to train AI models, and do not let people read it unless you ask us to for support, it is needed for security or to comply with the law.

Microsoft (Outlook) User Data

Connecting Outlook Calendar is optional. LoopGantt asks Microsoft for permission to read and write your calendars (Calendars.ReadWrite), to stay connected (offline access) and to know which account you connected (your name, email address and account ID). It uses that permission only to create one calendar per project you pick and, if you turn it on, a “LoopGantt · Meetings” calendar, and to keep the events in those calendars up to date. It does not read, change or delete your other calendars or their events.

• What we send to Microsoft: an event for each dated task (its name, dates or times, and a link back to LoopGantt) and for each meeting (its title, notes, time, repeat rule and place), plus each project calendar’s name and colour. We add no attendees, so Outlook sends no invitations on our behalf. A Microsoft Teams meeting is created only for a meeting you organize whose video call you set to Microsoft Teams (available with a work or school Microsoft 365 account); its join link is added to that meeting.
• What we read from Microsoft: only the calendars and events LoopGantt created, to keep them in step with your projects.
• What we keep: the Microsoft account’s email address and account ID, the access tokens (stored encrypted), and the IDs of the calendars and events we created. We keep nothing else from your Microsoft account.
• Disconnecting: you can disconnect at any time in Settings → Integrations, and remove the LoopGantt calendars from Outlook at the same time. LoopGantt stops using the connection at once. To withdraw the permission at Microsoft too, remove LoopGantt from the apps with access to your Microsoft account (for a work or school account, your organization’s administrator can also remove it).

We do not use data received from Microsoft for advertising, do not sell it, do not use it to train AI models, and do not let people read it unless you ask us to for support, it is needed for security or to comply with the law.

Zoom User Data

Connecting Zoom is optional. LoopGantt asks Zoom for permission to create, update, read and delete Zoom meetings in your Zoom account, and to know which Zoom account you connected (its user ID and email address). It uses that permission only for the meetings you organize in LoopGantt whose video call you set to Zoom. It does not read, change or delete any other Zoom meeting, recording or chat.

• What we send to Zoom: for each such meeting, its title and, for a one-time meeting, its start time, length and time zone. A repeating meeting gets one Zoom meeting without a fixed time, used for every occurrence. We send no notes and no attendees, so Zoom sends no invitations on our behalf.
• What we keep: the Zoom account’s user ID and email address, the access tokens (stored encrypted), and for each meeting the Zoom meeting ID and its join link (which is added to the meeting, so its invitees can join). We do not keep the host start link or anything else from your Zoom account.
• Changes and deletion: when you change such a meeting we update its Zoom meeting; when you cancel it, or change its video call away from Zoom, we delete its Zoom meeting.
• Disconnecting: you can disconnect at any time in Settings → Integrations; LoopGantt then also withdraws its permission at Zoom and stops using the connection at once. If you remove LoopGantt from the apps in your Zoom account instead, Zoom tells us and we delete the tokens and Zoom IDs we kept straight away. The Zoom meetings already created stay in your Zoom account.

We do not use data received from Zoom for advertising, do not sell it, do not use it to train AI models, and do not let people read it unless you ask us to for support, it is needed for security or to comply with the law.

Data Storage and Security

Your data is stored in a PostgreSQL database on our own server (see Hostinger above). All connections between your browser and LoopGantt use HTTPS (TLS encryption in transit). Database access is restricted to authenticated application requests through Row Level Security policies, and secrets for connected services (such as calendar connections) are encrypted by the application before they are stored.

We follow security best practices including parameterized database queries, server-side validation, and principle of least privilege for service credentials. However, no system is 100% secure, and we cannot guarantee absolute security.

Authenticated Users

When you create an account, your email address and project data are stored until you delete your account. You can export all your data at any time and request complete account deletion, which permanently removes your email and all associated project data from our database.

Sign-in and sign-up endpoints are rate-limited by IP address to prevent abuse. IP addresses are used solely for rate limiting and are not retained for tracking or profiling.

Your Rights

You have the following rights regarding your data:

• Export your data: You can export any project as JSON or CSV directly from the application at any time.
• Delete your account at any time: You can permanently delete your account from Settings → Danger Zone at any point, or by emailing [email protected]. After you confirm, your account enters a 30-day grace period during which you can cancel by logging in — you retain read-only access and can export all your data as JSON. On day 30, your account, all projects, tasks, comments, attachments, billing records on our side, and personal data are permanently deleted. Your active subscription is automatically cancelled when you initiate deletion (you keep Pro access until the end of your paid period). Payment and tax records held by our payment processor (Lemon Squeezy) may be retained for tax compliance under GDPR Article 17(3)(b) and are outside the scope of this deletion; contact Lemon Squeezy directly if you need those records removed.
• Access your data: You can request a full copy of all data we hold about you by contacting us at the email above.

Cookies

LoopGantt uses the following cookies:

• Authentication cookies — Essential cookies that maintain your login session. These are strictly necessary for the application to function when you are signed in.
• Analytics cookies (Google Analytics) — Used to collect anonymized usage data. These cookies help us understand how the application is used so we can improve it. You can block these through your browser settings. Umami, our other analytics tool, uses no cookies.
• Theme preference — A local storage value (not a tracking cookie) that remembers your dark or light mode preference.

Children’s Privacy

LoopGantt is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If we become aware that we have collected personal information from a child under 13, we will take steps to delete that information promptly. If you believe a child under 13 has provided us with personal information, please contact us at [email protected].

Changes to This Policy

We may update this Privacy Policy from time to time. When we make significant changes, we will update the “Last updated” date at the top of this page. For material changes that affect how we handle your data, we will notify registered users by email. Your continued use of LoopGantt after changes take effect constitutes acceptance of the updated policy.

Contact

If you have questions about this Privacy Policy or how we handle your data, contact us at:

[email protected]

Loopends Studios