Privacy Policy

Nexture AI LLC

Effective Date: September 25, 2026

This document was last reviewed and updated on the effective date above.

Brand notice. This service is offered publicly under the name MiaSure. "MiaSure" is a trade name of Nexture AI LLC, the Wyoming limited liability company that operates the Service and is your contracting party under this document. Any reference herein to "Nexture AI," "Nexture AI LLC," "the Company," "we," "us," or "our" means Nexture AI LLC operating as MiaSure.

This Privacy Policy describes how Nexture AI LLC ("Nexture AI," "we," "us," or "our") collects, uses, processes, stores, and discloses your personal information when you use our platform and related services (the "Service"). Your privacy is important to us, and we are committed to protecting your personal information.

By accessing or using the Service, you agree to the collection, use, and disclosure of your information in accordance with this Privacy Policy. If you do not agree with the terms of this Privacy Policy, please do not access or use the Service.

1. Introduction & Your Commitment to Privacy

Nexture AI is dedicated to providing an innovative platform for insurance brokers and buyers while maintaining high standards for privacy and data security. This Privacy Policy explains our practices concerning the information we collect and process, particularly Nonpublic Personal Information (NPI) as defined by the Gramm-Leach-Bliley Act (GLBA) and personal information under various U.S. state privacy laws.

Important Note

Nexture AI's Service is designed exclusively for Property & Casualty (P&C) insurance documents. We do not collect, process, or store Protected Health Information (PHI) subject to the Health Insurance Portability and Accountability Act (HIPAA).

GLBA Compliance: As a service provider to financial institutions (insurance brokers), Nexture AI maintains an information security program and privacy practices consistent with GLBA requirements, including:

• Limiting the collection and use of NPI to what is necessary to provide and improve the Service.
• Not disclosing NPI to nonaffiliated third parties except as permitted under GLBA (e.g., to service providers under contract, as required by law, or with your consent).
• Maintaining administrative, technical, and physical safeguards to protect NPI as described in our Security Statement.
• Providing this privacy notice at account opening and annually thereafter for the duration of the customer relationship, as required by Regulation P.

2. Your Role as Data Controller/Processor

2.1. For Insureds: When you, as an individual insured, upload your own documents and use the Service for your personal insurance management, Nexture AI acts as the "Controller" of your personal information, determining the purposes and means of processing your data.

2.2. For Brokers: When you, as an insurance broker or firm ("Broker User"), upload documents containing your clients' information, Nexture AI acts as a "Service Provider" or "Processor" for your clients' Nonpublic Personal Information (NPI). In this context, the Broker User is the "Financial Institution" or "Controller," and you retain primary responsibility for your clients' NPI. Our processing of such NPI is governed by our Terms of Service and, where one has been executed between you and Nexture AI, a Data Processing Addendum or GLBA Addendum.

3. Information We Collect

We collect various types of information, including personal information, to provide and improve our Service.

3.1. Information You Provide Directly:

• User Profile Data: When you register for an account, we collect your name, email address, physical address, phone number, company name (for Broker Users), job title (for Broker Users), and login credentials.
• Communications: Records of your correspondence with us, such as customer support inquiries or feedback.

3.2. Information from User-Uploaded Documents: When you upload insurance documents (e.g., policies, binders, endorsements, quotes) to the Platform, our Service processes the content of these documents. This includes, but is not limited to, extracting and storing:

