Privacy Policy

Effective date: September 8, 2026

Last updated: September 8, 2026

About this policy

Atlas is a hosted agentic trading infrastructure service operated by [LEGAL ENTITY NAME] through the Atlas website. In this policy, “Atlas,” “we,” “us,” and “our” refer to that operator. We are the controller responsible for personal information we process for the purposes described here.

This policy covers visitors to our website and the use of Atlas accounts, hosted agents, connections, subscriptions, support, and separately enabled Rewards Sharing and yield features. The trading and protocol integrations covered by this policy are Polymarket, predict.fun, Hyperliquid, and Morpho. Polymarket means its international service, not Polymarket US. Availability and the information needed depend on the integration and features you select. This policy governs Atlas processing, not the independent activities of those services or public blockchain participants.

Atlas offers a free tier and paid subscriptions to eligible international consumers. All US users are excluded from using the service. This restriction does not waive or limit applicable privacy rights of website visitors, including visitors in the United States. Using Atlas or accepting its terms is not blanket consent to every processing activity.

You can access this Privacy Policy on our website. Our Terms of Service address service eligibility, permissions, and use of Atlas. Our correspondence address is 276 Fifth Ave, Ste 704 PMB 137, New York, NY 10001, United States.

Information we collect

The information involved depends on your interactions, connected services, and agent permissions. We collect information you provide, information generated through service operation, and information received from the sources described in “Where information comes from.”

Account and communications information

We process account identifiers, contact information you provide, authentication records, subscription status, preferences, consent records, and correspondence. Support requests include their contents, attachments, and the information necessary to investigate and resolve an issue. We ask you to provide only personal information relevant to your request.

Agent inputs, outputs, and research

We process agent instructions, strategies, prompts, chat history, uploaded material, objectives, configured limits, generated responses, research results, and activity records. Context can include market information, external research, tool results, positions, balances, and transaction status needed to answer a request or operate an agent.

External research can contain personal information published by others. Agent outputs can infer preferences, risk tolerance, or trading intentions from your instructions and activity. These inferences can be inaccurate. Sensitive personal information should be included only when necessary for a specifically supported function. We do not seek unrelated health, biometric, political, religious, or similarly sensitive information for trading or agent operation.

Connections, credentials, and transactions

We process connected account and wallet identifiers, public addresses, networks, supported assets, balances, positions, orders, trading history, transaction hashes, counterparties or destination addresses, fees, timestamps, and execution results. We also process connection status, requested and granted permissions, authorization scopes, approvals, changes to limits, revocation requests, and related evidence.

Depending on the connection you select, Atlas processes API credentials, access tokens, session credentials, delegated signing credentials or permissions, and other authorization material needed for the connection. Permissions can enable asset movements, not just access to balances or other information. Atlas can use granted authority to initiate trades, withdrawals, transfers, swaps, and bridging without fresh approval for every action.

If you choose custody or key management through a wallet provider, that provider manages the relevant private keys under the arrangement you select. Other connections can involve wallet approvals, signing requests, or delegated authority available to Atlas. The selected arrangement determines the credentials Atlas and the provider receive, store, or use. Before you authorize a connection, we identify the selected wallet provider, the relevant custody or signing arrangement, the information and permissions requested, and the available revocation methods.

Rewards, yield, and other authorized position activity

If you enable Rewards Sharing or yield features within the covered integrations, we process program eligibility, covered positions and enrollment periods, reward estimates and receipts, gross and net distributions, accepted fee schedules, calculation records, and payment or correction history. Yield records can include protocol and network identifiers, selected markets or vaults, contract addresses, receipt tokens or shares, deposits, redemptions, allocation settings, reinvestment choices, external fees, and withdrawal status.

We also process feature consents, approved amounts and destinations, fee collection authority, changes, opt out times, and revocation records. Where a separately authorized strategy within the covered integrations involves borrowing or derivatives, we process relevant debt, collateral, margin, liquidation, and position records. Collecting these categories does not grant permission to enable a feature or increase its scope.

Subscription and payment information

For paid subscriptions, we process the chosen plan, billing contact information, invoice details, payment status, transaction references, refunds, and information needed for billing or tax obligations. A selected payment provider processes payment instrument and transaction information needed for the chosen payment method. The payment method and integration determine whether Atlas receives payment identifiers, limited instrument details, or other billing information.

Before payment information is collected, we identify the selected payment provider, explain the information requested and the respective roles of Atlas and that provider, and make the provider's privacy notice available. We limit the payment information Atlas receives and retains to what is necessary for billing, reconciliation, security, support, and applicable legal obligations.

Device, operational, and eligibility information

We process IP addresses, browser and device characteristics, request timestamps, session identifiers, connection events, error reports, performance measurements, and security logs. IP addresses can indicate approximate location. These records can relate to visitors without accounts. Routine diagnostics exclude private chats, strategies, credentials, and complete transaction histories unless a limited excerpt is necessary to investigate a specific operational or security issue.

Eligibility checks can involve location declarations, approximate location, account information, and screening results necessary to apply service restrictions or applicable law. If a particular feature or provider requires identity or sanctions verification, the relevant information can include a name, date of birth, address, identification document, or verification result. Before that collection, we explain what is required, why, who receives it, and whether Atlas receives documents or only a result. We identify any selected verification provider and its privacy notice at that stage. We do not require every visitor or user to submit identity documents or undergo a full identity verification process.

Where information comes from

We receive information directly from you and automatically through your interactions with Atlas. Other sources include agents operating on your instructions, connected wallets and the covered integrations, payment providers, public blockchain records, public research sources, research services, and people authorized to contact us for you. If verification is required for a selected function, we can receive the disclosed information from the identified verification provider.

Connecting a service allows information exchange within the authorized scope. It is not permission to obtain unrelated information. An external provider acting independently is responsible for its own processing under its privacy notice and applicable law.

Why we process information and our legal grounds

Where applicable law requires a legal basis, we apply the basis appropriate to the particular purpose and information:

Providing requested services. We use account, authentication, agent, connection, transaction, subscription, and enabled feature information to create and administer accounts, operate agents, retrieve research, maintain context, apply instructions and limits, execute authorized activity, reconcile balances, administer rewards and yield, calculate agreed fees, process payments and refunds, and provide requested support. We rely on contract necessity only to the extent processing is objectively necessary to provide the service you request.

Security and reliability. We use proportionate account, device, operational, connection, and relevant transaction information to prevent fraud and abuse, investigate unauthorized activity, enforce eligibility restrictions and service terms, and diagnose service failures. Where recognized by law, we rely on legitimate interests in protecting people, accounts, systems, and service reliability, after assessing necessity and balancing those interests against your rights. We rely on a legal obligation instead where a particular check is required by law.

Accounting, compliance, and legal rights. We use necessary billing, transaction, authorization, eligibility, and correspondence records to meet applicable tax, accounting, or other legal duties. Where permitted, we rely on legitimate interests to establish, exercise, or defend legal claims and resolve disputes. We do not treat all possible compliance activity as legally mandatory.

Operational communications. We use contact and account information to send service, security, subscription, and transaction notices. The basis is contract necessity, a relevant legal obligation, or a necessary and balanced legitimate interest, depending on the notice.

Optional analytics and offers. We use information for optional service analytics and optional marketing communications only after affirmative consent. We explain the information, purpose, and choices when requesting that consent. These activities do not authorize behavioral advertising or model training.

Other consent based processing. We obtain any specific or separate consent required for sensitive information, a covered automated decision, or another regulated activity. We do not rely on general acceptance of this policy as that consent.

Contract necessity does not cover every activity simply because it appears in our Terms. Where local law requires a different permitted ground, additional consent, or another condition, we meet that requirement before the affected processing. We do not use personal information for an incompatible new purpose without the required notice and lawful basis.

Providing information necessary for an account, connection, payment, or required eligibility check is a condition of the affected function. Without it, we may be unable to provide that function, but refusal of optional consent does not prevent unrelated essential use. Authorization for an agent to transact is distinct from privacy consent.

You can withdraw privacy consent through the channel used to give it or by contacting privacy@askatlas.gg. We make withdrawal as easy as giving consent. Withdrawal does not affect the lawfulness of earlier processing, and we explain any effect on a feature that depends on the withdrawn consent.

Agent operation and automated decisions

Within granted permissions and configured instructions, agents can initiate trades, withdrawals, transfers, swaps, and bridging without fresh user approval for each action. They process instructions, research, market conditions, account information, and configured limits to select and submit actions. Separately enabled automation can also assess reward eligibility, calculate agreed fees, claim rewards, supply or redeem assets, and perform authorized reinvestments or reallocations.

Models generate responses or proposed actions by identifying patterns in the context supplied to them. Models and execution logic use the relevant instructions, permissions, market or account information, and configured checks to determine requests sent for execution. Eligibility or security rules can also restrict access based on the information used for those checks. These processes can affect access, balances, positions, asset exposure, fees, and financial outcomes. Models are probabilistic and can misinterpret instructions or use incomplete or inaccurate information. Human review does not occur before every order or transaction.

Where processing constitutes a decision based solely on automated processing that produces legal or similarly significant effects, including under the EU GDPR, UK data protection law, or an analogous law, we will not enable that covered processing unless a legally permitted condition and the required safeguards are in place. We use express, specific consent where that is the applicable condition, or another basis that the law expressly permits for that decision, such as strict contract necessity or legal authorization with the required safeguards. A general legitimate interest, ordinary feature authorization, or acceptance of this policy is not sufficient by itself.

You can request meaningful information about a covered decision, express your view, contest the outcome, or request human intervention by emailing privacy@askatlas.gg. We will arrange review by a trained person with authority to assess the relevant inputs, logs, decision logic, permissions, and your explanation; identify and correct relevant inaccuracies; and change an access decision or future operation where appropriate. We will explain the result and any available further challenge. You can withdraw consent for future covered processing and request that the affected automation stop.

Human intervention does not promise to reverse a transaction already submitted or completed, undo an irreversible blockchain action, or restore a market opportunity. If the required legal conditions or meaningful review arrangements cannot be met, we will not provide the affected automated feature. Accepting this policy does not itself authorize deployment of assets, fee collection, borrowing, or publication of activity.

Model providers and our prohibition on training

Operating an agent requires sending relevant prompts, instructions, conversation context, research, tool results, and requested account or transaction context to model providers for inference, meaning generating responses or actions. The necessary context depends on the task and can contain personal or commercially sensitive information. We limit the context supplied to what is needed for the requested operation.

We do not use your agent instructions, chats, prompts, outputs, strategies, trading history, account data, reward or yield records, or other user information to train, fine tune, or improve any machine learning model, whether our own or another party's. This prohibition also covers versions described as deidentified, anonymized, or aggregated.

We require model providers and other providers processing user information on our behalf to be bound by terms prohibiting training, fine tuning, and model improvement using that information. We use model services only under terms limiting processing to inference and necessary service operations, including authorized debugging, security, abuse prevention, and legal compliance. None of those purposes permits model training or improvement. We require limits on provider retention and human access consistent with the permitted purposes and applicable law; not every permitted service operation requires zero retention.

We do not intentionally include seed phrases, private keys, API credentials, session secrets, access tokens, passwords, or other credentials in model context. Credentials belong in the applicable connection flow, not prompts, chats, uploads, or support messages. If you include secrets in ordinary content, they can enter the processing context; detection or removal cannot be guaranteed.

Any license in the Atlas Terms to process your content is limited by this policy. It does not override the prohibition on training or authorize publication of your private content.

When information is disclosed

We disclose information only to the extent necessary for the purposes described in this policy and subject to the applicable legal basis:

Operational providers. Hosting, storage, communications, support, security, diagnostics, and model providers receive information necessary for their contracted services. We require confidentiality, appropriate security, purpose and retention limits, assistance with privacy rights, and the prohibition on training. Providers acting as processors must follow our documented instructions and applicable requirements for any further processors.

Connected services and transaction infrastructure. Selected wallet providers, execution services, the covered integrations Polymarket, predict.fun, Hyperliquid, and Morpho, and the relevant blockchain networks receive wallet identifiers, transaction parameters, authorization or signing requests, and execution information necessary for authorized activity. Their role depends on the selected connection. A provider can process information on our behalf for one function and independently for another; we explain the relevant roles when you connect.

Rewards and yield services. Where enabled within the covered integrations, protocol interfaces, indexing or claim services, and fee collection infrastructure receive information necessary to carry out authorized activity. Public contracts and their participants can observe deposits, withdrawals, receipt token holdings, and fee transactions. Selecting a vault or allocation does not authorize disclosure of private strategies, chats, or complete account histories to its curator or allocator.

Payment and verification providers. We exchange necessary payment information to administer subscriptions and necessary verification information for a disclosed eligibility or legal requirement. We identify the selected providers and their roles at checkout or before verification. Independent processing is subject to their own notices; processing on our behalf is subject to our instructions and contractual restrictions.

Professional and legal recipients. Professional advisers, auditors, competent authorities, courts, or other necessary recipients can receive relevant information for advice, applicable legal duties, valid legal process, safety, fraud investigations, or establishing, exercising, or defending legal rights. We limit disclosures to what is legally required or otherwise necessary and lawful.

Business transactions. A prospective or actual merger, financing, restructuring, or transfer of a business or assets can require limited disclosure under confidentiality and purpose restrictions. We require continued protection of personal information and provide legally required notices. Such an event does not authorize model training, public disclosure of private content, or disregard of your rights.

Your specific direction. We can make a private disclosure to a recipient you specifically identify and authorize, subject to applicable law. General use of Atlas is not authorization to disclose information to unrelated recipients.

Authorized personnel may review relevant information for support, troubleshooting, security, compliance, meaningful review of an automated decision, or another documented operational need. We require access to be limited to that need. Support does not authorize unrestricted browsing of private strategies or chats.

Independent provider notices do not authorize Atlas to disclose unrelated information or override our restrictions on private content. You can obtain more specific information about recipients relevant to your use by contacting privacy@askatlas.gg.

Private content and public blockchains

Atlas does not publicly share your strategies or trading history, publish private chats or agent content, or operate public strategy or performance disclosures. The same protection applies to private reward and yield records. We do not authorize our service providers to publish that information.

Blockchain activity is different. Transactions submitted to a public blockchain can permanently expose addresses, amounts, asset movements, contract interactions, and timestamps. Others can analyze those records, link an address to you, or infer trading activity. Atlas cannot make public blockchain records private or erase copies maintained by independent participants.

An observable reward payment, fee transfer, bridge transaction, or deposit into an identifiable vault or fee arrangement can allow others to infer use of Atlas or a particular strategy. Our prohibitions on public sharing and model training protect private Atlas records; they cannot prevent independent analysis of public blockchain activity.

Cookies, analytics, and advertising choices

We do not sell personal information for money or other valuable consideration. We do not share personal information for advertising across unrelated services or contexts, use it for targeted behavioral advertising, or use behavioral advertising pixels.

We use cookies and local storage without optional consent only where strictly necessary and legally permitted for sessions, authentication, wallet connections, and security. These technologies can hold session or connection identifiers and security information. We use them only for the stated essential purposes, not to track browsing across unrelated services.

The following limits apply to browser storage:

Session storage and session cookies expire when the session ends.

Persistent authentication and wallet connection identifiers expire no later than 30 days after they are set or renewed, or earlier when the relevant authentication or authorization ends.

Security cookies and comparable security storage expire within 90 days after they are set.

Optional preference storage lasts no longer than 12 months.

Optional analytics identifiers, if offered and accepted, expire within 90 days after they are set.

Optional analytics, preference storage that is not strictly necessary, and optional offers require your affirmative consent before the relevant collection or use. At the point of choice, we identify the purpose, information involved, relevant provider or recipient, duration, and available controls. We make refusal and later withdrawal as easy as acceptance through the same channel. You can also contact privacy@askatlas.gg. Withdrawal stops future optional collection or use and leads to removal or expiry of associated optional identifiers within our control.

Atlas and operational providers receive essential storage information only for their respective necessary functions. Optional analytics providers, if used, receive only the information covered by your consent and our provider restrictions. Neither diagnostics nor consent to analytics authorizes model training or behavioral advertising.

Browser controls can also restrict cookies or remove local storage, although disabling essential technologies can affect authentication or connected functions. Browser storage expiry does not itself delete server records, which follow “Retention, disconnection, and deletion.” We honor Global Privacy Control and other valid universal preference signals where applicable law requires, even though we do not sell personal information or share it for behavioral advertising. Do Not Track signals are distinct from those legally recognized preference signals and are not treated as consent to optional processing.

Retention, disconnection, and deletion

We retain personal information only while necessary for a disclosed purpose. The limits below govern Atlas records and records held by processors on our behalf. A shorter period required by law or a valid exercise of privacy rights takes priority. A listed period is not a reason to retain information that is no longer needed.

Active account information and chats. We keep contact details, profile information, agent configuration, and chat history while needed to provide an active account or requested function. We delete routine profile, configuration, and chat information within 30 days after a valid account closure or deletion request. If a limited part is necessary as transaction or legal evidence, only that necessary part follows the relevant evidence period below.

Execution, authorization, rewards, and fee evidence. We retain necessary execution, reward, distribution, and fee evidence for up to six years after the relevant transaction. We retain necessary consent evidence for up to six years after the last use of the applicable consent, and necessary revocation or relationship evidence for up to six years after the relevant relationship ends. We keep only the records and limited excerpts needed to establish instructions, authority, amounts, outcomes, or legal rights, not entire chats simply because an instruction led to a transaction.

Billing and tax records. We retain necessary invoices, payment records, and tax documentation for up to seven years after the end of the relevant financial year.

Routine telemetry. We retain routine device, performance, and diagnostic records for no more than 90 days after collection.

Security logs. We retain security event and access logs for no more than 12 months after the event, except for specific information necessary for an active investigation or lawful hold.

Support records. We retain support correspondence and necessary attachments for no more than 24 months after the issue is resolved. A specific portion needed for a legal claim or another justified purpose follows the applicable period, rather than extending retention of the entire support history.

Credentials and secrets. We disable Atlas operational access when revocation becomes effective or the relevant connection or service ends. We delete stored credentials and secrets within 30 days after that event unless retaining a specific item is legally necessary. Any legally retained secret remains unavailable for ordinary operational use. Minimal evidence of authorization or revocation can be retained separately under the evidence period without preserving a usable credential.

Verification information. If Atlas receives verification document copies, we delete copies no longer needed within 30 days after verification is completed, unless a specific legal requirement or other legally justified necessity requires longer retention. We retain only a minimal verification result or status for up to six years after verification, and only where genuinely necessary for compliance or a dispute. We do not apply that period to document copies by default.

Backups. Deleted information can remain in restricted backups until those backups rotate, no later than 90 days after deletion from active systems. It is not available for ordinary use. If a backup is restored, we require the relevant deletions and restrictions to be reapplied before ordinary processing resumes.

If a legal requirement, specific dispute, investigation, or preservation obligation justifies longer retention, we isolate the necessary records, restrict their use, and document the basis. We review the continuing necessity at least annually. When the hold or other exception ends, we delete the retained information within 30 days if its ordinary retention period has expired. We do not retain information indefinitely merely because it might be useful.

We require processors to follow applicable deletion or expiry instructions and contractual retention limits for permitted service operations. Independent payment, wallet, verification, or trading providers can have their own lawful retention duties. Public blockchain records and copies held by independent participants are outside Atlas deletion control.

Disconnecting a wallet or service is not the same as deleting an account or revoking every permission. Provider access, API or session credentials, signing delegation, and blockchain contract approvals may need separate revocation through the relevant provider, wallet, or contract. Contact support@askatlas.gg for operational assistance and privacy@askatlas.gg for privacy requests.

Withdrawing consent, revoking access, requesting deletion, or closing an account does not reverse transactions already submitted or completed. Disabling a rewards or yield feature does not itself delete necessary records of fees, distributions, deposits, or permissions. Deleting an Atlas account does not redeem an external position.

International processing

Personal information may be processed in the United States, including by Atlas personnel and cloud or model services, and in your country. Provider and recipient locations depend on the connection and service selected. The restriction on US users does not mean that personal information is never processed in the United States. You can request the specific recipients and destination countries relevant to your information through privacy@askatlas.gg.

We will not make a transfer restricted by applicable privacy law unless a valid transfer mechanism and any other required conditions are in place. For transfers governed by the EU GDPR, we rely on a valid adequacy decision only within its applicable scope or use the European Commission's 2021 Standard Contractual Clauses with the applicable module. For restricted UK transfers, we use an applicable adequacy regulation, the UK Addendum to those clauses, or the UK International Data Transfer Agreement, as appropriate.

Where required, we assess the recipient, destination laws, and transfer risks and require supplementary contractual, technical, or organizational measures. If the relevant conditions cannot be satisfied, we will not make the restricted transfer. We also meet any applicable local requirements for separate consent, transfer notices, or data localization before the covered processing.

Contact privacy@askatlas.gg for information about the safeguards applicable to your information or a copy of the relevant safeguards, subject to lawful redactions protecting confidential information and others' rights. Using Atlas is not blanket consent to processing in another country.

Where a legally required regional representative is appointed, we provide its identity and contact details in the applicable regional notice before the covered processing begins.

Security

We require technical and organizational measures proportionate to the nature and risks of processing, including the sensitivity of private trading information and credentials that can authorize asset movements. These requirements include access limited by role and operational need, appropriate protection of information in storage and transit, controls over credential use, provider security obligations, and procedures for incident response and deletion. We assess safeguards for the processing involved rather than treating any connection as inherently without risk.

No system is completely secure. Report suspected unauthorized access or a security issue to support@askatlas.gg. We will investigate and provide notices to affected individuals and authorities within the periods required by applicable law. This policy does not waive security obligations, breach notification duties, or applicable remedies.

Your rights and choices

Depending on your location and applicable law, your rights include:

Confirmation of whether we process your personal information, access to that information, and details about its purposes, categories, sources, recipients, retention, and applicable safeguards.

Correction of inaccurate information and completion of incomplete information.

Deletion of information, restriction of its use, and receipt of a portable copy in an appropriate format where the legal conditions apply.

Objection to processing based on legitimate interests and objection to direct marketing. We stop direct marketing when you object. For other objections, we stop the covered processing unless a lawful ground permits it to continue.

Withdrawal of consent, without affecting the lawfulness of processing before withdrawal.

Applicable limits on uses or disclosures of sensitive personal information and applicable rights to opt out of sale, sharing, or targeted advertising, even though Atlas prohibits those advertising practices.

Information, human intervention, an opportunity to express your view, and a way to contest a qualifying automated decision as described in “Agent operation and automated decisions.”

These rights are not limited to account holders or waived by an eligibility restriction. To make a request, email privacy@askatlas.gg or write to the correspondence address in “Contact.” Describe your request and enough information to locate the relevant records. We verify identity in proportion to the request and risk, using only reasonably necessary information. A government identity document or full identity verification process is not automatically required. Authorized representatives can act where permitted, subject to proportionate checks of identity and authority.

We acknowledge requests within 10 business days, or sooner if applicable law requires. We respond within one calendar month after receipt, or within a shorter period required by law. If the complexity or number of requests justifies an extension and applicable law permits it, we may extend by up to two additional months. We will explain the reason and revised deadline within the first month, or sooner where required. We do not use an extension where local law does not permit it.

Requests are ordinarily free. If applicable law permits a fee or refusal for a particular request, we explain the legal basis, any proposed fee, and your available options. We explain any lawful refusal or limitation, including where retaining specific information is required by law or necessary to protect others' rights. The periods in “Retention, disconnection, and deletion” do not automatically override a deletion or other rights request.

You can ask us to reconsider a decision or exercise an applicable appeal right by emailing privacy@askatlas.gg and identifying the decision. We review the reasons and respond within one calendar month or any shorter legally required appeal period, explaining the outcome and further options. You may complain directly to the competent privacy regulator without first contacting us, including the relevant European supervisory authority or the UK Information Commissioner's Office where applicable. For European rights, this can include the authority where you habitually reside, work, or believe an infringement occurred.

We do not unlawfully discriminate against you for exercising privacy rights. Optional marketing messages include an unsubscribe method. Essential account, security, and transaction communications are separate from optional marketing.

Children and policy changes

Atlas is intended for adults aged 18 or older who meet any higher minimum age and other applicable eligibility requirements. It is not directed to children. If you believe a child has provided personal information, contact privacy@askatlas.gg. We will investigate and delete information collected contrary to applicable requirements, subject only to lawful, necessary retention.

We update the dates above when this policy changes and provide notice of material changes before they take effect where required. Where a change requires consent or another legal condition, posting an update or continued use alone does not satisfy that requirement. Changes do not retroactively authorize training on or public sharing of previously collected private user information.

Contact

For privacy questions, rights requests, appeals, transfer information, or an accessible version of this policy, email privacy@askatlas.gg.

For service assistance, billing questions, or security reports, email support@askatlas.gg.

For formal legal notices, email legal@askatlas.gg.

Postal correspondence: [LEGAL ENTITY NAME], Atlas Privacy, 276 Fifth Ave, Ste 704 PMB 137, New York, NY 10001, United States.

Referenced links

Atlas website. https://askatlas.gg