Privacy Policy

Last Updated: June 24, 2026

Yahmation, LLC ("we," "us," or "our") respects your privacy. This Privacy Policy explains how we collect, use, and share information when you visit our website or use our services, including our Form Builder, Yahmation Flow, and Yahmation Client Portal applications.

1. Information We Collect

We may collect:

• Name
• Email address
• Phone number
• Business details
• IP address
• Website usage data (pages visited, device/browser information, etc.)
• Form submission data entered by end users into forms created with Form Builder
• Workflow execution data processed through Yahmation Flow, including trigger payloads, node inputs/outputs, and integration data
• Google account information (email address) when you connect a Google account to Form Builder or Yahmation Flow
• eBay seller account information — including your eBay account identity and the listing, inventory, and order data in your account — when you connect an eBay account to Yahmation Flow or the Yahmation Client Portal
• Buyers' personal information contained in your eBay orders — including buyer names, shipping addresses, and contact details — obtained through eBay's order and fulfillment APIs and processed to manage, fulfill, and relist your listings on your behalf

2. How We Use Information

We use information to:

• Provide and improve services
• Communicate with clients and respond to inquiries
• Maintain security and prevent fraud
• Comply with legal obligations
• Export form submission data to Google Sheets on your behalf when you enable this integration
• Execute automated workflows on your behalf through Yahmation Flow, including reading and sending data to third-party services you configure
• Manage your eBay listings and orders on your behalf through Yahmation Flow and the Yahmation Client Portal — including automatically relisting or replenishing listings and responding to order events — using eBay's APIs and only as you authorize

3. Third-Party Services

We may share data with third-party providers to operate our business and deliver services, such as hosting providers, analytics services, automation platforms (e.g., workflow tools), marketplace and e-commerce platforms (e.g., eBay), AI service providers, CRM tools, and communication services. We share only what is necessary to provide the services, and we do not sell or rent your personal information.

4. Google API Services — User Data Policy

Our Form Builder and Yahmation Flow applications use Google API Services to provide integrations with Google Sheets, Google Drive, and Gmail. This section describes how we access, use, store, and share Google user data obtained through these integrations.

4.1 Data We Access

When you connect a Google account to Form Builder or Yahmation Flow, we may request access to the following scopes depending on which integrations you enable:

• Google Sheets (read/write): To read, write, and append data in spreadsheets you designate. Used by Form Builder to export form submissions and by Yahmation Flow to read and write spreadsheet data as part of automated workflows.
• Google Drive (app-created files): To upload, download, and list files that you create or open through our applications. We do not access files outside of those you explicitly interact with through our services.
• Gmail (send only): To send emails on your behalf as part of automated workflows you configure in Yahmation Flow. We do not read, modify, or delete your existing emails.
• User profile (email): To display which Google account is connected and to identify the correct account when multiple accounts are linked.

4.2 How We Use Google Data

Google user data is used exclusively to:

• Display a list of your spreadsheets so you can choose where to export form submissions or configure workflow automations
• Display the sheet/tab names within a selected spreadsheet
• Read data from and write data to your Google Sheets as part of form submissions or automated workflows
• Upload and download files to/from Google Drive as part of automated workflows you configure
• Send emails via Gmail on your behalf as part of automated workflows you configure
• Display your connected Google account email address in the application interface

We do not use Google user data for advertising, analytics, market research, or any purpose unrelated to providing the integration functionality described above.

4.3 Storage of Google Data

We store the following Google data on our servers:

• OAuth tokens (access token and refresh token): Stored encrypted at rest in our database, used to maintain your Google connection so you do not need to re-authenticate on every request.
• Google account email address: Stored to identify connected accounts.
• Token expiration timestamp: Used to automatically refresh expired tokens.

We do not store the contents of your Google Sheets, Drive files, or any other Google user data beyond what is listed above. Spreadsheet names and sheet lists are fetched in real time and are not persisted.

4.4 Sharing of Google Data

We do not share, sell, or transfer Google user data to any third party, except:

• As necessary to provide the integration (i.e., communicating with Google APIs on your behalf)
• As required by law, regulation, or legal process

4.5 Revoking Access

You can disconnect your Google account at any time from within the Form Builder or Yahmation Flow integration settings. When you disconnect:

• Your OAuth tokens are revoked with Google and deleted from our servers
• We will no longer have any access to your Google account
• Form submission export to Google Sheets will stop for any forms using that account
• Any Yahmation Flow workflows using that Google account will no longer be able to access Google services

You can also revoke access from your Google Account permissions page.

4.6 Google API Services User Data Policy Compliance

Our use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

4.7 Prohibited Uses of Google Data

We do not and will not use Google user data for any of the following purposes:

