Services Privacy Policy

This Services Privacy Policy explains how Alpine Anchor, LLC (“Alpine Anchor”, “we”, “us”) collects, uses, shares, stores, and protects personal information when you use Horizon: the Horizon web application at app.horizonplatform.ai, the Horizon app for iPhone and iPad, Horizon AI agents, and related services (together, the “Services”). Our marketing websites, such as horizonplatform.ai, are covered by our Website Privacy Policy.

Horizon is a business platform. Most information in Horizon belongs to the organization that subscribes to it (your employer or the business that invited you). When we process that organization’s information, including information about its customers and contacts, we do so on the organization’s behalf as a service provider / processor, under our agreement with that organization and our Data Processing Addendum. This policy describes what we do with that information, but your organization’s own privacy notice governs how your organization uses it.

If you connect a Google account to Horizon, Section 1 explains exactly what Google data Horizon accesses and how it is used, shared, protected, kept, and deleted.

Please read this policy before using the Services, and contact us at [email protected] if you have any questions. This Services Privacy Policy forms part of our Master Services Agreement.

1. Google User Data

This section explains how Horizon, the app developed by Alpine Anchor, accesses, uses, stores, shares, protects, retains, and deletes data it receives from Google APIs (“Google user data”). It applies to everyone who connects a Google account to Horizon or signs in to Horizon with Google.

Limited Use disclosure. Horizon’s use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements. Horizon’s use of information received from Google Workspace APIs will also adhere to the Google Workspace API User Data and Developer Policy.

Horizon does not use data obtained through Google Workspace APIs to develop, improve, or train generalized or non-personalized artificial intelligence or machine learning models.

A. What Google user data Horizon accesses

Horizon asks Google only for the permissions needed for the features you turn on. It asks for additional permissions only when you, or an administrator in your organization, turn on a feature that needs them, and Google shows you each permission before you approve it.

Google service	Permission (OAuth scope)	What Horizon accesses	Why
Sign-in profile	openid, email, profile	Your name, email address, and profile picture	To identify you and the Google account you connected
Gmail	gmail.readonly	Your email messages, including their content and attachments	So that Horizon agents can find and read the email you ask about, for example to summarize a thread or answer a question about it
Gmail	gmail.compose	Drafts in your mailbox	So that agents can write email drafts for you to review
Gmail	gmail.send	Sending email from your account	Only if you turn on sending, so that agents can send email you ask them to send
Google Calendar	calendar.readonly	Your calendar events: titles, times, attendees, locations, descriptions, and conferencing details	To import your meetings into Horizon and so that agents can answer questions about your schedule
Google Calendar	calendar.events	Creating and updating events on your calendars	So that agents can schedule or change meetings when you ask
Google Meet	meetings.space.readonly	Conference records, transcripts, and participant names for your Google Meet meetings	Only if you turn on Meet transcript import, so that Horizon can import transcripts and generate meeting notes
Google Drive	drive.readonly	The files in your Drive and their contents	So that agents can search for and read the files you ask about
Google Drive	drive.file	Files that you open with Horizon or that Horizon creates	So that agents can work with files you choose and files they create for you
Google Docs, Sheets, and Slides	documents, spreadsheets, presentations	Creating and editing documents, spreadsheets, and presentations	So that agents can create or update documents you ask for

B. How Horizon uses Google user data

Horizon uses Google user data only to provide and improve user-facing features that you can see and control in Horizon, for example:

reading and summarizing the email, calendar events, and files you ask an agent about;
drafting, and if you turn it on sending, email on your behalf;
creating and updating calendar events and documents when you ask;
importing your meetings and transcripts and generating meeting notes, summaries, and action items.

Horizon acts on your Google account only when you, or an agent you set up, ask it to.

What we never do with Google user data. We do not:

use it to serve advertising, including targeted, personalized, retargeted, or interest-based advertising;
sell it, or transfer it to advertising platforms, data brokers, or information resellers;
use it to determine credit-worthiness or for lending purposes;
use it to develop, improve, or train generalized or non-personalized AI or machine learning models, or allow any AI provider we use to do so;
use it to build databases or profiles for any purpose other than providing Horizon’s features to you; or
use it, or Google APIs, to create, alter, or share sexually explicit or intimate imagery of any person, including AI-generated non-consensual intimate imagery (NCII). Horizon does not generate images.

