Legal

Privacy Policy

Last updated: June 1, 2026

Introduction

Parallel Strategies AI ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our platform and services. Please read this policy carefully to understand our practices regarding your personal data. Our data practices are designed to be no less protective than the privacy policies of the third-party platforms we integrate with, including Google (Gmail and Google Analytics), LinkedIn Company Pages, X (formerly Twitter), TikTok, and Meta (Facebook and Instagram). Our use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Information We Collect

Account Information

When you create an account, we collect your name, email address, company name, and password. If you sign up through a social provider, we may receive additional profile information.

Usage Data

We automatically collect information about how you interact with our platform, including pages visited, features used, and actions taken within the application.

Integration Data

When you connect third-party services (CRM, social media, etc.), we access and store data necessary to provide our services, such as contact information, social media posts, and communication records.

Device Information

We collect information about the device you use to access our platform, including IP address, browser type, operating system, and device identifiers.

Google Services Data (Gmail & Google Analytics)

When you connect a Google account to Parallel Strategies AI, we access Google APIs on your behalf to provide the specific features you authorize. This section describes how we handle Google user data in compliance with the Google API Services User Data Policy, including the Limited Use requirements that apply to Gmail and Google Analytics data.

What Google User Data We Access

We only request the OAuth scopes required for features you explicitly enable. The Google user data accessed by our platform is:

Gmail (when you connect Gmail)

  • https://www.googleapis.com/auth/gmail.readonly — read email messages, threads, labels, and metadata in your mailbox so we can display your inbox, sync conversations to CRM contacts, and surface replies inside the platform.
  • https://www.googleapis.com/auth/gmail.send — send emails on your behalf from your connected Gmail address when you compose, reply, or run an outbound campaign step inside the platform.
  • https://www.googleapis.com/auth/gmail.modify — modify message state (mark as read, archive, apply labels, move) and manage push-notification watches so the platform stays in sync with your mailbox.
  • Your Google account email address and basic profile (name, picture).

Google Analytics (when you connect a GA4 account)

  • https://www.googleapis.com/auth/analytics.readonly — read your Google Analytics data, including reports, properties, views, and configuration accessed via the Google Analytics Data API and Admin API.
  • https://www.googleapis.com/auth/analytics.edit — manage your Google Analytics property configuration (such as creating custom dimensions or data streams) only when you initiate those actions from inside the platform.
  • https://www.googleapis.com/auth/analytics.manage.users.readonly — read the list of users who have access to your GA property so we can display permissions and route data correctly.

Google Calendar (when you connect a calendar)

  • https://www.googleapis.com/auth/calendar.readonly — read-only access to your calendar list and events, used solely to display your calendars alongside your CRM pipeline inside the platform's Calendar module. We never create, edit, or delete your calendar events.

How We Use Google User Data

Google user data is used exclusively to provide the user-facing features you have authorized:

  • Gmail inbox & threads: display your messages inside the CRM, attach them to the correct contact or deal, and show reply status on outbound campaigns.
  • Outbound email: send messages, drafts, replies, forwards, and campaign steps from your address via the Gmail API.
  • Sync state: mark messages read, apply labels, archive, and renew Gmail push-notification watches so the inbox stays in sync.
  • Analytics dashboards: render charts, reports, and AI-generated summaries of your Google Analytics traffic, conversions, and audience data inside the platform.

We do not use Google user data for any purpose other than to provide and improve these user-facing features.

Limited Use — What We Will Never Do

Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

  • We do not sell Google user data.
  • We do not use Google user data to serve advertisements, including personalized, remarketing, or interest-based advertising.
  • We do not transfer Google user data to third parties except as needed to provide or improve user-facing features, to comply with applicable law, or as part of a merger, acquisition, or sale of assets with notice to users.
  • We do not use Google user data, including the contents of Gmail messages or Google Analytics reports, to train generalized or third-party AI or machine learning models.
  • To power user-facing AI features inside the platform (such as Google Analytics summaries, insights, drafts, and assistant responses), portions of your Google Analytics data may be sent to third-party AI providers — specifically OpenAI and Anthropic — for inference. These providers process the data on a per-request basis to return a response to you and, under the API terms we use, do not retain that data for training their models. We only send the minimum data needed to fulfill the feature you triggered.
  • Humans do not read your Gmail messages or Google Analytics data except (a) with your explicit consent, (b) for security investigations or to comply with law, or (c) when the data has been aggregated and anonymized for internal operations.

