Privacy Policy
Last updated: October 26, 2026
This policy describes how Synaty Marketing Inc. handles personal information when you visit our website, contact us, use our client portal, or communicate with our team. When a client enters information about its own customers in the portal, we use that information to provide the client-requested service; the client is responsible for its own relationship with those people and any notices or permissions it must provide.
Information we handle
- Information you provide: names, email addresses, phone numbers, business and project details, messages, applications, and other information you choose to send through our forms or communications.
- Portal information: account and contact details, records and content entered by clients (which may include their customers’ contact details, consent status, and communications), tasks, campaigns, and settings needed to operate the service. When Resend handles a campaign, we also receive provider message identifiers and delivery-event information for that campaign.
- Payments: website-project and subscription checkout is handled by Stripe. Payment-card details are entered directly with Stripe; Synaty does not receive or store full card numbers. For a website application, the submitted contact email and project brief are also attached to the Stripe checkout session so we can match the paid order to the application. We receive checkout, subscription, payment-status, amount, and customer identifiers needed to administer the transaction.
- Necessary cookies and request information: authentication and cross-site request protection use first-party cookies. Our server and abuse-prevention controls also process technical connection information, such as IP address, request time, and browser/request details, to operate, secure, and troubleshoot the service.
- Optional analytics on Synaty's public website: only after you select “Accept optional analytics,” our site stores a first-party visitor ID and your choice in browser storage. For page visits, we record the page path, referring site's origin (not the full referring URL), and a broad device category. These analytics events do not include an IP address, full URL, or advertising identifier. You can reject or withdraw consent using “Privacy preferences” in the site footer.
- Analytics on a client's website: when a client installs Synaty Analytics on a site it controls, the tracker sends page views and optional named events to a client-specific property. The event data includes a page path without query/hash, referring-site origin, broad device category, event type/name, and a property-specific hash of a browser-session identifier. The tracker does not read form fields or send raw IP addresses, full URLs, or advertising IDs. Consent behavior depends on the property's setting; consent is required by default, and the client is responsible for its own privacy notice, consent manager, and legal basis. Do not include personal information in page paths or event names.
- Connected social/ad accounts: when a client authorizes Meta, we receive and store the app-scoped Meta account identifier needed to associate and honor deletion requests, Facebook/Instagram professional-account and Page information, posts and available insights, and Meta ad-account campaign metrics needed for the requested reporting. The authorization tokens are stored server-side in encrypted form and are not shown in the client portal. A client can remove a local connection, use Meta's data-deletion request flow, and revoke Synaty's authorization in its Meta Business Integrations settings.
- Google Business Profile reviews: when a client connects a Google account and selects a profile location, Synaty stores that location's name and address and, only after the client requests a sync, the reviewer's display name, rating, review text, review timestamps, and any existing business reply returned by Google's API. The Google refresh token is encrypted server-side and is never returned to browser code. Google requires the
business.manageOAuth permission, which is broader than read-only; Synaty currently uses it only to list profile locations and read reviews, without editing profiles or posting replies. - Shared website preview visit counts: when you open a Synaty-hosted client preview, we use a random, first-party, HTTP-only browser cookie (expires after 12 months) to count unique browsers and group the same browser across preview sites. The preview counter stores only a keyed hash of that random ID, preview IDs, and first/last visit timestamps; it does not put the raw cookie value, IP address, user-agent, referrer, page path, name, or email in preview-view records. Common link-preview bots and authenticated Synaty admin views are excluded. These pseudonymous counts and groups are available only to authorized administrators; a browser/device is not a verified person, and clearing/blocking cookies or using another browser/device can create a separate count.
- Site chat: opening the chat creates a random visitor ID in that browser tab’s session storage. Opening the chat alone does not create a server-side prospect record. If you send a message, we store the message text and ID in a chat prospect record, with a system-generated placeholder email address; the widget uses the ID to check for our reply while the chat is open. You do not need to provide your name or email to use the chat.
How we use information
We use information to respond to requests, deliver and administer services, operate accounts and requested integrations, process transactions, provide customer support, maintain security, prevent abuse, and meet legal obligations. Optional website analytics are used to understand which pages are useful. Marketing email and SMS are sent only when applicable consent and suppression checks permit; service and transactional messages may be sent to carry out a request or manage an account.
Service providers and sharing
We share information with service providers when needed to operate a feature you or a client requests. These may include Cloudflare for DNS, traffic delivery, or security; Stripe for checkout and payments; the configured email provider (such as Resend or an SMTP service); and Twilio for SMS and voice. When Resend is configured for campaign email, its signed callbacks may report delivery, bounce, complaint, open, and click events; open and click counts depend on provider reporting and are not definitive proof that a person viewed or acted on a message. If an AI feature is used, the prompt and any selected text or workspace data included with it may be processed by the AI provider configured for the service—such as a self-hosted Ollama model, Google Gemini, OpenAI, or another compatible provider. Please avoid submitting sensitive information to an AI feature unless you are authorized to do so.
Other optional integrations include public OpenStreetMap search services when a client searches for business leads (no Google Places API key or billing account is used), GitHub when a client requests a repository preview, Meta when a client authorizes Facebook/Instagram account insights or ad-account campaign reporting, and Google's official Business Profile APIs when a client connects a profile to import reviews. The review integration does not use Google Places or require Google billing. Website-analytics events from a client's site are received by Synaty for that client's portal reporting; we do not send them to Meta. Meta's available metrics and reporting times are controlled by Meta. A client-configured webhook sends the event information selected by that client to the destination it specifies. Each provider handles information under its own terms and privacy practices. These providers may process information outside Ontario or Canada.
We do not sell personal information. We do not use third-party advertising pixels or advertising trackers on our public marketing website. We may disclose information if required by law or when reasonably necessary to protect people, the service, or our legal rights. If error-monitoring services are enabled in the server configuration, limited technical error or performance information may also be sent to that provider.
Retention
Synaty public-site analytics events, client-site analytics events, preview viewer groups, Meta insight snapshots, and hashed Meta deletion-confirmation records are automatically deleted after 13 months; preview viewer groups are also removed when their preview is deleted, and expired Meta and Google OAuth state is deleted by the daily cleanup. Encrypted Google Business Profile authorization tokens, saved profile locations, and imported review records remain until the client disconnects the integration or the client account is deleted. Disconnecting removes the local token and imported review data and asks Google to revoke authorization; clients can also review or revoke app access in their Google Account. Encrypted Meta authorization tokens and account connections remain until the client removes the local connection, a verified Meta deletion request is processed, or the client account is deleted; revoking Synaty in Meta's settings is also recommended. Chat-only prospect records are automatically deleted 90 days after the first message creates the record. For Resend campaign events, the recipient-email mapping is removed from local delivery records after 90 days; provider message identifiers and campaign-level event totals remain with the campaign until it is deleted. We retain email and SMS opt-out or bounce/complaint suppression records as needed to respect those choices and prevent further marketing messages. Other inquiry, project, billing, account, and client-entered records are kept for as long as reasonably needed to provide the service, meet legal or accounting obligations, and resolve disputes. Technical logs are retained for security and troubleshooting under the server’s operational log practices. Providers may keep information under their own retention policies.
Security
We use HTTPS, access controls, password hashing, and other safeguards appropriate to the service. Meta authorization tokens used for Facebook, Instagram, and advertising reporting and Google Business Profile refresh tokens are encrypted in the application database and are not returned to browser code. No internet service can be guaranteed completely secure; use a unique password and contact us promptly if you suspect unauthorized access.
Your choices and privacy requests
On Synaty's public website, you can decline optional analytics or withdraw consent using “Privacy preferences” in the footer. When you reject those public-site analytics, the site removes its analytics ID from that browser and sends a request to delete events associated with that ID. For analytics on a client's website, use that site's consent manager; withdrawing consent stops future collection but does not automatically delete previously received events. Contact that site's owner for a data request; the client can ask Synaty to remove the property's event history. A client can disconnect Google Business Profile from the reputation dashboard to delete Synaty's saved token, locations, and imported reviews. Browser settings can also clear first-party local or session storage; clearing the preview-viewer cookie causes later visits to be counted as a new browser group. To ask a privacy question or request access, correction, or deletion of personal information, email [email protected]. We will review requests subject to applicable law and records we must retain.
Policy updates
We may update this policy as the service changes. The current version and its revision date will be posted on this page.