We do not use Google user data, including Gmail, Calendar and Drive content, to train generalized AI or machine-learning models, and we do not permit our AI service providers to do so; requests containing such data are routed only to model endpoints that are contractually committed to not training on that data.

C. Who receives Google user data

We share or transfer Google user data only as needed to provide the features you request and only with your consent, for security purposes, to comply with applicable law, or as part of a merger, acquisition, or sale of assets after obtaining your explicit prior consent. The service providers that process Google user data for us are:

AI model providers, to produce the output you asked for (for example a summary, a draft, or meeting notes). Requests are sent through OpenRouter, Inc. to the provider of the model being used: OpenAI, Anthropic, or Google. We send only the portion of your data that the task needs. Before Horizon’s AI features process your data, you are asked to agree to this at your first sign-in (see Section 7).
Supabase, Inc. (database and file storage) and Hetzner Online GmbH (servers), which store and run Horizon.
Cloudflare, Inc., which carries network traffic to and from Horizon.
Apple Inc., if you use the Horizon iOS app with notifications turned on. A notification can include a preview of an agent’s reply, which may quote your Google data.

Each of these providers may use the data only to provide its service to us. The full list of our providers is on our Sub-Processors page. We do not transfer Google user data to any other third party.

People. Alpine Anchor employees and contractors do not read Google user data unless:

you give us explicit permission to view specific data, for example in a support request;
it is necessary for security purposes, such as investigating a bug or abuse;
it is necessary to comply with applicable law; or
the data has been aggregated and anonymized and is used for internal operations.

D. How Horizon protects Google user data

Google access and refresh tokens are encrypted with AES-256-GCM before they are stored, and are never shown to anyone.
All data is encrypted in transit with TLS.
Each organization’s data is kept separate in our database by row-level security, so only members of your organization can reach it.
Meeting data is kept in private storage, reachable only through short-lived signed links.
Changes to records are written to an append-only audit log.

See Section 13 for our other security measures.

E. How long Horizon keeps Google user data

Access tokens: until you disconnect the Google account or revoke Horizon’s access.
Email, calendar, and file content an agent reads: kept as part of that agent conversation so the agent can continue the task. Message text in agent conversations is removed about 90 days after the conversation ends; files attached to conversations and some working copies made while an agent completes a task are kept until you or your organization delete them or ask us to delete them (see Section 12).
Imported meetings and transcripts: kept as described in Section 6.D.
Documents, events, and email that agents create: these live in your Google account, and you control them there.

F. How to revoke access and delete Google user data

Disconnect in Horizon. Disconnecting a Google account in Horizon revokes Horizon’s access with Google and deletes the stored tokens, so Horizon can no longer access your Google data.
Revoke in Google. You can also remove Horizon’s access at any time from your Google Account’s third-party connections page. If you use a Google Workspace account, your administrator can also remove Horizon for your organization.
Delete data. Deleting your Horizon account deletes the Google user data that is yours alone (Section 11). To have other Google user data already stored in Horizon deleted, email [email protected] from the email address on your Horizon account. We will delete it within 30 days, except where we must keep it to comply with law.

We will notify you, and ask for your consent where required, before we use Google user data in any way this policy does not describe.

2. Definitions

A. Services means the Horizon platform, including the web application at app.horizonplatform.ai, the Horizon iPhone and iPad app, Horizon AI agents and their integrations with other services (for example Slack and Microsoft Teams), APIs, documentation, and related support.

B. Users means the people who sign in to or interact with the Services, including employees and contractors of our business customers.

C. Connected Account means an account with another service, such as Google, Microsoft, Slack, Salesforce, HubSpot, QuickBooks, Xero, Sage Intacct, Stripe, Virtuous, or GitHub, that you or your organization authorizes Horizon to access.

D. Customer Content means the information you and your organization put into the Services or ask the Services to retrieve, including messages to agents, uploaded files, meeting recordings and transcripts, and data retrieved from Connected Accounts.

3. Personal Information We Collect

A. Account Data

When your organization invites you and you create an account, we collect your name, email address, organization membership, and role. Sign-in is handled by our authentication provider, Clerk. If you sign in with Google, Clerk receives your name, email address, and profile picture from Google (see Section 1). If you sign in with a password, Clerk processes it; Alpine Anchor does not receive or store your password. If you turn on multi-factor authentication, Clerk processes the factor you choose, such as an authenticator app or a phone number for text-message codes.

