← Doplando

Privacy Policy

Last updated: August 2026

Doplando ("we", "us", "our") provides a task and team management application at doplando.com (the "Service"). This Privacy Policy explains what information we collect, how we use it, and the choices you have.

1. Information we collect

  • Account information. When you sign in with Google, we receive your name, email address, and profile picture via Firebase Authentication. We do not receive or store your Google password.
  • Content you create. Tasks, projects, offices/teams, quality-gate checklists, inspections, directions, meeting notes, brainstorm sessions, and any text, files, or messages you enter into the Service.
  • Team communication. Direct messages you send to teammates within the Service, and a lightweight "last active" timestamp used to show whether a teammate is currently online.
  • Contact details for reminders. If you enable WhatsApp or push notifications, we store the phone number or device token needed to deliver them.
  • Billing information. If you purchase credits or a subscription, payment is processed by Stripe or Razorpay. We do not receive or store your card number — only the resulting transaction status and amount.
  • Usage data. Basic technical logs (timestamps, error reports) used to keep the Service reliable.

2. Google user data — Contacts ("Invite Friends")

If you choose to use the optional "Invite Friends" feature, we ask for permission to read your Google Contacts and "Other contacts" (people you've corresponded with in Gmail), using Google's People API. This is entirely opt-in — we never request this access as part of normal sign-in.

  • We use this data only to show you a list of names/email addresses so you can pick who to invite.
  • The Google access token used to fetch this list is used once, server-side, for that single request, and is never stored.
  • We do not store your full contact list. We only retain the email addresses you explicitly select and send an invite to, so we can track whether that invite was accepted and credit your account.
  • We do not sell, share, or use your contacts for advertising, and we do not access this data unless you actively click "Connect Gmail Contacts."
  • You can revoke this access at any time from your Google Account permissions page.

3. Google user data — Sending email ("Waiting on Others")

If you park a task as pending with an outside party and choose to send them a follow-up, we ask for permission to send email on your behalf, using the Gmail API (gmail.send scope). This is entirely opt-in — we never request this access as part of normal sign-in, and we ask for it each time you send.

  • We use this access only to send the single follow-up message you have written and reviewed on screen, to the one recipient you specified. Nothing is sent automatically or in the background.
  • We cannot read your email. gmail.send grants send-only access — it does not permit reading, searching, or listing any message in your mailbox, including the ones we send.
  • The Google access token is used once, server-side, for that single send, and is never stored.
  • The message is sent from your own Gmail address so the recipient sees a person they recognise and their reply reaches your inbox; a copy stays in your Gmail Sent folder, under your control. We retain only the fact that a reminder was sent and when, so the task can show how many times you have chased.
  • We do not sell or share this access, and we do not use it for advertising.
  • You can revoke this access at any time from your Google Account permissions page.

Doplando's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

4. How we use information

We use your information to operate and improve the Service: to show your tasks and your team's data to the right people, to send the reminders and notifications you've configured, to process payments you've requested, and to respond to support requests. Some features (for example, generating meeting minutes from a transcript) send the relevant content to a third-party AI provider to produce that output; the content is used only to fulfil your request and is not used to train third-party models on our behalf.

5. Where your data is stored

Data is stored using Google Firebase/Firestore and Google Cloud infrastructure, encrypted in transit (HTTPS/TLS). Access is protected by per-user authentication and access-control rules so that team data is only visible to people you've explicitly added to that team/office.

6. Sharing

We do not sell your personal information. We share data only with: (a) other members of an office/team you've joined, limited to what that team context requires; (b) service providers who process data on our behalf (Google Firebase, Stripe, Razorpay, Twilio for WhatsApp delivery, and email delivery via Gmail SMTP), bound to use it only to provide their service to us; and (c) authorities where required by law.

7. Your choices and rights

  • You can review and edit most of your data directly within the app.
  • You can disconnect Google Contacts access at any time (see section 2).
  • You can request export or deletion of your account and associated data by contacting us (see section 9) — we'll act on verified requests within a reasonable time.
  • Turning off notification channels (email/WhatsApp/push) stops those specific deliveries; you can re-enable them anytime from Settings → Reminders.

8. Data retention

We retain your data for as long as your account is active. If you request account deletion, we remove your personal data and content within a reasonable period, except where retention is required for legal, security, or billing-record purposes.

9. Children's privacy

The Service is not directed at children under 13, and we do not knowingly collect personal information from them.

10. Contact us

Questions about this policy or a request about your data? Use the Contact option available on the sign-in page and in the app footer, and we'll respond to you directly.

11. Changes to this policy

We may update this policy as the Service evolves. Material changes will be reflected by updating the "Last updated" date above.