How Google Data Is Stored & Protected

OAuth refresh and access tokens for your Google account are stored encrypted in our backend database (Xano, hosted on Google Cloud / AWS infrastructure) and are scoped to your user record and company workspace. Gmail message content that we display is fetched on demand from the Gmail API; we cache metadata (message IDs, thread IDs, subject, sender, timestamp, and labels) and store the bodies of messages you explicitly send through the platform (so we can show them in your sent log and attribute them to CRM activity). Google Analytics responses are cached transiently to render dashboards and are not exported off-platform. All data is transmitted over TLS and access is restricted via per-company scoping and authenticated API requests.

Sharing of Google User Data

We do not sell Google user data, and we do not share it with third parties for their own purposes. We share Google user data only with the subprocessors that make our platform run, and only to the extent each subprocessor needs it to deliver its service:

  • Xano — backend database and API platform where your account, tokens, and synced metadata are stored.
  • Vercel — hosting for the web application that displays your data to you.
  • Amazon Web Services (AWS) — Lambda and supporting infrastructure that proxies certain Google API operations.
  • Anthropic (Claude) — AI model provider that powers in-product summaries, insights, and drafts. Portions of your Google Analytics data may be sent to Anthropic for inference when you trigger an AI feature. Under Anthropic's API terms, customer data submitted via the API is not used to train Anthropic models.
  • OpenAI — AI model provider that powers in-product summaries, insights, and drafts. Portions of your Google Analytics data may be sent to OpenAI for inference when you trigger an AI feature. Under OpenAI's API terms, data submitted via the API is not used to train OpenAI models by default.

These subprocessors are contractually bound to handle Google user data in a manner consistent with this Privacy Policy and the Google API Services User Data Policy, including the Limited Use requirements. Google user data is transferred to OpenAI and Anthropic only as needed to provide or improve user-facing features.

Retention & Deletion of Google Data

We retain Google user data only as long as needed to provide the features you have enabled. You can remove your Google data at any time using any of the following methods:

  • Disconnect Gmail or Google Analytics from inside the platform's Integrations / Settings page. This revokes our stored tokens and deletes the related cached data.
  • Revoke our access directly from your Google account at myaccount.google.com/permissions. Once revoked, our tokens stop working and the associated data is purged on our next sync.
  • Email us at support@parallelstrategies.ai with a deletion request. We will delete all Google user data tied to your account within 30 days of confirming the request.

X (Twitter) Data

When you connect your X account to Parallel Strategies AI, we access X's API on your behalf to provide analytics and AI-powered insights. This section describes how we handle that data in compliance with the X Developer Agreement and Policy.

What X Data We Access

  • Your public profile information (username, display name, profile image, bio)
  • Tweet content, impressions, and engagement metrics (likes, retweets, replies, clicks)
  • Follower and following counts and growth trends
  • Audience demographic insights available through the X API
  • Account-level analytics (total impressions, engagement rate, media views)

How We Use X Data

  • To display your X analytics dashboard within our platform
  • To power AI-generated insights, content recommendations, and performance analysis
  • To identify trends in your posting activity and audience engagement
  • To generate reports and summaries on your behalf

We use X data solely to provide the services you have authorized. We do not use X data for any purpose inconsistent with your reasonable expectations or X's Developer Policy.

X Data Retention & Deletion

We retain X data only as long as necessary to provide our services or as required by law. If you disconnect your X account or request deletion of your data, we will delete all stored X data associated with your account within 30 days. You may submit a data deletion request by contacting us at support@parallelstrategies.ai.

No Surveillance or Tracking

We do not use X data to track, monitor, or surveil X users, individuals, or groups. We do not use X data to monitor sensitive topics, political events, protests, rallies, or community organizing activities. Our platform is designed exclusively to help you understand and improve your own X account performance.

No Off-Platform Advertising

We do not use X data to serve advertisements to users on platforms other than X, and we do not sell or license X data to advertising networks or data brokers for targeting purposes.

Off-Platform Data Matching

We do not associate your X user data with data from other platforms or external identifiers without your express, informed, opt-in consent. If we introduce any cross-platform data linking features in the future, we will request your explicit permission before enabling them.

Third-Party Compliance

Any third-party service providers who receive X data as part of delivering our platform (e.g., hosting, analytics infrastructure) are contractually required to handle that data in compliance with X's Terms of Service, Privacy Policy, Developer Agreement, and Developer Policy.

TikTok Data

When you connect your TikTok account to Parallel Strategies AI, we access TikTok's official APIs on your behalf — including the TikTok Content Posting API and TikTok Login Kit user-data scopes — to display analytics, manage your connected account, and publish video content when you explicitly choose to post. This section describes how we handle TikTok user data in compliance with TikTok's Terms of Service and TikTok's Privacy Policy.

What TikTok Data We Access

We only request the OAuth scopes required for TikTok features you explicitly enable. The TikTok user data accessed by our platform is:

Basic profile information (user.info.basic)

  • TikTok open ID and union ID
  • Display name and avatar URL

Display profile information (user.info.profile)

  • Username and bio/description
  • Profile deep link and verification status
  • Large-format avatar image URL

Account statistics (user.info.stats)

  • Follower count, following count, total likes, and video count

Video publishing (video.publish)

  • When you compose and publish a video from inside the platform, we upload the video file and metadata (title, caption/description, privacy level, and posting options you select) to TikTok on your behalf via the official TikTok Content Posting API.
  • We also retrieve your public video list and per-video performance metrics (views, likes, comments, shares, cover image, duration, and share URL) to power your TikTok analytics dashboard.
  • We query creator posting settings (such as available privacy levels and maximum video duration) so the compose flow shows only options TikTok allows for your account.

How We Use TikTok Data

TikTok user data is used exclusively to provide the user-facing features you have authorized:

  • Account connection: identify and display your connected TikTok account inside the platform.
  • Analytics dashboards: show your profile stats, video library, and engagement metrics so you can track performance over time.
  • Video publishing: publish videos to your TikTok account only when you initiate a post and confirm the content, privacy settings, and posting options.
  • Compose compliance: load creator-specific posting constraints from TikTok so you can choose valid privacy levels and posting settings before publishing.

We do not use TikTok user data for advertising, profiling unrelated users, or any purpose other than to provide and improve these user-facing features.

How TikTok Data Is Stored & Secured

OAuth access and refresh tokens for your TikTok account are stored encrypted in our backend database (Xano, hosted on Google Cloud / AWS infrastructure) and are scoped to your user record and company workspace. TikTok profile fields, account statistics, and cached video metadata are stored in the same backend and are accessible only to authenticated users within your company workspace. Video files you choose to publish are transmitted directly to TikTok's upload endpoints over TLS during the posting flow; we do not retain uploaded video binaries after TikTok confirms the publish request. All API communication uses HTTPS/TLS, and access is restricted via per-company scoping and authenticated API requests.

Retention & Deletion of TikTok Data

We retain TikTok user data only as long as needed to provide the features you have enabled, and no longer than 30 days after you disconnect your TikTok account or revoke our access. When you disconnect or revoke access, we delete stored TikTok OAuth tokens, profile data, cached video metadata, and analytics associated with your account. You can remove your TikTok data at any time using any of the following methods:

  • Disconnect TikTok from inside the platform's Integrations page or TikTok analytics module. This revokes our stored tokens and deletes the related cached TikTok data from our systems.
  • Revoke our access directly from your TikTok account at tiktok.com/setting/manage-permissions. Once revoked, our tokens stop working and the associated TikTok data is deleted from our platform.
  • Email us at support@parallelstrategies.ai with a deletion request. We will delete all TikTok user data tied to your account within 30 days of confirming the request.

No Sale or Unauthorized Sharing of TikTok Data

We do not sell TikTok user data. We do not share TikTok user data with third parties for their own marketing, advertising, or data-broker purposes. We honor user revocation: when you disconnect TikTok or revoke our app's access, we stop collecting new TikTok data and delete the TikTok data we previously stored, as described above. We share TikTok user data only with the subprocessors that operate our platform (listed below) and only to the extent each subprocessor needs it to deliver its service.

Sharing of TikTok User Data

We do not sell TikTok user data, and we do not share it with third parties for their own purposes. We share TikTok user data only with the subprocessors that make our platform run:

  • Xano — backend database and API platform where your account, tokens, and synced TikTok metadata are stored.
  • Vercel — hosting for the web application that displays your TikTok data to you.
  • Amazon Web Services (AWS) — supporting infrastructure that proxies certain TikTok API operations.
  • TikTok — when you connect your account or publish a video, data is transmitted to TikTok's official APIs to authenticate you and complete the actions you request.

These subprocessors are contractually bound to handle TikTok user data in a manner consistent with this Privacy Policy and TikTok's developer and platform policies.

Meta (Facebook & Instagram) Data

When you connect Meta to Parallel Strategies AI via Facebook Login, we access the Meta Graph API on your behalf after you grant permissions on Meta's consent screen. This section describes how we handle Meta user data in compliance with the Meta Platform Terms and Meta Developer Policies.

What Meta data we collect

Authenticated user (Facebook Login)

  • Meta user ID, name, email (when shared), and profile picture
  • Pages and Instagram professional accounts you authorize, including names and identifiers needed to publish and read analytics

Facebook Page data

  • Posts, comments, reactions, and Page insights you enable

Instagram professional account data

  • Media, comments, and insights for accounts linked to authorized Pages

Data about other Meta users

When you view comments or reactions on your content, we may receive limited profile fields for those users (for example, name and photo) solely to display them in your workspace. This data is cached briefly for display and is not stored long-term or used for profiling unrelated users.

How we obtain Meta data

We obtain Meta data only through the Meta Graph API after you complete Facebook Login and authorize the permissions our features require. We do not scrape Meta properties outside those APIs.

How we use Meta data

We use Meta data only for purposes you enable, including:

  • Publishing posts to Facebook Pages and Instagram accounts you manage
  • Displaying comments, reactions, and engagement on your content
  • Reporting and analytics dashboards inside the Platform

We do not use Meta data for advertising, surveillance, or any purpose outside these user-facing features or beyond each permission's allowed usage.

Legal basis (GDPR)

Where the GDPR applies, we process Meta data based on your consent when you connect Meta and authorize scopes, and on our legitimate interests in operating, securing, and improving the service — limited to what is necessary for those purposes.

Sharing, subprocessors, and no sale of Meta data

We do not sell Meta user data. We share Meta data only with subprocessors that operate our platform (for example Xano for storage, Vercel for hosting, and AWS for supporting infrastructure) and only to the extent each needs it to deliver the service. When you publish or read data, information is also transmitted to Meta's APIs as required to complete the action you request.

Retention

We retain Meta data only as long as needed to provide the features you enable. OAuth tokens and your admin profile remain until you disconnect Meta or request deletion. Cached fields for other users' profiles are kept only briefly for display. We delete Meta data when you disconnect, remove our app from Facebook, or submit a verified deletion request, as described on our Data Deletion page.

Security

Meta OAuth tokens and synced data are transmitted over TLS and stored in our backend with access restricted by authentication and per-company workspace scoping. Tokens are stored encrypted at rest.

International transfers

Meta data may be processed in the United States and other countries where our subprocessors operate. Where required, we rely on appropriate safeguards for cross-border transfers.

Your rights and data deletion

You may disconnect Meta from Integrations or the Meta analytics module, revoke our app in your Facebook settings, or follow the steps on our Data Deletion page. You may also email privacy@parallelstrategies.ai to request access to or deletion of your data. We honor verified requests within 30 days.

LinkedIn Data

When you connect LinkedIn to Parallel Strategies AI, we access LinkedIn's APIs on your behalf after you complete LinkedIn's OAuth consent screen. By default we request the openid, profile, email, and w_member_social scopes (Sign In with LinkedIn and Share on LinkedIn) to identify your account and publish posts to your own member profile when you choose. Where your connection includes organization permissions, we additionally use LinkedIn's Community Management APIs for the Company Page features described below. This section describes how we handle LinkedIn member and organization data in compliance with the LinkedIn Marketing API Terms, LinkedIn's data storage requirements, and applicable privacy laws.

