MERCHUNO

Privacy policy

Effective November 6, 2026.

Information we use

Merchuno receives your account identifier, email address, and available profile name when you sign in. We store the business details, prompts, website content, domain choices, and saved revisions you provide. We also store subscription status, payment-provider identifiers, hosting records, and support correspondence.

Our providers may process technical information such as IP addresses, browser details, security events, and service logs to deliver and protect the service. Stripe processes your payment details; Merchuno does not store your full card number.

Free website applications

If you apply for a free website build, we store your submitted contact and business details, website needs, existing hosting and hosting preferences, and any campaign labels included in the application link. Authorized Merchuno staff review applications privately and may contact selected applicants about their project. Applications do not create customer accounts, start subscriptions or website builds, or enroll you in automated follow-up emails. We use short-lived, hashed rate-limit keys to prevent spam. To ask us to remove an application, email support@merchuno.co.

Website inquiries and embedded tools

When someone submits a contact or quote form on a website hosted by Merchuno, we store their submitted answers, uploaded files, and the originating page in the website owner’s private Merchuno inbox. We use limited technical data to prevent spam and duplicate submissions. We email the website owner a notification that includes the submitted answers and the names of any uploaded files. Uploaded files require authenticated access through Merchuno and are not published as website media. These inquiries are available to the website owner and are retained with their account. For native appointments, we store the visitor’s name, email, phone, property address, project notes, selected time, time zone, and appointment status. The website owner manages requests and appointments in Merchuno. We email appointment receipts and status updates to the visitor and, when enabled, notifications to the website owner. If the website owner connects Google Calendar or Microsoft Outlook/Microsoft 365, we check selected calendars for busy times and can copy appointment details (service, customer name, email, phone, property address, time, and status) to the calendar they select. We retain busy intervals and event identifiers, rather than personal event titles or descriptions. Calendar access tokens are stored encrypted. Owners can disconnect their calendars in appointment settings; a completed disconnect removes events created by Merchuno and deletes our saved connection credentials. If provider access is unavailable, owners can erase the saved connection and remove any remaining exported events in the calendar app. The original personal calendar events are not deleted. Retained third-party booking, map, and video embeds connect visitors directly to their provider, which processes information under its own policies.

How we use information

We use information to create and edit your website, save your work, provide hosting, process subscriptions, prevent abuse, recover from failures, and respond to support requests. Content you choose to publish, including business contact details, becomes publicly available on your website.

If you create a website draft without becoming a paying customer, we may send up to four follow-up emails to help you review it, make changes, or choose a plan. These messages use your account email address and link to your private website studio. Each includes an unsubscribe option. A first payment or an unsubscribe stops the sequence. We retain your email preference to honor your choice; unsubscribing does not stop essential account, security, or billing messages.

Optional ChatGPT connection

If you connect Merchuno to ChatGPT, the permissions you approve allow ChatGPT to retrieve your account profile, website drafts, migration progress, launch details and, when requested, contact inquiries. With the relevant permissions, ChatGPT can also request website imports and edits, publish a version you approve, and prepare or verify a custom domain. Information returned to ChatGPT is handled under your OpenAI account and workspace settings. Your Merchuno password, model API keys and full payment details are not sent to ChatGPT by this connection. We retain hashed authorization tokens and connection records to secure this access. You can revoke the connection on the Merchuno ChatGPT page or in ChatGPT. Revocation stops subsequent access; it does not delete information already returned to your conversations. The plugin does not have access to your DNS provider account.

Google account and calendar data

Google sign-in

If you choose Google sign-in, Merchuno receives and stores your Google account identifier, verified email address, and available profile name to identify your account and let you sign in. Basic sign-in does not grant access to Gmail messages, contacts, calendar events, or Google Drive files.

Optional Google Calendar access

You separately authorize calendar access from your website’s appointment settings. Merchuno requests calendar.calendarlist.readonly to list your calendars and calendar.events to check availability and manage appointment events. These permissions allow event changes; Merchuno uses them only for the scheduling features described here.

Public booking pages show available appointment times, not your personal event details or calendar names. Google account and calendar data is used for sign-in, scheduling, synchronization, and maintaining the security and reliability of those features. It is not sent to our AI-generation providers or used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models.

Sharing and protection of Google data

Google calendar data passes through Cloudflare, which runs Merchuno and stores its application data. Google receives authorization requests and appointment changes. We do not sell Google user data or disclose it to advertisers or data brokers. We do not use it for advertising, credit, or lending decisions. Any other disclosure is limited to operating the features you authorize, necessary security investigations, or legal requirements. Human access is limited to your permission for specific support needs, necessary security investigations, or legal requirements. We protect private account data with access controls, use HTTPS in transit, and encrypt saved calendar tokens.

Merchuno follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs.

Disconnecting and deleting Google data

You can change calendar selections or disconnect in Merchuno’s appointment settings. A completed disconnect removes Merchuno-created events from the provider and deletes the saved connection, encrypted tokens, calendar list, busy intervals, and event mappings from our active database. Your original personal calendar events and native Merchuno appointment records are kept.