• Insurance Policy Data (P&C Only): Policy numbers, coverage limits, deductibles, premiums, effective dates, types of coverage, insured property addresses, vehicle identification numbers (VINs), driver information (including names, dates of birth, driver's license numbers), loss history, and other details contained within P&C insurance documents.
• No SSNs: As stated in our Terms of Service, we expressly prohibit the upload of Social Security Numbers (SSNs) and do not intentionally collect or store them. Nexture AI disclaims all liability for SSNs uploaded in violation of our Terms.

Prohibited Data: Users must not upload documents containing Social Security Numbers. See our Terms of Service for full details on prohibited content.

3.3. Information Collected Automatically: When you access or use the Service, we may automatically collect certain information about your device, browsing actions, and patterns, including:

• Usage Data: Details of your access to and use of the Service, including traffic data, location data, logs, and other communication data and the resources that you access and use on the Service. This includes interactions with AI tools (e.g., chatbot queries, summaries generated).
• First-Party Usage Analytics: We operate a first-party analytics tracker that records how you use the Service — the pages you view, the features you use, the search query terms you enter within the platform, and the exports you generate — together with device and browser characteristics (a "fingerprint" consisting of your user-agent string, browser language, screen and viewport dimensions, and timezone) and a per-session identifier stored in your browser's session storage. This information is tied to your account and stored in our own systems. We use it solely on a first-party basis to understand product usage, diagnose issues, and improve the Service. It is not sold and is not used for cross-site or cross-context behavioral tracking or advertising.
• Device Information: Information about your computer and internet connection, including your IP address, operating system, browser type, and unique device identifiers.

3.3a. Document Access Records: When a policy, a deliverable, or a document we produced is opened, we record that it was opened: which document, which screen, which page, the time, and who opened it. For someone signed in to an account we record their account identifier and not their network address. For a recipient opening a link or a client portal, where there is no account, we record the network their request came from (for example 203.0.113.0/24) rather than their individual address, and we do not record a more precise location. Where a file is delivered we also record a cryptographic fingerprint of the exact bytes sent, so it can later be shown which version was received. This record exists because it is the broker’s professional-liability evidence of who was shown what, and it is kept on the schedule in Section 9.

3.3b. Meetings, Recording, and Transcription: Where a user connects a calendar account and enables our meeting assistant for a meeting, the assistant joins that meeting and a transcript is produced from the audio by a third-party speech-to-text provider. We store the transcript, a summary, and the identities of the people in the meeting (names and email addresses from the calendar invitation) so the meeting can be linked to the correct account and the right people can see it. We do not store the meeting audio or video. The assistant is not enabled unless the user turns it on for that meeting. Notice and consent are the responsibility of the account holder who enables it: several U.S. states require the consent of every participant before a conversation is recorded or transcribed, and the account holder must obtain it. We provide the assistant; we do not obtain consent on anyone’s behalf. Transcripts and meeting records are deleted when the associated policy or account is deleted, on the schedule in Section 9.

3.4. Cookies and Tracking Technologies: We use cookies and similar tracking technologies to enhance your user experience, analyze trends, administer the website, and gather demographic information about our user base. Specifically:

Essential authentication and session cookies are the only cookies the Service sets, and they are strictly necessary for the platform to function. We do not set analytics or advertising cookies. Our usage analytics are gathered through a first-party tracker (described in Section 3.3) and through Plausible, a cookieless, aggregate page-analytics service. Your interface preferences (e.g., layout and theme) are saved in your browser's local storage on your own device — not in cookies. We do not use cookies for third-party advertising or cross-site behavioral tracking. You can control or clear browser storage at the individual browser level. Disabling essential cookies may prevent you from using the Service.

Do Not Track (DNT) Signals: Some browsers transmit "Do Not Track" signals to websites. Because there is no common industry standard for interpreting DNT signals, we do not currently alter our data collection and use practices based on DNT signals. We will update this policy if a uniform standard is established.

4. How We Use Your Information

We use the information we collect for various purposes, primarily to provide, maintain, and improve our Service, and for legitimate business operations.

4.1. To Provide the Service:

• To operate and maintain the Platform, including storing your documents and account information.
• To enable AI functionality such as smart sorting, document summarization, policy comparison, and chatbot responses.
• Mia’s memory: Mia, our AI assistant, keeps a lasting record of what it learns from your activity on the Service — including your conversations with it, your preferences, your role and focus areas, and the documents and actions you take — and uses that record to personalize its answers in later conversations. Mia learns these items automatically as you use the Service; it does not ask each time. You can see and delete remembered items at any time under Settings › Memory.
• To process payments you make for the Service (via our third-party payment processor).
• To communicate with you about your account and provide customer support.
• Support access (off by default, with your consent): Only where you have explicitly enabled it in your account settings, authorized Nexture personnel may access your account — including by securely accessing the Service as your account in a read-only support session — solely to operate, troubleshoot, and support the Service. This access is disabled by default, restricted to authorized personnel, time-limited, and recorded in an audit log, and you can enable or disable it at any time in your account settings.

4.2. To Improve the Platform & AI Models:

• AI Fine-Tuning: To enhance the capabilities and accuracy of our platform's AI tools (such as document summarization, comparison, and chatbot responses), we may use the content of user-uploaded documents and interactions within the platform. Where we do so, the data is rigorously anonymized or pseudonymized before being used for internal model fine-tuning and improvement. This process helps us deliver more precise and relevant services and improve the overall functionality of our AI without identifying specific individuals or entities.
• Analytics: To analyze usage patterns and improve the user experience, functionality, and performance of the Service. This is done on a first-party basis using our own usage-analytics tracker (described in Section 3.3), the cookieless, aggregate Plausible service, and Sentry for error and performance diagnostics (with personal information scrubbed before transmission and no session recording or replay). We use this information only to operate and improve the Service — never to sell your data or to track you across other sites.

4.3. For Security & Compliance:

• To monitor, detect, and prevent security incidents, fraud, and other malicious or illegal activities.
• To comply with our legal obligations, including under the Gramm-Leach-Bliley Act (GLBA) and various U.S. state data privacy and breach notification laws.
• To enforce our Terms of Service.

5. How We Share Your Information

Nexture AI does not sell your personal information or share it with third parties for their independent marketing or cross-context behavioral advertising purposes. We only share your information in the following limited circumstances:

5.1. With Service Providers (Our Sub-processors): We engage trusted third-party service providers to perform functions on our behalf and help us operate and improve the Service. These providers are contractually obligated to protect your information and use it only for the purposes for which it was disclosed. They include categories such as:

• Infrastructure & Hosting: Render (PaaS hosting), Amazon Web Services (S3, KMS, SES, Cognito, Secrets Manager — primary region us-east-1), MongoDB Atlas (primary database), and Redis Cloud (queue + cache).
• Large Language Model (LLM) Providers: OpenAI, Anthropic, Google AI (Gemini + Geocoding), and Mistral AI. All operate under enterprise/API agreements that prohibit them from using your input data to train or improve their general models. These providers may temporarily retain inputs and outputs for a limited period (typically up to 30 days) for abuse monitoring and trust-and-safety purposes, after which the data is deleted, except where a zero-data-retention arrangement is in place.
• Document Processing: LLMWhisperer (OCR / PDF-to-text).
• Billing: Stripe — receives only billing details; no policy or insured data.
• Operational Telemetry: Sentry — error and performance monitoring with PII scrubbed before transmission.
• Conditional / Opt-In: Microsoft Graph (Outlook/OneDrive/SharePoint), Box, and web-research providers (Tavily, Jina Reader, Firecrawl) are only invoked when the corresponding feature is explicitly enabled by your broker.

A complete, current list of sub-processors — including each provider's role, data class, region, and contractual basis — is maintained at miasure.com/legal/sub-processors. We provide 30 days' advance notice via email and an in-app banner before adding any new sub-processor that handles tenant data.

5.2. As Required by Law: We may disclose your information if required to do so by law or in response to valid requests by public authorities (e.g., a court order, subpoena, or government agency request).

5.3. To Protect Our Rights: We may disclose your information when we believe it is necessary to protect the rights, property, or safety of Nexture AI, our users, or others.

5.4. Business Transfers: In the event of a merger, acquisition, sale of assets, or other corporate change, your personal information may be transferred to the acquiring entity, subject to their commitment to similar privacy protections. We will notify you via email and/or a prominent notice on the Service of any such change in ownership or control of your personal information.

6. AI & Your Data (Transparency & Your Control)

AI-Generated Outputs: The Service uses artificial intelligence to generate document summaries, policy comparisons, data extractions, and chatbot responses. All AI-generated outputs are presented as aids and should be reviewed by qualified professionals before reliance. We clearly identify AI-generated content within the platform where applicable.

No Automated Decision-Making: Nexture AI does not use automated decision-making or profiling that produces legal or similarly significant effects on you. All AI outputs are informational tools intended to assist human decision-making, not replace it.

AI Fine-Tuning: As explained in Section 4.2, we may use anonymized or pseudonymized User Content and interactions to improve and fine-tune our internal AI models.

Opt-Out Right for AI Fine-Tuning: You have the right to opt out of the use of your anonymized or pseudonymized data for our internal AI model fine-tuning.

• How to Opt-Out: To exercise this right, please contact us at privacy@miasure.com.
• In-Product Controls: You do not have to write to us. The same controls are available in your account at any time under Settings → Extraction Preferences, where two switches — each on by default, and each governing only the anonymized or pseudonymized material described in Section 4.2 — control the specific contributions your account makes to platform improvement:
• "Contribute to the shared forms library" — We build generic knowledge about standard insurance forms (what a form does and what it changes) and share it across accounts so that every policy is read more accurately. Nothing about your policies enters that library: no named insured, no policy number, no premium, no policy period, and no location. Every entry must pass a genericity check enforced in our code before it is written, and an entry we cannot describe generically is refused rather than shared. Turning this off keeps your documents out of it entirely; you continue to benefit from what other customers have contributed.
• "Help us fix the platform's own mistakes" — When we check a finished summary or comparison and find a flaw in how we produced it, we keep a description of the flaw itself — which rule broke, and where in our software — so that we can correct it for every customer. Only that generic, account-free description of the defect ever leaves your account, and it must pass the same kind of fail-closed check described above before it does: a description we cannot generalize is discarded, not shared. Checking your own deliverables for your own benefit is part of delivering the Service to you and is not affected by this switch.
• Effect of Opt-Out: Upon opting out, your new data and interactions will not be used for future fine-tuning. However, due to the technical complexities of AI model training, we cannot guarantee the complete removal of your previously contributed anonymized/pseudonymized data from historical, already-trained models.

7. Data Retention & Deletion

We retain your personal information for as long as necessary to fulfill the purposes for which it was collected, to provide the Service, to comply with our legal obligations (including GLBA and state record-keeping requirements), resolve disputes, and enforce our agreements. Specific retention periods are as follows:

• Trash (soft delete): Moving a document to Trash hides it from your active library and from every list, search, deliverable, calendar event, and notification that references it. Trashed items do not auto-expire — they remain available for restore until you choose to permanently delete them.
• Permanent Deletion (Delete Forever): When you choose Delete Forever, our cascade-deletion routine removes the Document and the records made from it from our active systems within minutes. This covers the Document record, its draft deliverables, all extraction tables, the canonical policy snapshot, the encrypted PDF and OCR transcript in S3, page-image artifacts, indexed vector-store chunks, shares + share-conversation history, review-session snapshots, workspace and view memberships, calendar events, notifications, and deliverable edit-request audit trails. Published or sent documents are kept as business records. A deliverable you published or sent (for example, a Summary of Insurance shared with a client) is not removed when the document it was made from is permanently deleted; it stays in your Deliverables, marked as made from a deleted document, and is removed when you permanently delete it individually or close your account. See our Security Statement § 4.5 for the full cascade detail.
• Backups: MongoDB Atlas point-in-time backups and S3 versioned object copies are governed by their respective retention policies (maximum 90 days). Permanently-deleted data ages out of these backups on the next rotation cycle. The customer-controlled key revocation feature described in Security Statement § 3.1.1 will, once shipped, enable cryptographic destruction of data including backups.
• Deleting Your Account Yourself: You can close your account from inside the Service, under Settings › Security › Your data › Delete my account (on an insured account, also on the Your data page). Before anything is deleted, we first check that your account can be closed this way, then ask you to confirm it is you by entering your current password — and, if you use an authenticator app, its current code — and to type “delete my account”. An account cannot be closed from a support session. When you confirm, our account-erasure routine deletes your account profile, the documents in your account and the policy data extracted from them, your deliverables (published or sent ones included), your Mia chat history and Mia’s memory, and the other records tied to your account, and removes the stored files from our active systems. Copies you shared that a recipient has already accepted are in the recipient’s own account and are not deleted. Payment and billing records are kept for the period stated in the table above. Closing your account cannot be undone, so you may wish to download a copy of your data first (see Section 8). If the deletion cannot be completed, the Service tells you so rather than reporting success; you can then contact us at privacy@miasure.com.
• Accounts That Must Be Closed by Email: Some accounts cannot be closed from inside the Service, because closing them would remove records that other people rely on or would leave a charge unsettled: accounts that belong to a firm or an organization on the Service (including a firm’s owner and administrators), MiaSure administrator accounts, and accounts with a recurring billing plan or a paid balance. An account also cannot be closed while a copy of its data is still being prepared. In each case the Service tells you why. To close such an account — or if you prefer not to use the in-app option — email privacy@miasure.com from the address you sign in with, and we will verify your identity before acting on the request.
• Account Deletion: If you close your account entirely, we will retain limited account metadata (email, account creation/closure timestamps) for up to three (3) years to comply with legal obligations, prevent fraud, and resolve disputes, after which it will be securely deleted or anonymized. When you close your account yourself, the email address in this record is stored encrypted.
• Legal Compliance: We may retain specific records for longer periods if required by law (e.g., GLBA, state insurance regulations) or for legitimate business interests such as auditing or maintaining business records (e.g., payment records held for 7 years).
• AI Fine-Tuning Data: Anonymized/pseudonymized data already incorporated into our AI fine-tuning datasets at the time of your deletion request may persist there subject to your opt-out rights under Section 6.

8. Your Privacy Rights (U.S. State-Specific)

Depending on your state of residency, you may have specific rights regarding your personal information under laws such as the California Consumer Privacy Act (CCPA) / California Privacy Rights Act (CPRA), Virginia Consumer Data Protection Act (VCDPA), Colorado Privacy Act (CPA), Utah Consumer Privacy Act (UCPA), Connecticut Data Privacy Act (CTDPA), and other applicable state laws.

These rights may include:

• The Right to Know: To request information about the categories and specific pieces of personal information we have collected about you, the sources from which it is collected, the purposes for collecting/selling/sharing it, and the categories of third parties to whom we disclose it.
• The Right to Delete: To request the deletion of your personal information, subject to certain exceptions (e.g., to complete transactions, for security purposes, to comply with legal obligations).
• The Right to Correct/Rectify: To request the correction of inaccurate personal information.
• The Right to Data Portability: To receive a copy of your personal information in a structured, commonly used, machine-readable format.
• The Right to Opt-Out of Sale/Sharing: Nexture AI does not sell or share your personal information with third parties for their independent marketing or cross-context behavioral advertising purposes. Therefore, an opt-out mechanism for "sale/sharing" is not generally required as we do not engage in these activities.
• The Right to Limit Use and Disclosure of Sensitive Personal Information: While P&C insurance data is sensitive, its processing for the provision of our core service is generally exempt from the "right to limit" under CCPA/CPRA, as it is necessary for the transaction.
• The Right to Non-Discrimination: We will not discriminate against you for exercising your privacy rights.

How to Exercise Your Rights: To exercise any of these rights, please contact us at privacy@miasure.com. We may need to verify your identity before processing your request.

In-App Self-Service: You can also exercise two of these rights yourself, from inside the Service, under Settings › Security › Your data (on an insured account, also on the Your data page). Neither option can be used from a read-only support session.

• Download a copy of your data (Right to Know and Right to Data Portability): We prepare one .zip file containing your account details, every document in your account in the form it was uploaded, the deliverables you saved (as they were saved), and the policy data we extracted from each document in a structured, machine-readable format (JSON), together with a manifest listing everything in the file. If an item does not fit within the file’s size or time limit, or cannot be read, the manifest names it and says why. The file is stored encrypted and can be downloaded for 24 hours, only while you are signed in to your account, through a short-lived download link. After 24 hours it can no longer be downloaded, and the stored file is deleted the next time you return to that page or request a new copy, and in any case when you close your account. We never email the file or a link to it. When a copy is requested, we email a notice to the address you sign in with, so that you would know if someone else requested it; the notice contains none of your data. You can request up to three copies a day. The file does not include Mia chat history, account activity logs, or billing records; for a copy of those, email privacy@miasure.com from the address you sign in with.
• Delete my account (Right to Delete): You can close your account after confirming it is you with your current password and, if you use one, your authenticator code. What is deleted, what is kept, and which accounts must be closed by email instead are described in Section 7.

The Response Timeframe below applies to requests made by email. The in-app options act without waiting for us: a copy of your data is usually ready within minutes, and an account is closed when you confirm.

Response Timeframe: We will acknowledge receipt of your request within 10 business days. We will respond to verified requests within 45 calendar days from receipt. If we require additional time (up to an additional 45 days), we will inform you of the reason and extension in writing.

Authorized Agents: You may designate an authorized agent to submit a privacy rights request on your behalf. To do so, you must provide the authorized agent with written permission and we may require you to verify your identity directly with us. An authorized agent may also submit a request with a valid power of attorney.

Appeal Process: If we deny your privacy rights request in whole or in part, you have the right to appeal our decision. To appeal, please contact us at privacy@miasure.com with the subject line "Privacy Rights Appeal" within 60 days of receiving our decision. We will respond to your appeal within 60 days. If the appeal is denied, we will provide you with instructions on how to contact your state's Attorney General to submit a complaint.

California "Shine the Light" (Civil Code § 1798.83): California residents may request information about whether we have disclosed personal information to third parties for their direct marketing purposes. As stated above, Nexture AI does not share personal information with third parties for their direct marketing purposes.

9. Data Security

We implement robust technical and organizational measures to protect your personal information from unauthorized access, use, alteration, or disclosure. For a detailed description of our security practices, please refer to our Security Statement.

What is encrypted at rest: Your uploaded documents and the structured policy data we extract from them are encrypted at rest using AES-256-GCM with per-tenant keys managed in AWS Key Management Service (KMS). This includes coverage details, limits, premiums, agent reasoning, audit history, deliverable content, communications bodies, client contact details, and the cross-tenant audit log.

What is plaintext at the database level: A small number of identifiers necessary for product functionality — insured name on a policy, carrier name, policy number, document filename, client legal name, and your account email — are stored as plaintext so that search, filtering, and navigation work efficiently across your library. These identifiers are protected by per-tenant access scoping, multi-factor employee authentication, audit logging, and TLS encryption in transit. We disclose this transparently; the alternative (encrypting these fields) is on our roadmap (Security Statement § 3.1.1) as a customer-controlled key-revocation feature.

What we can see while you are an active customer: Our extraction pipeline and AI agents must process your documents in plaintext to do their work (OCR, language-model extraction, SOIFA responses, deliverable generation). Employees with production code-deploy access therefore have the technical capability to access in-flight data while your account is active; that access is constrained by access controls, audit logging, and the contractual obligations described in our Security Statement. We do not claim that our employees cannot read your data while you use the Service; we claim they are constrained from doing so without authorization.

10. Data Breach Notification

In the event of a security breach that results in the unauthorized access, acquisition, or disclosure of your personal information, Nexture AI will:

• Investigate promptly: We will immediately investigate the scope and nature of the breach and take steps to contain and remediate it.
• Notify affected individuals: We will notify affected users without unreasonable delay, and no later than 60 days after discovery of the breach (or sooner where required by applicable state law). Notification will be provided via email to the address associated with your account.
• Notify regulators: We will notify applicable state attorneys general and regulatory authorities as required by law.
• Notification content: Breach notifications will include a description of the incident, the types of information involved, the steps we are taking in response, and steps you can take to protect yourself.
• Broker notification: For Broker Users, we will also notify you of any breach affecting your clients' NPI so that you can fulfill your own notification obligations as the data controller.

11. International Data Transfers

Nexture AI is based in the United States and primarily stores and processes data within the United States (AWS us-east-1, N. Virginia). Our Service is primarily designed for users located in the United States. However, some of our sub-processors, including LLM providers, may process data in other regions as part of their service delivery. In all cases:

• We ensure that sub-processors are bound by contractual obligations to protect your data consistent with this Privacy Policy.
• Data transfers are limited to what is necessary for the specific processing purpose.
• If you are located outside the United States and choose to use our Service, you understand and consent to your data being transferred to, stored, and processed in the United States, which may have different data protection standards than your jurisdiction.

If you are located in the European Economic Area (EEA), United Kingdom, or other jurisdiction with data protection laws that may differ from U.S. law, please note that we may not offer the full range of protections required under your local law, such as the General Data Protection Regulation (GDPR). We are committed to working with users and organizations to address cross-border data protection concerns. If you have questions about international data use, please contact us at privacy@miasure.com.

12. Children's Privacy

Our Service is not intended for individuals under the age of 18. We do not knowingly collect personal information from children under 18. If we become aware that we have inadvertently collected personal information from a child under 18, we will take steps to delete that information as quickly as possible.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. We will notify you of any material changes by posting the new Privacy Policy on this page and updating the "Effective Date" at the top. For material changes, we will also provide notice via email or a prominent in-app notification at least 30 days before the changes take effect. We encourage you to review this Privacy Policy periodically.

14. Contact Information

If you have any questions or concerns about this Privacy Policy or our privacy practices, please contact us at: