Privacy Policy

We collect the information needed to run the service.

• Contact details, such as account email addresses, billing contacts, and support correspondence
• Authentication and account-security details, such as password hashes, email-verification state, linked Google account identifiers, multi-factor authentication settings, recovery artifacts, and portal session records
• Account and setup details, such as Frontline connected mailboxes, docs uploaded for context, workspace settings, Stripe app setup, notes, and dashboard preferences
• For NoticeDock Stripe apps, Stripe account ID, relevant Stripe object data, app settings, and operational data such as subscription, entitlement, app-installation, deauthorization, billing-status, and webhook-event information. For Billing Ops, this may include customer and invoice metadata, invoice status, amount remaining, notes, and workflow history. For Payment Link and Coupon Loss Guard, this may include active Payment Links, Coupons, promotion codes, Products, Prices, and related configuration needed to perform a review
• Billing and subscription information processed through a third-party payment provider
• Technical and usage information, such as IP address, browser details, device/session details, and service logs used for security and reliability
• Support and recovery details, such as login-help requests, email-rescue requests, admin email change requests, and follow-up notes needed to review those requests safely

We use information to provide, support, and protect NoticeDock.

• To run Frontline AI support, Billing Ops Stripe sync, Payment Link and Coupon Loss Guard reviews, portal dashboard sessions, and related product features
• To use Stripe data in NoticeDock Billing Ops so the app can show invoice workflow context, including customer details, invoice status, amount remaining, notes, and history
• To use Stripe data in Payment Link and Coupon Loss Guard to identify pricing, currency, trial, billing schedule, checkout, discount, expiry, redemption-limit, and restriction differences for review
• To manage subscriptions, billing, post-payment dashboard access, and account support
• To verify password logins, Google sign-in, email verification, password reset, multi-factor authentication, and account-recovery requests
• To investigate issues, improve reliability, and maintain security
• To prevent abuse, fraud, unauthorized access, and misuse of the service
• To comply with legal obligations when required

Frontline may process support data with AI providers.

When Frontline is enabled, NoticeDock may process relevant support docs, workspace settings, primary-inbox customer messages, reply drafts, and conversation context with AI and infrastructure providers, including OpenAI API services, so Frontline can classify messages, draft replies, apply escalation settings, and operate the service.

Uploaded docs and customer messages are treated as customer-provided support context. They do not override NoticeDock safety rules, escalation settings, signature handling, or internal protections.

OpenAI states that API data is not used to train or improve OpenAI models by default unless the customer opts in.

NoticeDock Stripe apps use Stripe data to provide their app features.

For NoticeDock Billing Ops, we use Stripe data so the app can show invoice workflow context inside the product. That may include Stripe account ID, customer and invoice metadata, invoice status, amount remaining, webhook event metadata, app settings, notes, and workflow history.

Stripe API keys and secrets are protected and are not shown in the NoticeDock user interface.

Payment Link and Coupon Loss Guard is a read-only Stripe app. It may access the connected Stripe account ID and relevant Stripe object data needed to perform its review, including active Payment Links, Coupons, promotion codes, Products, Prices, and related configuration. It uses that data to identify pricing, currency, trial, billing schedule, checkout, discount, expiry, redemption-limit, and restriction differences.

Payment Link and Coupon Loss Guard does not create, edit, or delete Stripe objects. Stripe app operations may also involve subscription, entitlement, app-installation, deauthorization, billing-status, and webhook-event information needed to provide, secure, and support the apps.

We use necessary cookies and session records to keep the portal secure.

NoticeDock uses necessary cookies and related session records to keep signed-in customers in the portal, move safely between secure dashboard pages, protect export and proof-file downloads, and sign customers out when a session expires or is revoked.

These session controls are used for authentication, security, and service operation. They are not used to sell advertising profiles.

We use account-security data to verify that the right person is accessing the right account.