Data about you (authenticated admin)

When you sign in with LinkedIn, we receive profile information for the account that authorizes access, such as:

  • LinkedIn member ID / URN
  • Name, email address (when shared), headline, and profile photo URL
  • When your connection includes organization permissions: organizations (Company Pages) you administer, including page name, logo, and identifiers needed to post and read analytics

Data about other LinkedIn members

When you view comments, reactions, or engagement on your Page's posts, we may retrieve limited profile fields for commenters and reactors (for example, name, headline, and photo) solely to display them in your workspace. This data is cached briefly for display and is not stored long-term, consistent with LinkedIn's storage limits.

Organization and engagement data

  • Posts, comments, nested replies, and reactions on Pages you manage
  • Page and post analytics (impressions, clicks, shares, follower statistics, and related reporting metrics)

How we use LinkedIn data

We use LinkedIn data only to provide features you enable:

  • Publishing posts to your own member profile when you compose and publish them in the platform
  • Publishing and scheduling posts to Company Pages you administer (when your connection includes organization permissions)
  • Displaying comments, replies, and reactions in post detail views
  • Showing engagement and page analytics dashboards and reports
  • Maintaining your connection and syncing content you request

We do not use LinkedIn data for advertising, profiling unrelated members, surveillance, or any purpose outside these user-facing features.

Legal basis (GDPR)

Where the GDPR applies, we process LinkedIn data based on your consent when you connect LinkedIn and authorize the requested scopes, and on our legitimate interests in operating, securing, and improving the service you use — limited to what is necessary for those purposes.

Sharing, subprocessors, and no sale of data

We do not sell LinkedIn member data. We share LinkedIn data only with subprocessors that operate our platform (for example Xano for storage, Vercel for hosting, and AWS for supporting infrastructure) and only to the extent each needs it to deliver the service. When you publish or read data, information is also transmitted to LinkedIn's APIs as required to complete the action you request.

Retention (aligned with LinkedIn limits)

We retain LinkedIn data only as long as needed to provide the service and in line with LinkedIn's data storage requirements and our backend cleanup jobs:

  • Other members' profile data (commenters/reactors): cached for up to 24 hours, not stored long-term
  • Members' social activity content (e.g. comment text): up to 48 hours unless deleted sooner
  • Organization social activity: up to 6 weeks (up to 6 months where the organization authenticated the connection)
  • Page admin and reporting data: up to 1 year
  • OAuth tokens and your admin profile: until you disconnect LinkedIn or request deletion, then deleted as described below

Security

LinkedIn OAuth tokens and synced data are transmitted over TLS and stored in our backend with access restricted by authentication and per-company workspace scoping. Tokens are stored encrypted at rest.

International transfers

LinkedIn data may be processed in the United States and other countries where our subprocessors operate. Where required, we rely on appropriate safeguards (such as standard contractual clauses) for cross-border transfers.

Your rights, deletion, and disconnect

You may disconnect LinkedIn from the dashboard (module hub or LinkedIn analytics module), which stops API access and triggers deletion of stored LinkedIn tokens and associated data for your workspace, subject to the retention windows above for cached third-party member fields. You may also email privacy@parallelstrategies.ai to request access to or deletion of your data; we will honor verified requests and LinkedIn Marketing API Terms deletion requirements.

How We Use Your Information

  • To provide, maintain, and improve our services
  • To process transactions and send related information
  • To send you technical notices, updates, and support messages
  • To respond to your comments, questions, and customer service requests
  • To communicate with you about products, services, and events
  • To monitor and analyze trends, usage, and activities
  • To detect, investigate, and prevent fraudulent transactions and other illegal activities
  • To personalize and improve your experience

Information Sharing

We do not sell your personal information, and we do not use Google user data, LinkedIn data, X data, TikTok data, or Meta data for advertising. We share your information only with the subprocessors that operate our platform, and only to the extent each one needs to deliver its service:

Subprocessors We Use

  • Xano — backend database, authentication, and API platform.
  • Vercel — web application hosting.
  • Amazon Web Services (AWS) — Lambda and supporting infrastructure for proxied operations.
  • Anthropic (Claude) — AI model provider for in-product summaries, drafts, and assistant features. Data submitted via the Anthropic API is not used to train Anthropic models.
  • OpenAI — AI model provider for in-product summaries, drafts, and assistant features. Data submitted via the OpenAI API is not used to train OpenAI models by default.
  • Stripe — payment and subscription processing.
  • Twilio — VoIP and telephony for in-product calling features.
  • PeopleDataLabs — contact-enrichment data for CRM records you explicitly choose to enrich.
  • Google (Gmail and Analytics APIs), LinkedIn (Community Management APIs), X (Twitter API), TikTok (Login Kit and Content Posting API), and Meta (Facebook and Instagram APIs) — only when you connect those accounts; we read and write data to those platforms on your behalf as described above.

All subprocessors that handle Google user data are contractually bound to comply with the Google API Services User Data Policy. All subprocessors that handle LinkedIn data are contractually bound to comply with the LinkedIn Marketing API Terms and LinkedIn's data and security requirements. All subprocessors that handle X data are contractually bound to comply with X's Developer Policy. All subprocessors that handle TikTok and Meta data are contractually bound to comply with those platforms' terms and developer policies.

Legal Requirements

We may disclose information if required by law or in response to valid requests by public authorities (e.g., court orders or government agencies).

Business Transfers

If we are involved in a merger, acquisition, or sale of assets, your information may be transferred as part of that transaction. Any successor entity will be required to honor this Privacy Policy.

Data Security

We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction. This includes encryption of data in transit and at rest, regular security assessments, and access controls. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

Your Rights

Depending on your location, you may have the following rights regarding your personal data:

  • Access: Request a copy of the personal data we hold about you
  • Correction: Request that we correct inaccurate or incomplete data
  • Deletion: Request that we delete your personal data, including any LinkedIn, X, TikTok, or Meta data we have stored on your behalf
  • Portability: Request a copy of your data in a portable format
  • Opt-out: Opt out of marketing communications at any time
  • Revoke X Access: Disconnect your X account at any time via your account settings, which will stop all X API access and trigger deletion of stored X data
  • Revoke TikTok Access: Disconnect your TikTok account at any time via the Integrations page or TikTok module in your dashboard, which stops all TikTok API access and triggers deletion of stored TikTok data. You may also revoke access at tiktok.com/setting/manage-permissions, or email support@parallelstrategies.ai to request deletion.
  • Revoke Google Access: Disconnect Gmail or Google Analytics from inside the platform's Integrations page, or revoke our access directly at myaccount.google.com/permissions. Either action stops further Google API access and triggers deletion of stored Google user data
  • Revoke LinkedIn Access: Disconnect LinkedIn from the module hub or LinkedIn analytics module, which stops API access and triggers deletion of stored LinkedIn data. You may also email privacy@parallelstrategies.ai for a deletion request
  • Revoke Meta Access: Disconnect Meta from Integrations or the Meta analytics module, or remove our app from your Facebook account settings. See our Data Deletion page for full instructions

To exercise any of these rights, please contact us using the information provided below.

Cookies

We use cookies and similar tracking technologies to collect and track information about your activity on our platform. Cookies are small data files stored on your device. We use both session cookies (which expire when you close your browser) and persistent cookies (which remain until deleted). You can control cookie preferences through your browser settings, though disabling cookies may affect the functionality of our services.

Regulatory Compliance

We design our data practices to comply with applicable laws, including the EU General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) where they apply. Our handling of LinkedIn data complies with the LinkedIn Marketing API Terms and LinkedIn's data storage, privacy, and security requirements. Our handling of Meta data complies with the Meta Platform Terms and Meta Developer Policies. If you are a California resident, you may have additional rights to know, delete, and opt out of certain sharing; contact us at privacy@parallelstrategies.ai.

Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. We encourage you to review this Privacy Policy periodically for any changes. Changes are effective when they are posted on this page.

Contact Us

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

Parallel Strategies AI

Organized under the laws of the State of Delaware, United States

Website: parallelstrategies.ai

Privacy: privacy@parallelstrategies.ai

Support: support@parallelstrategies.ai