• Serving advertisements, including retargeting, personalized, or interest-based advertising
• Selling or transferring data to third parties, advertising platforms, data brokers, or information resellers
• Determining credit-worthiness or for lending purposes
• Surveillance or any purpose where data is displayed, sold, or distributed to a third party conducting surveillance

4.8 Human Access to Google Data

Yahmation employees, agents, and contractors will not read your Google user data unless:

• You have provided affirmative consent for us to access specific data (e.g., for troubleshooting a support request)
• It is necessary to investigate a security incident, abuse, or potential violation of our terms
• It is required by applicable law, regulation, or legal process
• The data has been aggregated and anonymized so that it can no longer be associated with an individual user, and is used solely for internal operations consistent with applicable privacy requirements

4.9 Limited Use

Our use of Google user data is limited exclusively to providing and improving user-facing features of our Form Builder and Yahmation Flow applications that are prominent in the application's user interface. We do not use Google user data for any purpose other than the integration functionality described in this section.

5. eBay API Services — Connected Account & Marketplace Data

Yahmation Flow and the Yahmation Client Portal integrate with eBay through eBay's APIs so we can manage listings and orders on behalf of sellers who connect their eBay account — for example, to automatically relist or replenish inventory when an item sells, or to pause and resume listings. This section describes how we access, use, store, share, and delete eBay data. Our handling of eBay data is consistent with the eBay User Privacy Notice and the eBay API License Agreement; we do not process eBay personal information in any manner that eBay itself could not.

5.1 Data We Access

When an eBay seller account is connected to Yahmation through eBay's secure OAuth authorization, we may access the following, depending on the features you enable:

• Seller account identity: your eBay user identifier and basic account information, used to identify the connected account and route data correctly.
• Inventory & listing data: your inventory items, offers, and listings, used to create, revise, relist, replenish, publish, or end listings as part of automated workflows you configure.
• Order & fulfillment data: your eBay orders and their details. This includes buyers' personal information — such as buyer names, shipping addresses, and contact information — which we process to fulfill, manage, and relist your listings on your behalf.

5.2 How We Use eBay Data

eBay data is used exclusively to operate the automation features you configure, including to:

• Read your listings, inventory, and orders to determine when and how to relist, replenish, or update items
• Create, revise, relist, publish, or withdraw listings on your behalf
• Process order events (for example, to trigger a relist when an item sells, or to pause and resume listings)
• Display your eBay account, listings, and relisting status within the Yahmation Flow and Yahmation Client Portal interfaces

We do not use eBay data for advertising, to build buyer marketing lists, for resale, or for any purpose unrelated to providing the integration functionality described above.

5.3 Storage of eBay Data

We store the following on our servers:

• OAuth tokens (access and refresh tokens): stored encrypted at rest, used to maintain your eBay connection so you do not need to re-authenticate on every request.
• Connected-account identifiers and configuration needed to route eBay notifications and run your workflows.
• Order and execution data processed by your workflows, retained only as long as needed to operate the service and limited to the minimum necessary.

Sensitive data, including OAuth tokens, is encrypted in transit and at rest using strong, industry-standard cryptography.

5.4 Sharing of eBay Data

We do not sell, rent, or trade eBay data. We share it only:

