Privacy Policy

Nudgly AI LLC is the controller for personal data we process for the product. If you use Nudgly through a company account, that company may also be a controller for the data it puts into the service.

Account data

• Name, email, and phone number you give at sign up.
• Plan, billing status, and country.
• Persona choice and dashboard settings.

Messages and work data

When you chat with Nudgly we process the messages you send and the replies it writes. If you connect a tool, Nudgly processes the data that connection is used for. Which tools a given account can connect is not the same fact as which tools every account is offered. OWNER CONFIRMATION REQUIRED: the production list of integrations offered to all users, checked from configuration rather than from one account's connection screen.

Usage data

We collect device type, app version, approximate location from IP, and product events such as which integrations you open. This helps us keep the service stable.

We use personal data to run Nudgly, to bill you, to keep accounts safe, and to improve the assistant.

• Deliver messages and complete the actions you request.
• Show daily briefings, reminders, and follow ups.
• Prevent abuse and debug failures.
• Send product mail you can opt out of.

We share data with providers that host the product, send messages, process payments, and generate assistant replies. We do not sell personal data. OWNER CONFIRMATION REQUIRED: the names of those providers and whether any of them use customer content to train generalized models. This policy does not name them, because that list was not verified.

We may share data if the law requires it, to protect people from harm, or if Nudgly is part of a merger or sale. In that last case we will still expect the buyer to respect this policy.

When you chat with your assistant in the Nudgly app, your messages reach our servers so the assistant can reply and use your connected tools.

WhatsApp and Telegram are optional integrations. If you connect one, that app processes the messages that pass through it under its own rules. Read their privacy pages as well as ours.

If you connect a Google account, Nudgly stores the tokens for that connection so it can call Google until you disconnect. What that account can use depends on which Google services that account has connected. One account showing Gmail, Calendar, Docs, Drive, Meet, or Sheets as connected does not, by itself, mean every user is offered those connections. Google's own terms apply to the account you connect.

Gmail and Google Calendar

Where Gmail is connected, Nudgly uses it for the mail actions you ask for, such as reading a thread or preparing a draft. Where Google Calendar is connected, Nudgly uses it for the schedule actions you ask for. OWNER CONFIRMATION REQUIRED: the production OAuth scopes for Gmail and Calendar, including whether send and event-write scopes are requested for every user.

Google Docs, Sheets, and Drive

Docs and Sheets are not described here as read-only. The product can show edit actions for both, and those actions can be set to ask before a change. Drive can show file actions as well. OWNER CONFIRMATION REQUIRED: the production scopes for Docs, Sheets, and Drive, and whether edit actions are available to every user. This policy does not list those scope strings, because they were not verified from production configuration.

Google Meet

Google Meet has appeared as connected on at least one account. The marketing site has also described Meet as coming soon. Those statements conflict, so this policy does not say Meet is unavailable to everyone, and it does not say every user can connect it. OWNER CONFIRMATION REQUIRED: whether Meet is offered to all users, and whether Nudgly joins calls, stores a join link, or receives recordings, transcripts, or participant lists. Until that is confirmed, this policy does not state that Meet content is collected.

What Nudgly does with Google data

Nudgly uses Google data to carry out the user-facing request you made. To produce a reply, that content may be sent to the provider that generates the assistant's response. This policy does not authorise use of Google user data to train or improve generalized AI models. It also does not state the Limited Use commitment. OWNER CONFIRMATION REQUIRED: the model providers in use and whether their contracts and settings prohibit training on Google user data. Do not treat this page as that confirmation.

We do not sell Google user data.

How long Google data is kept, and how disconnect works

Google data fetched into an account is kept while that account is open. You can disconnect a Google service from the dashboard when that control is shown. Disconnecting is meant to stop new access. OWNER CONFIRMATION REQUIRED: whether tokens are deleted at disconnect, what previously fetched copies remain, and how long those copies are kept. This page does not state a number of days.

Zoom has appeared with a Connect control on at least one account. The marketing site has also described Zoom as coming soon. Those statements conflict. This policy does not say Zoom is unavailable to everyone, and it does not say every user can connect it or that Nudgly joins Zoom calls.

If your account offers Zoom and you connect it, Nudgly receives only the access that connect step requests. OWNER CONFIRMATION REQUIRED: whether Zoom is enabled for all users, the production scopes, and whether Nudgly can list meetings, create meetings, join calls, or receive recordings, transcripts, chat, or participant lists. Until that is confirmed, this policy does not state that any of that Zoom content is collected, and it does not name a Zoom processor or a Zoom retention period.

The same caution applies to Google Meet, described above. Disconnect and account deletion for either service follow the Google disconnect section and How long we keep data. OWNER CONFIRMATION REQUIRED: the exact deletion steps for a Zoom connection.

We keep account data while the account is open. When you delete the account we delete or anonymise personal data, except records we must keep. OWNER CONFIRMATION REQUIRED: how account deletion works in the product, how long data remains afterward, and which records are kept for tax, disputes, or security. This page does not state a number of days.

Disconnecting an integration is meant to stop new access to that service. OWNER CONFIRMATION REQUIRED: whether stored tokens are deleted at disconnect, and whether previously fetched copies remain until account deletion.

Depending on where you live, you may ask to access, correct, export, or delete your data, or to object to certain processing. You can also withdraw consent where we relied on it.

Send requests to team@nudgly.io. We may need to confirm it is you. You can also complain to your local data authority.

OWNER CONFIRMATION REQUIRED: which security controls are in place. This policy does not state encryption in transit, encryption at rest, staff access limits, certifications, or security assessments, because those facts were not verified. Tell us at team@nudgly.io if you think there is a security issue.

Nudgly is not directed at children under 18. We do not knowingly collect their data. If you believe a child has created an account, contact us and we will close it.

We may update this page as the product changes. The date at the top is the latest version. If a change is material we will send a note to the email on your account.