B. Billing Information

For paying customers, we keep records of subscriptions, invoices, and payments. Card payments are processed by Stripe; we do not store full payment card numbers.

C. Connected Account Data

When you connect a Connected Account, we receive an access credential (an OAuth token or API key) and the data the Services need from that account to perform the features you turn on. Sections 1 and 5 describe Google and Microsoft data in detail. For other Connected Accounts, Horizon reads and, when you ask it to, writes records such as contacts, deals, invoices, payments, and accounts in that service.

D. Customer Content

We collect the content you provide or ask Horizon to work with, including:

Messages you send to Horizon agents and to other people in Horizon, including through the web app, the iOS app, Slack, Microsoft Teams, and other messaging channels your organization connects.
Files you upload (for example photos, PDFs, spreadsheets, and documents) and files agents create for you.
Agent instructions, and “memories” that agents save to remember facts for future tasks.
Meeting information (see Section 6).
Addresses you type into address fields, which are sent to Google Maps Platform for autocomplete and routing.

E. Meeting Recordings and Transcripts

See Section 6.

F. Mobile App Data

See Section 9.

G. Form, Email, and Support Data

We keep information you send us through forms, email, and support conversations.

H. Usage, Diagnostic, and Log Data

We compile statistics and other information about the performance, operation, and use of the Services, including data about identifiable Users’ use of features. To do this we use PostHog, a product-analytics service provided by PostHog, Inc. When you are signed in to the web application, we associate this data with your name, email address, role, and organization. We configure PostHog to mask on-page text and input values.

We also use PostHog session replay in the Horizon web application (app.horizonplatform.ai) to understand how people use the Services and to find and fix usability problems and errors. A recording shows the layout of the pages you visit and how you navigate, click, scroll, and move your mouse. Before anything leaves your browser, all text on the page and everything you type into a form field is masked (replaced with placeholder characters), so recordings do not show the text you read or what you type. Screens in the Horizon application that display health or patient records, accounting or general-ledger records, payroll records, or HR records are not recorded. We also use PostHog heatmaps and click analytics, which record where on a page people click and scroll, but not the text on the page. Recordings are kept for 30 days.

Our servers also record technical logs (for example request identifiers, timestamps, error messages, and IP addresses) to operate and secure the Services. Some error logs can contain short fragments of Customer Content. We keep these logs on our own infrastructure for 30 days. We also send application logs to PostHog, where they are kept according to the retention settings of our PostHog account.

The Horizon iOS app does not include third-party analytics, advertising, or crash-reporting software.

4. How We Use Personal Information

We use personal information to:

Provide the Services, including running the AI agents and features you and your organization direct
Transcribe recordings and generate meeting notes, summaries, and action items when you ask
Send notifications, including push notifications and transactional emails
Provide support and maintenance, and troubleshoot problems
Process billing and payments
Analyze usage of the Services to maintain and improve them, as described in Section 3.H
Secure the Services and prevent fraud, abuse, and illegal activity
Comply with law and legal process, and enforce our agreements

We do not sell personal information. We do not use Customer Content or data from Connected Accounts for advertising. We do not use Google user data, including Gmail, Calendar and Drive content, to train generalized AI or machine-learning models, and we do not permit our AI service providers to do so; requests containing such data are routed only to model endpoints that are contractually committed to not training on that data. See Sections 1 and 7.

5. Microsoft Data

When your organization connects Microsoft Teams, an administrator signs in with Microsoft using the openid and profile permissions only. We receive and store the Microsoft tenant ID, the administrator’s Microsoft user ID, and their name, to link your organization’s Teams tenant to Horizon. We do not store the Microsoft access token from that sign-in.

When a Horizon agent is added to Teams, messages sent to the agent are delivered to Horizon through Microsoft’s Bot Framework. In channels where the agent is installed, Horizon reads the messages in the thread it is replying to (using Microsoft Graph resource-specific consent), so the agent has context. If you accept a file the agent offers, the file is uploaded to your OneDrive. This data is used only to respond to you and is handled like other Customer Content.

Horizon does not currently access Outlook mail, Outlook or Microsoft 365 calendars, or Teams meeting recordings or transcripts. We will update this policy before we add any of these.

6. Meeting Recordings, Transcripts, and Notice to Participants

A. Sources

Horizon works with meeting information from:

Google Meet transcripts and Google Calendar events you choose to import (Section 1);
in-person recordings you make with the Horizon iOS app; and
audio files you upload in the web application.

B. Your responsibility to notify participants

Recording and transcription laws vary. Some jurisdictions require the consent of everyone being recorded. The customer, or the user who records or uploads a meeting, is responsible for telling participants that the meeting is being recorded and transcribed, and for obtaining any consent the law requires. Horizon requires you to confirm that participants have been told before a recording starts in the iOS app or before an audio file is uploaded in the web application. We store that confirmation, the time you gave it, and your user ID with the recording.

C. How recordings are processed

Audio is stored in private storage that only your organization can access. To transcribe it, we give our transcription provider, AssemblyAI, Inc., a link to the audio that expires after one hour. AssemblyAI converts the speech to text. To label who spoke when, its model tells apart the voices within that one recording and assigns generic labels such as “Speaker A”. Horizon does not create voiceprints or other biometric identifiers, does not match voices across recordings, and does not use speaker labels to identify individuals. When you ask, the transcript is sent to the AI providers in Section 7 to generate notes, summaries, decisions, and action items.

D. Retention and deletion

Audio: deleted from our storage 7 days after the transcript is completed (or after we determine the audio cannot be transcribed), or 30 days after a transcription failure so that it can be retried.
AssemblyAI: audio is sent to AssemblyAI only for transcription, through a short-lived link; we never upload audio files to AssemblyAI. AssemblyAI does not use it to train models: we have opted out of its model-improvement program. Horizon deletes AssemblyAI’s copy of the transcript as soon as Horizon receives it, and AssemblyAI’s retention is limited to one day as a safeguard.
Transcripts, notes, and meeting details: kept until you or your organization delete them or ask us to delete them (Section 11).
Recordings on your iPhone or iPad: stay on the device until they are uploaded to Horizon or you discard them.

7. AI Processing

Horizon is an AI-driven service: its agents, Operator chat, meeting notes, and document extraction all use artificial intelligence models. To provide these features we send the information needed for the task to AI model providers. This can include your messages, agent instructions and saved memories, file contents and images, meeting transcripts, and data retrieved from Connected Accounts (for example an email, a calendar event, a document, or a CRM record).

Your consent. Before Horizon’s AI features process your data, each user is asked to agree at first sign-in, on the web and in the iOS app. That consent covers sharing your data with the AI providers described in this section and listed on our Sub-Processors page.

Providers. Most AI requests are sent through OpenRouter, Inc., which routes each request to the provider of the selected model. The models we use today come from OpenAI, Anthropic, and Google. Some features send requests directly to Anthropic, PBC. We have signed data processing agreements with OpenAI, OpenRouter, and Anthropic.

Training. We do not use Google user data, including Gmail, Calendar and Drive content, to train generalized AI or machine-learning models, and we do not permit our AI service providers to do so; requests containing such data are routed only to model endpoints that are contractually committed to not training on that data. We have also opted out of our transcription provider AssemblyAI’s model-improvement program.

Accuracy. AI output can be incomplete or wrong. Review it before relying on it, especially before an agent sends a message or changes a record on your behalf.

A. Service providers (sub-processors)

We share personal information with service providers that host, secure, and operate the Services for us, including providers of authentication, database and file storage, hosting and networking, AI models, transcription, email delivery, push notifications, maps, analytics, and payments. We share personal information with these providers only so that they can provide their services to us, and we expect them to protect it with safeguards consistent with this policy. The current list, with each provider’s purpose and location, is on our Sub-Processors page.

B. Services you connect or direct us to use

When you or your organization connect a Connected Account, deploy an agent to a messaging channel, or configure a connector, Horizon sends data to that service as you direct (for example, updating a record in your CRM, posting a reply in Slack, or calling a web address your organization configures). That service’s own terms and privacy policy govern the data it receives.

C. Within your organization

Information you put into Horizon is visible to other Users in your organization according to the permissions your organization sets.

D. Legal and safety

We may share personal information to respond to subpoenas, court orders, or other legal process; to establish or exercise our legal rights or defend against legal claims; or if we believe it is necessary to investigate, prevent, or act on illegal activity, suspected fraud, threats to anyone’s safety, or violations of our agreements.

E. Business transfers

If Alpine Anchor is involved in a merger, acquisition, or sale of assets, personal information may be transferred as part of that transaction, subject to this policy. Google user data is transferred only after obtaining your explicit prior consent (Section 1.C).

9. Mobile App and Push Notifications

The Horizon app for iPhone and iPad collects:

Account and sign-in data, through Clerk. Clerk also receives a device identifier assigned by Apple to our apps on your device (the identifier for vendor) and your device model, operating system version, and app version, to secure sign-in.
Push notification data. If you allow notifications, we store your device’s Apple Push Notification service token, device model, operating system and app version, and the organization you are signed in to, so that we can send you notifications. Notification content, such as the sender’s name, a message preview, or an approval summary, is delivered through Apple’s push notification service. We remove the token when you sign out or switch organizations. You can turn notifications off at any time in iOS Settings.
Microphone, only when you start an in-person recording (Section 6).
Camera and photos, only when you choose to add a photo to a conversation. Photos chosen from your library may include embedded location information (EXIF data) unless you turn off location in the photo picker’s options.
Files you choose to attach.

The app keeps a cache of recent conversations on your device to load quickly; it is cleared when you sign out or switch organizations. The app does not track you across other companies’ apps or websites, does not use the advertising identifier, and does not include third-party analytics or advertising software.

10. Links to Other Websites and Services

The Services contain links to, and integrations with, websites and services operated by third parties. We are not responsible for their privacy practices.

11. Your Choices: Access, Correction, and Deletion

You can update your name and other profile details in your account settings.
You can disconnect a Connected Account at any time. For accounts connected through OAuth sign-in, such as Google, disconnecting revokes Horizon’s access with the provider. You can also revoke Google access from your Google Account (Section 1.F).
You can turn off push notifications in iOS Settings.
Delete your account. In the web app, open your account menu and choose Manage account, then Security, then Delete account. Your access to every organization ends at once, and your personal Connected Accounts are disconnected and Horizon’s access with each provider is revoked. Content that is yours alone, such as agent conversations no one else is part of, your scheduled agent tasks, and your agent memories, is permanently deleted 30 days later. At the same time we ask PostHog to delete the usage analytics and session recordings associated with your account (Section 3.H). Information that belongs to your organization’s workspace stays with the organization, and your name on it is replaced with “Deleted user”.
Delete an organization. An owner or administrator can delete the organization’s workspace from Settings, then Danger, then Delete organization. Every member loses access at once, the organization’s Connected Accounts and bank connections are disconnected and revoked, its agents and scheduled work stop, its published websites go offline, and its subscription is cancelled. 30 days later we permanently delete the workspace’s content, including its CRM records (such as contacts, companies, deals, activities, and quotes), marketing content, support tickets, forms and their submissions, projects, goals, and planning, HR records, agents and their conversations, memories, and run history, meetings and their recordings, transcripts, and notes, boards, notifications, reports, dashboards, and settings, uploaded files, construction field records and photos, published websites, and member profiles, invitations, and API keys. We keep billing and usage records, the organization’s finance and accounting records (including payroll, compensation, and leave records, tax records, invoices, payments, bank records, and the documents behind them), signed agreements, and our audit log, as Section 12 describes. Where a kept record refers to something otherwise deleted, such as the customer on an invoice or the employee on a pay run, we keep only that item and remove the personal contact details it no longer needs. Content the organization shared with other organizations, such as community and marketplace listings and its partner directory profile, is removed from public view at once and permanently deleted after 30 days. Agents that other organizations have already installed are their own copies and keep working, and the deleted organization’s people are no longer named on them. An administrator can email [email protected] to have any other information left in the workspace deleted.
To request a copy of your personal information, or its correction or deletion, you can also email [email protected] from the email address on your Horizon account. We complete deletion requests within 30 days, except where we must keep information to comply with law. If the information belongs to your organization’s workspace, we may refer your request to your organization or act on its instructions, as our agreement with it requires.

12. Data Retention

How long we keep data depends on the type of data. Meeting audio is deleted 7 days after it is transcribed, or 30 days after a failed transcription. Message text in agent conversations is removed about 90 days after the conversation ends, although files attached to conversations, some working copies made while an agent completes a task, meeting transcripts and notes, and agent memories are kept until you or your organization delete them or ask us to delete them. Connected Account tokens are kept until the account is disconnected. Server logs are kept for 30 days and database backups for 7 days. Billing records, the finance, accounting, payroll, and agreement records an organization keeps in Horizon, and our audit log, which can include copies of deleted records, are kept as long as needed for legal, tax, and accounting purposes, including after the organization is deleted (Section 11).

We are building retention settings that will let your organization choose how long Horizon keeps each kind of data. We will update this policy when they are available. Until then, you can ask us to delete data at any time (Section 11).

13. Security Measures

We protect personal information with technical and organizational measures appropriate to its sensitivity, including:

encryption of data in transit with TLS;
encryption of Connected Account tokens and other credentials with AES-256-GCM before storage;
isolation of each organization’s data in our database using row-level security;
an append-only audit log of changes to records;
multi-factor authentication for Users, through Clerk;
private file storage that is reached only through short-lived signed links; and
network ingress through Cloudflare, so our production servers are not reached directly from the public internet.

No Internet transmission or storage system is completely secure. If we learn of a security breach affecting your personal information, we will notify you and the authorities as the law requires, and notify our business customers as our agreements with them require.

14. Hosting and International Transfers

Alpine Anchor is based in the United States. Production customer data is stored and processed on our production hosts: servers operated by Hetzner Online GmbH, and database and file storage provided by Supabase, Inc., with Cloudflare, Inc. providing DNS and network ingress. Production customer data is hosted in the United States: our Hetzner servers are in Ashburn, Virginia, and our Supabase database and storage are in the US East region. Our AI providers, our transcription provider (AssemblyAI), and our analytics provider (PostHog) process data in the United States; some of our other service providers also process data in other locations, as shown on our Sub-Processors page.

Where we transfer personal data from the European Economic Area, the United Kingdom, or Switzerland to a country that has not been recognized as providing adequate protection, we rely on appropriate safeguards, such as the EU Standard Contractual Clauses.

15. Children’s Personal Information

The Services are intended for business use by adults. We do not knowingly collect personal information from children under 16. If you believe a child has given us personal information, contact [email protected] and we will delete it.

16. Notice to European Users

If you are in the EEA, the United Kingdom, or Switzerland, the following applies in addition to the rest of this policy. Alpine Anchor, LLC acts as a controller for account data (account administration, billing, security, and the usage data described in Section 3.H) and as a processor for Customer Content, including data from Connected Accounts and meeting recordings, which we process on behalf of your organization under our Data Processing Addendum.

Legal bases. We process personal data to perform our contract with you or your organization (providing and supporting the Services and processing billing), where it furthers our legitimate interests in operating, securing, and improving the Services (balanced against your rights), with your consent where we ask for it (for example, when you connect an account or allow notifications), and to comply with legal obligations.

Your rights. Subject to the conditions and exceptions in applicable law, you have the right to request access to, rectification of, or erasure of your personal data; to withdraw consent where we rely on it; to receive a portable copy of the personal data you provided; and to object to or request restriction of certain processing. To exercise these rights, contact [email protected]. You also have the right to lodge a complaint with your local data protection supervisory authority.

17. Notice to California and Other U.S. State Residents

Depending on where you live, you may have the right to know what personal information we collect about you and how we use and disclose it; to access, correct, or delete it; to obtain a portable copy; and to opt out of the sale or sharing of your personal information for targeted advertising and of certain profiling. We will not discriminate against you for exercising these rights.

We do not sell personal information collected through the Services, and we do not share it for cross-context behavioral advertising. To make a request, email [email protected]. You may use an authorized agent; we may need to verify your identity, and your agent’s authority, before we respond. If we decline your request, you can appeal by replying to our decision.

18. Changes to This Policy

We may update this policy from time to time. We will post the updated policy here and update the “Last updated” date. If we make a material change, we will notify account administrators by email or in the Services before it takes effect. We will not use Google user data in a new way that this policy does not describe without first asking for your consent.

19. Contact Us

If you have questions about this policy or our privacy practices, or want to exercise your rights, contact us at:

Alpine Anchor, LLC Attention: Privacy PO Box 535562 Grand Prairie, TX 75053 Email: [email protected]