You choose the apps, inputs and actions. This policy explains the data Nudge needs to run them, including Google connections and AI processing.
Who we are
Nudge AI (“Nudge”, “we”, “us”) is a workflow automation service at nudge.flazetech.in. This policy explains how we handle information when you visit the site, create an account, connect an app, or run a workflow.
Read About us for more about the service and Terms of Service for the rules that apply to using it.
Information we handle
- Account information: your email address, name if provided, account identifier and sign-in information. Email/password accounts use a password hash; we do not store the original password.
- Workflow information: the workflows you save, prompts, settings, incoming data, execution inputs and outputs, error details, and optional agent conversation history.
- Connections and credentials: connected-account identifiers, granted permissions, Google access and refresh tokens, and personal AI provider keys you choose to save.
- Usage and technical information: run counts, token and credit usage, timestamps, session information and technical logs used to operate, troubleshoot and protect the service. Server logs may include request metadata such as IP addresses and user agents.
- Support information: information you choose to send when asking for help or making a privacy request.
Workflow data can include information about other people. Only provide data you are authorized to process, and limit it to what your workflow needs.
Google account data
Google sign-in and Google connector access are separate actions. Signing in does not by itself give Nudge access to your Gmail messages or spreadsheets.
| Feature | Data and use |
|---|---|
| Sign in with Google | Basic identity permissions (openid, email and profile) identify your Google account and let you sign in to Nudge. We use the returned account ID, email and available name to establish your account and session. |
| Gmail connector | The gmail.send permission sends emails that your configured workflow creates, including the recipient, subject and message body you supply. The current connector does not request permission to read your Gmail inbox. |
| Google Sheets connector | The spreadsheets permission reads or writes spreadsheet content at the spreadsheet and worksheet selected in your workflow. It can include cell values, ranges and the results of row operations. |
The connector consent flow currently requests Gmail sending and Google Sheets access together. The permission screen shows the requested access; you can decline it. Granted tokens let Nudge run the connected steps you configure, including scheduled and webhook-triggered runs while you are away.
We use Google API data to deliver the workflows you request. We follow the Google API Services User Data Policy, including its Limited Use requirements. We do not sell Google API data, use it for advertising or credit decisions, or use it to train general-purpose AI models.
Access by Nudge personnel to Google API data is limited to your affirmative permission for specific data, necessary security investigations, legal obligations, or permitted aggregated internal operations. These restrictions also apply to data derived from Google APIs.
How we use information
We use information to create and authenticate accounts, save and execute workflows, deliver actions to the services you select, display results, manage usage limits, answer support requests, and detect or investigate abuse and technical failures.
We do not sell personal information. We do not use Google API data for purposes unrelated to the visible workflow features you choose.
Storage and retention
Saved accounts and workflows are retained to provide your workspace until they are deleted or no longer needed. Execution history can contain your workflow inputs, outputs and error messages; older records are removed as the service’s history storage limit is reached. It is not a permanent archive.
Google tokens are retained until you disconnect the saved connection or they are removed as part of a deletion request. Personal AI keys are retained until replaced or removed. Optional agent session memory expires after 24 hours of inactivity; expired records are cleaned up during memory operations. Execution history may separately contain the same input or output.
Operational logs and any backups may retain information after it is removed from the active workspace. We limit continued retention to operational, security and legal needs. Contact us for account-specific deletion and retention questions; we may need to verify your identity before acting.
How information is protected
The public service uses HTTPS. Access to accounts, workflows and saved connections is controlled on the server. Passwords are hashed, and saved personal AI provider keys are encrypted before storage. Google connector tokens are stored on the backend and are not exposed in workflow exports.
Keep your account, webhook URLs and credentials private. Avoid putting secrets directly in prompts, workflow fields or support messages: workflow definitions and execution history can make their contents visible to people with workspace access. No online service can guarantee absolute security.
Your choices and deletion
- Use email/password sign-in if you do not want to use Google sign-in.
- Pause workflows to stop their automatic triggers. Review and delete workflows you no longer need.
- Remove a connected Google account on the Connections page. This removes Nudge’s stored connector credentials; it does not delete your Google account or information already written to Google.
- Revoke Nudge’s Google authorization in your Google Account’s third-party connections. Workflows relying on that authorization may then fail until you reconnect.
- Remove a personal AI key from Chat Model settings. Export workflow definitions from the builder when you need a copy.
- Contact us to request access, correction, deletion of account or stored workflow data, or assistance with other applicable privacy rights. Disconnecting Google alone does not delete existing execution history.
For questions about Nudge, support, privacy, or account and data deletion, email contact@flazetech.in. Include the email address associated with your Nudge account so we can help identify it. Do not send passwords, API keys or other credentials.
Children and policy changes
Nudge is a work automation service intended for people who can lawfully use it and authorize its connected services. It is not directed to children under 13. Contact us if you believe a child has provided personal information.
We may update this policy as the service changes. The date at the top identifies the current version. If a change requires new consent for Google data access or use, we will seek that consent before using the data in the new way.
Contact us
For questions about Nudge, support, privacy, or account and data deletion, email contact@flazetech.in. Include the email address associated with your Nudge account so we can help identify it. Do not send passwords, API keys or other credentials.