• With eBay, as necessary to operate the integration on your behalf (i.e., calling eBay's APIs)
• With the client or seller on whose behalf we act, and with service providers (sub-processors) who are contractually bound to data-protection obligations at least as protective as those in this policy and only to the extent strictly necessary
• As required by law, regulation, or legal process

5.5 Data Deletion & eBay Marketplace Account Deletion/Closure

We comply with eBay's Marketplace Account Deletion/Closure requirements. We operate a dedicated, signature-verified endpoint that receives eBay's account deletion/closure notifications, and upon receiving such a notification we permanently and irreversibly delete or purge that user's personal data from our systems — in a manner that cannot be reversed, even by our highest system privileges — across every account that connected it, within the timeframe eBay requires. The only data we may retain is the limited information we are required to keep to meet a specific, demonstrable legal obligation (for example, tax or fraud-prevention records); any such data remains protected and is not used for any other purpose. You may also request deletion of your data, or disconnect a connected eBay account, at any time (see Section 5.6).

5.6 Revoking Access

You can disconnect a connected eBay account at any time from the Yahmation Flow or Yahmation Client Portal integration settings. When you disconnect:

• Your eBay OAuth tokens are revoked and deleted from our servers
• We will no longer access that eBay account
• Any workflows using that account will stop running, including automated relisting

You can also revoke Yahmation's access from your eBay account's connected-applications and security settings.

6. Cookies & Tracking

We may use cookies and similar technologies for site functionality and analytics. You can manage cookies through your browser settings.

6.1 What Are Cookies?

Cookies are small text files stored on your device when you visit a website. They help websites remember information about your visit.

6.2 How We Use Cookies

We may use cookies to:

• Enable site functionality
• Analyze website traffic and usage patterns
• Improve site performance and user experience

6.3 Managing Cookies

You can disable or delete cookies through your browser settings. If you disable cookies, some features of the site may not function properly.

7. Data Retention

We retain personal data only as long as necessary for business, service delivery, and legal purposes. Google and eBay OAuth tokens are retained only while the corresponding account remains connected; when you disconnect, the tokens are deleted. Personal data obtained through a connected eBay account — including buyer order information — is deleted upon an eBay marketplace account deletion/closure notification, upon account disconnection, or upon your request, subject only to narrow legal-retention requirements.

8. Your Rights

You may request:

• Access to your data
• Correction of inaccurate data
• Deletion of personal data (subject to legal obligations)
• Disconnection of any connected third-party accounts (Google, eBay, etc.)

These rights apply to the personal information we hold, including data obtained through connected accounts such as Google and eBay. We do not sell or rent your personal information. To exercise any of these rights, contact us using the details in Section 16.

9. Security

We implement reasonable administrative, technical, and physical safeguards designed to protect information, including encryption of sensitive credentials at rest and in transit using strong, industry-standard cryptography. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security.

10. AI Use Disclosure

Yahmation uses artificial intelligence technologies to assist with automation, data processing, and workflow optimization.

• AI outputs may be probabilistic, incomplete, or incorrect.
• Human review is recommended before relying on AI-assisted outputs.
• AI does not replace professional judgment.
• The client remains responsible for final decisions and actions taken using deliverables or outputs.

11. Refund & Cancellation Policy (First-Month Risk-Free Guarantee)

Due to the nature of digital automation and AI services, Yahmation provides a first-month risk-free guarantee under the conditions outlined below.

11.1 Trial Period Eligibility

The first-month Trial Period only begins after:

• Payment for the agreed service term has been received
• All services have been fully implemented
• Systems are live, tested, and operating as intended
• The client has been shown how to use the services delivered

11.2 Refund Eligibility

Clients may request a refund within 30 calendar days from the Trial Period start date.

If approved:

• Only the first 30 days of service fees will be refunded
• Setup, onboarding, and custom work fees are non-refundable
• Third-party costs are non-refundable

11.3 Refund Exclusions

Refunds will not be issued for:

• Services rendered beyond the initial 30-day period
• Delays caused by the client (e.g., missing access, approvals, information)
• Failure to follow provided usage instructions
• Platform policy violations or unlawful use
• Abuse or misuse of automations or systems

11.4 Cancellations After Trial Period

After the first-month Trial Period, services may be canceled in accordance with the service agreement. No refunds will be issued for unused time or remaining service terms.

12. Acceptable Use Policy

This Acceptable Use Policy ("AUP") governs use of Yahmation's services. Clients may not use Yahmation services for:

• Illegal activity
• Spam or unsolicited messaging
• Abuse of third-party platforms
• Violations of platform terms, policies, or applicable laws

Violation may result in immediate service termination.

12.1 Trial Protection

Abuse of the first-month Trial Period, including excessive automation usage, intentional stress testing, or activity that violates third-party platform policies, will immediately void the risk-free guarantee.

13. Confidentiality & NDA Statement

Yahmation treats all client data, credentials, and business information as confidential. We will not share confidential information except as needed to perform services, with approved service providers under appropriate safeguards, or as required by law.

13.1 Formal NDAs

Formal Non-Disclosure Agreements (NDAs) may be executed upon request. If you require an NDA, contact us before sharing sensitive information.

14. SMS / Text Messaging

If you opt in to receive text messages from Yahmation — for example, by checking the SMS consent box on our contact or get-started forms — you agree to receive text messages related to your inquiry and the services you request, sent to the mobile number you provide. Message frequency varies. Message and data rates may apply. Reply STOP to opt out at any time, or HELP for help. Consent to receive text messages is not a condition of any purchase.

Mobile information and phone numbers collected for SMS/text-messaging purposes will not be shared with, sold, or rented to any third parties or affiliates for marketing or promotional purposes. No mobile opt-in information will be shared with third parties or affiliates for their own marketing. We share your mobile number only with the messaging provider that delivers texts on our behalf, solely to operate the program, and not for that provider's own marketing.

To stop receiving messages, reply STOP to any text. For help, reply HELP or email [email protected].

15. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated "Last Updated" date. Continued use of our services after changes constitutes acceptance of the revised policy.

16. Contact

Email: [email protected]