If you connect a professional Instagram account, GreetWidgets stores its account identifier, username, token expiration, and an encrypted access token to provide the connection you request. The pilot requests read-only basic profile and media permission; it does not request posting, messaging, or comment management permissions. Access tokens and app secrets are never included in public widgets.

You can disconnect in Your sites → GreetWidgets dashboard → Instagram account. Disconnect removes the stored connection and token and attempts to revoke provider access. You can also remove GreetMode Widgets in Instagram’s Apps and websites settings. Contact us through our contact page for account deletion requests. Public Instagram widgets remain unavailable during launch testing.

When you submit a campaign form, we store the name and email you provide, optional phone/message/custom answers, submission time, and any supported campaign tags on the link. The campaign business can read, export, categorize, and delete its leads. If you choose the optional marketing checkbox, we record that choice, its wording, and the submission time; leaving it unchecked does not block your request. Marketing preferences are not automatically sent to an email service.

The campaign links to the business’s own privacy notice. Please avoid sensitive personal information in form answers or campaign tags. Short-lived one-time form sessions and temporary IP-hashed rate limits help limit duplicate submissions and basic abuse. We record aggregate page requests, outbound-button clicks, and submissions; these are not unique-visitor counts. No full referrer URL or arbitrary query parameters are retained by this feature.

Automatic cleanup removes leads and activity older than 365 days. The campaign business may delete a lead earlier; aggregate activity counts remain until routine cleanup. Downloaded lead exports are controlled by that business. Campaign images may be loaded from an image host chosen by the business. Contact the business or GreetMode about personal data you want removed.

When you submit a GreetFeedback survey, we store your 0–10 score, optional written comment, submission time, and whether you used a QR or standard survey link. The business that owns the survey can read, export, categorize, and delete its responses. No name or email field is requested, but comments may contain personal information you choose to include; please avoid sensitive details.

Short-lived, one-time survey sessions help prevent duplicate submissions. Temporary IP-hashed rate-limit records help limit abuse. Responses are not public Google reviews and are not used to decide who may leave one. Automatic cleanup removes survey responses older than 365 days; the business may delete them earlier. Contact the business or GreetMode about a response you want removed. Exported copies are controlled by the business that downloaded them.

GreetMode only collects the information the service needs to work:

• Owner account details. When an owner creates an account, we store their email address and a password that is hashed and salted (it is never stored or sent in plain text). This is used to log the owner in and to identify their account and sites.
• Site settings. For each site an owner adds, we store the site name, the chat widget color, and the open/closed hours that control whether the widget shows the owner as online or offline. These make the widget look and behave the way the owner configured it.
• Visitor messages and threads. When a visitor sends a chat message or an offline message, we store the message text and, if the visitor chooses to provide them, their name and contact details. This data exists so the owner's inbox can show the conversation and the owner can read and reply to it.
• Contact form submissions. When someone uses our contact page, we store their name, email address, optional company name, and message so we can reply to the inquiry.
• Payment and checkout records. When an owner pays for a plan, we store the email address used at checkout and the plan chosen so the account claim and signup process can complete (including resuming an abandoned checkout). Card and payment details are handled by Stripe — we never see or store card numbers.
• Reply alerts. If an owner enables alerts, we store a browser push subscription and/or an alert email address of the owner's choosing, so we can notify them when a visitor sends a message.
• Login session. Signing in sets a secure session cookie that expires after 30 days. It only keeps the owner logged in.
• GreetProof protection and optional traffic reports. When installed, protection stores short-lived challenges and hashed, single-use tokens, plus the action name, outcome, and time. Optional traffic reporting records coarse timing, visibility, viewport size, browser capability flags, and interaction counts. It does not collect typed text, coordinates, URLs, cookies, or browser storage. Optional reporting stops when Do Not Track or Global Privacy Control is enabled. Protection verification is separate from optional reporting. Managed verification uses Cloudflare Turnstile, which processes browser and network information to assess automated traffic. See Cloudflare's privacy policy. Activity and traffic reports are removed from the application database after 14 days by scheduled cleanup; challenges expire after two minutes. Request limits use IP-derived hashes in temporary server files, cleaned up after 24 hours of inactivity.

Account, site, message, and GreetProof records are stored in a MySQL database on DreamHost operated for GreetMode. Visitor messages are stored for as long as they are needed to operate the owner's inbox; we have no fixed deletion schedule today. If that changes, this policy will be updated. If you would like data removed, see Your rights below.

Plan subscriptions are billed through Stripe, the payment provider. When an owner checks out, card entry happens on Stripe's own hosted payment page. GreetMode never sees or stores full card numbers, and no card details are saved in GreetMode's database.

GreetMode uses two analytics tools on its own website: Google Analytics 4 (GA4) and Microsoft Clarity. They show us how the site is used — for example which steps of the signup and install flow visitors reach, and where people get stuck. The events recorded are deliberately free of personal information: no names, email addresses, IDs, or message text are included. Separately, a small browser storage flag is used to count certain events once per browser rather than once per page view.

Neither tool loads until the visitor chooses to allow it. If you haven't made a choice yet, or you have turned analytics off, nothing is loaded and no data is sent to Google or Microsoft. Both tools are controlled from the same cookie banner, described in Cookies & consent below.

When you visit greetmode.com itself, you'll see a small cookie banner at the bottom of the page. It gives you three choices: Accept all, Reject non-essential, or switch Google Analytics and Microsoft Clarity on or off one at a time and save that. GreetMode's own website uses no advertising or marketing cookies — the two analytics tools above are the only optional ones.

Your choice is stored in your own browser, on your own device, under the name greetmode_consent. It records which of the two analytics tools you allowed and when you made the choice. It is never sent to GreetMode's servers, and it is not tied to an account, an email address, or anything else that identifies you. Clearing your browser storage removes it, and the banner simply asks again next time.

Analytics only run after you allow them. Nothing is loaded before then: the Google Analytics and Clarity scripts are added to the page only when your saved choice includes them, so no analytics data reaches Google or Microsoft until you have decided. Choosing Reject non-essential means the site runs without either tool.

Changed your mind? The Cookie settings link in the footer at the bottom of every page opens the banner again at any time. You can switch either tool on or off from there. Turning a tool off withdraws your permission for it: it stops on the next page and is told to stop collecting (Google Analytics gets a disable flag, Clarity a stop command).

One exception is worth knowing about: the chat widget's embed page shows no cookie banner. That page is built to be embedded on other businesses' websites, so a GreetMode banner appearing there would look like those site owners' own cookie notice. The choice you make here is about the greetmode.com website.

When an owner enables email alerts, alert emails are sent through Resend, our email provider. These emails contain only the site name, a 140-character preview of the new visitor message, and a link to the owner's inbox — never the full message or a visitor's contact details.

GreetMode does not sell or rent personal data, and does not share it for advertising or marketing. The only parties that ever receive data are the service providers needed to run GreetMode — the hosted database, Stripe for payments, Resend for alert emails, and Google Analytics and Microsoft Clarity for usage statistics, each loaded only after a visitor consents. Every provider is used only for the purpose described in this policy.

If you are an owner, visitor, or contact-form sender, you can ask to see what personal data is held about you, or ask to have it deleted, by emailing support@greetmode.com. We'll act on reasonable requests, and we'll never require payment or ask you for anything beyond what's needed to confirm the request is yours.

If this policy changes, the updated version will be posted on this page with a new effective date.