You can also revoke permission in your Google Account connections. Revocation stops further access but does not itself delete data already stored in Merchuno. If revoked access prevents cleanup, Merchuno offers an option to erase the saved connection; you then remove remaining Merchuno-created events in Google Calendar. Google sign-in information stays with your Merchuno account, and calendar connection data stays until disconnect or deletion. To request deletion of your account, sign-in information, or appointment records, open a ticket with Merchuno Support. Backup copies may remain until their retention cycle ends.

Support tickets

When you open a support ticket, we store its subject, category, priority, associated website, messages, and uploaded files. You and authorized support staff can access the conversation. Staff may keep private notes that are not shown to customers. We record ticket status, assignment, and read activity to manage requests. Files remain private and require permission to download. Support conversations are handled in your account rather than through personal staff email addresses.

Service providers

Amazon Cognito processes email/password registration, sign-in, email verification, and password recovery. If you choose Google sign-in, Google shares your account identifier, verified email address, and available profile name with Merchuno to create or access your account. Basic Google sign-in does not request access to Gmail messages, contacts, calendars, or Google Drive files. Calendar access is a separate, optional connection authorized by the website owner. Google and Microsoft process calendar authorization and synchronization. Access continues until disconnected or revoked at the provider. OpenAI processes AI-generation requests. OpenAI Sites and Cloudflare deliver the application, published websites, and their storage; Amazon Web Services provides account sign-in, email delivery, and the network entry point for customer domains. Stripe processes billing. Domain queries may be sent to DNSimple to check availability and pricing. Support tickets are stored in Merchuno, with files held in private storage. These providers receive the information needed for their services and apply their own privacy and security terms.

Do not include sensitive personal information, payment card details, passwords, or private customer records in website-generation prompts. Use only business content you are authorized to share and publish.

Optional ad measurement

If you enable “Marketing measurement” or choose “Accept all,” Merchuno uses a first-party cookie for up to 90 days to connect an ad visit with a completed account registration, checkout, and successful payment. We send Meta an anonymous measurement identifier, an available Meta ad-click or browser identifier, limited browser and network information, the event time, and payment amount and currency. Payment events come from Stripe-confirmed paid invoices. Free registrations, first paid customers, and subsequent invoice payments are separate events. We do not send names, email addresses, card details, Google account or calendar data, support messages, prompts, or the content of your website to Meta.

This optional measurement applies to Merchuno’s own application, not the websites we host for customers. Declining does not affect your account, payments, or hosting. You can change your choice using “Cookie preferences.” We honor Global Privacy Control and Do Not Track signals. Withdrawing your choice stops future sharing and cancels measurement events that have not been sent. Events already received by Meta are handled under Meta’s privacy policy. Browser matching data expires after 90 days; payment and delivery records may be retained for reconciliation, security, and legal purposes.

Optional Google Analytics

If you enable “Analytics” or choose “Accept all,” Google Analytics helps us understand visits to Merchuno, signup form starts and submissions, verified account registrations, checkout starts, and confirmed paid invoices. We send anonymous browser and session identifiers, general Merchuno page paths, the originating website’s domain, conventional campaign tags when available, event times, and payment amount and currency with an anonymous transaction identifier. Google also receives browser and network information when its analytics tag loads. We remove private page identifiers, search queries, and URL fragments, and we do not send names, emails, passwords, Google sign-in or calendar data, form contents, prompts, support messages, or customer website content. Advertising personalization and Google signals are disabled.

Google Analytics is separate from Google sign-in and calendar connections. Previous permission for Meta measurement does not activate Google Analytics: visitors must make a new measurement choice. Google Analytics loads only after permission, and it is not installed on customer-hosted websites. Anonymous browser matching lasts up to 90 days. You can withdraw through “Cookie preferences”; we stop future collection and cancel unsent server events. GPC and Do Not Track signals disable optional measurement. Information already received by Google is handled under Google’s privacy policy. Declining does not change your access to Merchuno.

Cookies and security

Choose “Customize” in the cookie notice or open “Cookie preferences” to control Analytics and Marketing measurement separately. Essential cookies stay on to provide the service. “Reject all” disables both optional categories; “Save choices” applies your selected categories.

Sign-in, security, and payment services may use cookies and similar technology necessary for their functions. Optional ad-measurement and analytics cookies require your choice as described above. We do not use the information you provide to sell advertising profiles. We use access controls, encrypted service credentials, and HTTPS to help protect your information, but no system can guarantee absolute security.

Retention and your choices

Saved drafts, revisions, and hosting data are retained to provide your account and recovery features. Canceling a subscription does not automatically delete your account or website data. Some billing, security, and dispute records may need to be kept for legal or operational reasons. Backup copies may remain until their retention cycle ends.

You can edit your website information and download a WordPress export through your account. To request access, correction, or deletion of personal information, open a ticket with Merchuno Support. We may verify your identity before fulfilling a request. Your information may be processed in the United States and other countries where our providers operate.

Contact and updates

Merchuno is intended for business users, not children. Contact Merchuno Support with privacy questions. We will update the effective date when this policy changes and provide additional notice when required. If the purposes for accessing Google user data change, we will disclose the change and obtain any required new consent before using it for that purpose.