Existing NoticeDock accounts can sign in with email and password, or with Google after a matching Google account has been linked. Google sign-in is offered only when the Google account email matches the existing NoticeDock login email, and the first successful match may link that Google account for future sign-in.

If multi-factor authentication is enabled, NoticeDock may ask for an authenticator code or recovery code after sign-in. When customers request login help, email rescue, or an admin email change, we may use the request details, account records, session data, and support history to review the request and decide what safe next step to offer.

Frontline connects only the mailbox features needed to handle support email.

Frontline is a support inbox assistant. Customers can connect a support mailbox through Microsoft OAuth or SMTP/manual provider settings. Frontline is designed to read the connected mailbox primary inbox only. It does not intentionally poll Spam, Junk, Trash, All Mail, or custom folders. Gmail and Google Workspace support inboxes should use SMTP/manual setup with an app password where available. Google sign-in for NoticeDock login is separate from Frontline mailbox access.

• Google sign-in for NoticeDock login: Customers may use Google sign-in for their NoticeDock portal account. That sign-in method does not connect a Gmail or Google Workspace support inbox to Frontline.
• Gmail and Google Workspace support inboxes: NoticeDock does not currently offer direct Google-hosted mailbox OAuth for Frontline mailbox connection. Gmail and Google Workspace support inboxes should use SMTP/manual setup with an app password where available.
• Future Google API terms: If NoticeDock enables direct Google-hosted mailbox APIs in the future, additional Google API data terms will apply. Google Workspace API data would be used only to provide user-authorized Frontline mailbox functionality. NoticeDock would not use Google Workspace API data, including Gmail data, to develop, improve, or train generalized or non-personalized AI or ML models, and would not sell Google user data or use Google user data for advertising.
• Microsoft OAuth / Outlook / Microsoft 365: Frontline requests Microsoft identity and mail permissions only to identify the connected Microsoft account, read incoming support emails from the connected Outlook or Microsoft 365 primary inbox, and send support replies from that same mailbox.
• Microsoft mailbox limits: Frontline does not delete, archive, label, modify, export, back up, sell, or change Microsoft mailbox messages or settings.
• SMTP/manual setup: If you choose SMTP/manual setup, Frontline stores the mailbox and server settings needed to read the primary inbox and send replies. You are responsible for providing credentials and settings for a mailbox you own or are authorized to use.
• Support email content: Incoming support messages are used only to decide whether a reply is needed, generate a reply from uploaded support docs and workspace settings, route or escalate requests, and maintain operational history. Uploaded support docs are used only for support-answer generation and escalation logic.
• Data controls: Customers can disconnect mailbox integrations, remove workspace details from the dashboard, and remove uploaded support docs. Billing and account records may still be retained as required for accounting, fraud prevention, legal compliance, and service operations.

We use third-party providers to help operate the service.

NoticeDock may use providers for hosting, infrastructure, authentication, payment processing, email delivery, file storage, analytics, and customer support operations. Those providers may process information only as needed to help us operate the service.

We do not sell your personal information.

We keep information for as long as it is needed to operate NoticeDock.

We may retain account records, support messages, service logs, security and session records, and product configuration details while an account is active and for a reasonable period afterward for support, security, recordkeeping, fraud prevention, and legal compliance.

We use reasonable safeguards to protect information.

We take reasonable steps to protect information against unauthorized access, disclosure, misuse, and account takeover. That can include access controls, authentication checks, session management, verification flows, and review of suspicious recovery or login activity. No method of storage, transmission, or internet service can be guaranteed completely secure.

You can contact us about access, correction, or deletion requests.

Signed-in customers can use account settings and support flows to manage passwords, request email verification, manage Google sign-in, manage multi-factor authentication, or request an admin email change. To update account information, request deletion, or ask a privacy-related question, email support@noticedock.com. We review requests in line with our legal obligations, service requirements, and account-security checks.

We may update this Privacy Policy from time to time.

When this policy changes, we will update this page and revise the effective date shown above.

Questions about privacy

For privacy questions or requests, contact support@noticedock.com.