Legal

Privacy Policy

How Phantm collects, uses, shares and protects personal information, and the choices you have.

Last updated

The short version

  • We do not sell personal information, and we do not use it for targeted advertising. Section 6
  • On the Self-serve plan, we keep prompts, responses and request records for as long as the business remains a Customer, with no fixed time limit, to run the Service and to train and improve Phantm's own routing. We never sell them or use them to train third-party or foundation models. This cannot be turned off on the Self-serve plan, and they cannot be deleted from the dashboard. Section 4.1
  • On the Enterprise plan, the Privacy option means we don't keep your prompts or responses. Zero data retention, including the measurement sample, is available by contract. Section 4.2
  • Your AI provider bills your own provider account. We store provider keys encrypted and gateway keys only as hashes, and we never see full card numbers. Section 4.4, Section 3.2
  • We host the Service in the United States (section 11). The service providers that help us, some of them based in other countries, are listed in this policy. Section 7
  • If you use a product built by one of our Customers, that Customer controls what it sends through Phantm. Send requests about your information to it, and we will help it respond. Section 2.3
  • To ask about your information, email support@getphantm.ai. A Customer's prompts and responses are erased only after our Terms with it end, for example when it asks us to end them and delete its data. Some records, and what our routing has learned, are kept after that. Section 12, Section 9

This summary is here to help you read the policy. It is not part of it; where it differs from the full text, the full text applies.

On this page 17 sections
  1. 1About this policy
  2. 2Whose data it is
  3. 3Information we collect
  4. 4How we handle Customer Content
  5. 5How we use information
  6. 6How we share information
  7. 7Service providers
  8. 8Cookies and similar technologies
  9. 9How long we keep information
  10. 10Security
  11. 11Where we process information
  12. 12Your choices and rights
  13. 13US state privacy rights
  14. 14EEA and UK privacy rights
  15. 15Children
  16. 16Changes to this policy
  17. 17Contact us

1About this policy#

Phantm, Inc. ("Phantm", "we", "us") is a Delaware corporation. We run an API gateway for AI model requests (the "Service"). A business points its AI software at Phantm, and we forward each request to the business's AI provider and work to lower what it costs. We also run the website at www.getphantm.ai and the dashboard at dashboard.getphantm.ai.

This policy explains what personal information we collect, how we use and share it, how long we keep it, and the choices and rights you have. It applies when you visit our website, try our demo, contact us, apply for a job, sign up, use the dashboard or the Service, or otherwise deal with us.

Some words have a set meaning in this policy:

Customer
A business that uses the Service and is billed for it.
Member
A person who signs in to the dashboard on behalf of a Customer.
End user
One of a Customer's own users, as identified on the requests the Customer sends through Phantm.
Customer Content
What a Customer sends through the Service and receives back: prompts, responses and anything in them.
Self-serve plan
The plan a business signs up for on its own from our website. Its data terms are the Collaborative data terms (section 4.1).
Enterprise plan
The plan we set up with a business under a signed agreement, with custom pricing. Its data terms are agreed in writing and include the Privacy option (section 4.2).

Other capitalized words, such as Savings fee, Billing period, Carried balance and Credit, have the meanings given in our Terms of Service, which a Customer accepts when it signs up and which govern use of the Service. A copy of the Terms is available from support@getphantm.ai. An Enterprise Customer's signed agreement sets its own data terms; where they differ from this policy, they govern that Customer's Customer Content.

2Whose data it is#

2.1Customer Content and request details#

A Customer decides what its requests contain and why it sends them. We process Customer Content, and the request details a Customer sends (such as End-user IDs), on the Customer's behalf to provide the Service. For that processing, the Customer is the controller (or "business") under privacy laws, and Phantm is its processor (or "service provider"). As its processor, we help the Customer respond to requests from its End users (section 2.3). A full data processing agreement is available on request (section 12).

2.2Improving our routing#

Under the Collaborative data terms, we also use Customer Content to improve Phantm's own routing and optimization, including to train our own routing models (section 4.1). For that use, we decide how the content is used, and we act as a controller. Our legal basis under the GDPR and UK GDPR is our legitimate interest in improving the Service, with the safeguards in section 4.1. Under US state privacy laws, we use it as a service provider, for the permitted purpose of building and improving the quality of our services, and never to provide services to anyone else with that personal information.

2.3If you are an End user#

If you use a product built by one of our Customers, that Customer controls what it sends through Phantm and is your first point of contact. Please send questions and requests about your information, such as a request to see or delete it, to that Customer. If you contact us instead, we will pass your request to the Customer, tell you we have done so, and help the Customer respond, as its service provider and processor. Where we act as a controller (section 2.2), we will also reply to you ourselves, as the law requires.

On the Self-serve plan, prompts and responses are kept until the Customer's data is erased, which happens only after our Terms with that Customer end (section 4.1).

2.4What Customers are responsible for#

Each Customer is responsible for giving its End users any notice the law requires, and for having the right to send their information through Phantm and to let us use it as this policy describes. On the Self-serve plan, that includes telling them that what they send is passed to Phantm, kept for as long as the business remains a Customer, and used to improve Phantm's own routing. Linking to this policy is one way to do this.

2.5Everything else#

For account, sign-in, billing, website, contact and job-application information, Phantm decides how and why it is used and is the controller. This policy is our notice for that information.

3Information we collect#

3.1Account and sign-in#

  • Sign-up details. Your email address and your company's name. If you sign up with an email address, you also choose a password, which we store only as a one-way hash, and we email you a 6-digit code to confirm the address.
  • GitHub or Google sign-in. If you sign up or sign in with GitHub or Google, the provider gives us your account ID, your email address and whether the provider has verified it. It also gives us a company hint: the company on your GitHub profile, your Google Workspace domain, or the domain of your email address. We use the hint only to suggest your company's name during sign-up. These providers may also send basic profile details, such as your name, which we do not keep. We never receive your password for those accounts.
  • Bot check. When you sign up with an email address, Cloudflare Turnstile checks your browser to tell people apart from automated sign-ups. Cloudflare collects information about your browser and device to do this, and we send it your IP address when we confirm the result.
  • Terms acceptance. When you accept our Terms, we record which version you accepted, when you accepted it, which Member accepted it and the IP address used.
  • Team. Each Member's email address and role (viewer, editor or admin). If an admin invites you, we receive your email address and role from that admin.
  • Account activity. Sign-ins and actions taken in the dashboard, such as signing up, linking a sign-in method, changing keys or inviting a teammate, with the time, IP address and browser type.

3.2Billing#

  • When a Customer adds a card, a page hosted by Stripe, our payment processor, collects it. For the Customer's first card, that page also collects the billing email and the company's legal name. Stripe holds the card details. We never receive full card numbers.
  • On the Self-serve plan, we charge the card on file automatically, through Stripe, for each 30-day Billing period, 48 hours after the period ends. A fee under $10 is carried into a later charge (Terms Section 7.4). Stripe emails a receipt for each charge to the billing email.
  • We keep the billing email, the legal name and any billing address we are given. We also keep each Billing period's statement, invoices, charges, Savings fee records, Carried balances, Credits, refunds, disputes (including disputes raised with a card issuer) and payment status, and a record of when the Customer authorized automatic charges to its card and the version of the wording it was shown.

3.3Using the Service#

  • Customer Content. The prompts a Customer sends and the responses it receives. What we keep depends on the Customer's plan (section 4).
  • Request details. For each request: the model requested and the model used, token counts, cost, latency, status and time, the gateway key used, and the user agent of the software that sent it. Also any tags the Customer adds, such as an End-user ID (the X-User-Id header), a feature, an environment, a request ID or a session ID. These details are personal information only where they identify a person, such as an End-user ID. We recommend that Customers send an internal ID rather than a name or email address.
  • Provider keys. The API keys a Customer gives us for its own AI provider accounts (section 4.4).
  • Prompt fingerprints. On every plan, keyed fingerprints of repeated sections of prompts, which contain no text, to help AI providers' prompt caches work.

3.4Our website, email, demo, forms and careers#

  • Contact forms. Your email address, and your message where a form asks for one. Web3Forms delivers these messages to us. If you book a call, Calendly collects the details you enter.
  • Job applications. Your name, email address, LinkedIn profile and a link to your resume, your GitHub profile where the role asks for it or you add it, and a note if you add one. Web3Forms delivers applications to us.
  • Email. If you email us, for example at support@getphantm.ai, we receive your email address and your message. Our email runs on Google Workspace.
  • Demo. The text you enter in the demo on our website. We send it to OpenAI, using Phantm's own account, to produce the result, and we do not save it to any account. We use your IP address to limit how often the demo can be used.
  • Technical information. Like any website, ours receives your IP address and browser details when you visit, through our hosting provider (Vercel). The services that supply our fonts (Google Fonts), our call-booking button (Calendly), and the page styles and icons on our home page (the Tailwind CSS CDN and Iconify) receive them too. We do not use analytics or advertising tools on our website.

3.5Information from other sources#

  • GitHub and Google, when you use them to sign in (section 3.1).
  • Cloudflare: the result of the bot check.
  • Stripe: whether a card is on file, the status of each payment, whether a card issuer asked the cardholder to approve a charge, refunds, and any dispute a cardholder raises with a card issuer.
  • AI providers: the response and token usage of each request, including the result of a request that finishes later, such as a background response, which we fetch with the Customer's provider key (section 4.4), and the results of the measurement sample and routing checks (section 4.3).
  • Your colleagues: an admin who invites you to the dashboard.

4How we handle Customer Content#

We offer two plans, Self-serve and Enterprise. What we keep depends on the plan:

Customer ContentSelf-serve planEnterprise, Privacy option
Prompt and response textKept with the request record, with no fixed time limit, for as long as the business remains a Customer; erased after our Terms with it end (section 12)Not kept
Request recordsFor as long as the business remains a CustomerMetadata only, for 30 days
Used to improve Phantm's routingYes, under the Collaborative data terms, with the safeguards in section 4.1No
Sold, or used to train third-party or foundation modelsNeverNever
Measurement sample (section 4.3)Applies. Kept in Phantm's own provider accounts with no fixed period, including after the Customer's data is erasedApplies, unless zero data retention is agreed by contract

4.1Self-serve plan: the Collaborative data terms#

Every Self-serve Customer accepts the Collaborative data terms when it accepts our Terms. Under them:

  • We store the text of each prompt and response with its request record for as long as the business remains a Customer. It is not deleted on a timer, and Members cannot delete it from the dashboard. We erase it once the final bill is settled after the Customer ends our Terms (its request to end them is also its instruction to erase), or 90 days after we end our Terms with the Customer, or once the final bill is settled if that is later (section 12).
  • We use it to run, secure and support the Service. For example, we use it to show the Customer its request history, to look into a request a Customer asks us about, or to fix a problem.
  • We also use it to improve Phantm's own routing and optimization. For example, we use it to test and train the internal models that decide how Phantm handles a request. We do not use it to build a profile of, or make decisions about, any person.
  • What our routing has learned from it is kept after the Customer's data is erased. That includes trained models, rules and statistics, and the records the routing was trained on, which can contain the text of prompts (section 9). We never use any of it to reveal Customer Content to anyone.
  • We never sell it. We never use it to train third-party or foundation models, and we never give it to anyone else to do so.
  • Apart from sending each request to the AI provider the Customer chose, we share it only with the service providers that help us run the Service (section 7), and with others only as section 6 describes.
  • Every Member of the Customer can see it in the dashboard (section 6.1). At Phantm, only staff who need it to run, support or improve the Service can access it.
  • At least once a year, we review whether we still need the Customer Content we keep, and erase or de-identify what we no longer need.

The Collaborative data terms cannot be turned off on the Self-serve plan. A Customer that needs us not to keep its prompts and responses should ask us about the Enterprise plan.

4.2Enterprise plan: the Privacy option#

Enterprise Customers sign a separate agreement that sets their data terms in writing, including a data processing agreement and retention periods. With the Privacy option:

  • We don't keep the text of prompts or responses. Request records hold metadata only (the request details in section 3.3), and we keep them for 30 days.
  • Usage and billing records, including the savings measured on each request, are kept as section 9 describes.
  • Zero data retention, including the measurement sample (section 4.3), is available by contract.

An Enterprise Customer can start with a Benchmark on its own traffic. During a Benchmark, its requests go to its AI provider unchanged while we measure, at our own expense, what we would have saved. To do that, we send an optimized copy of each request to the same AI provider from Phantm's own account. The records we keep for a Benchmark, and for how long, are agreed in writing.

4.3The measurement sample#

To verify savings, Phantm sends a sample of requests from its own accounts to the AI provider's batch service, and keeps those copies in those accounts so the measurement can be audited. The copies have no fixed retention period and are kept after a Customer's data is erased (section 9). When our routing model is unsure about a request, Phantm may also send it, from its own account, to the same AI provider to check its routing choice.

4.4Provider keys and gateway keys#

  • Provider keys. Customers bring their own keys for OpenAI, Anthropic or DeepSeek, and the provider bills model usage to the Customer's own account. When a Customer saves a key, we check it with the provider. We store the Customer's current provider key encrypted, and use it only to send that Customer's requests. That includes requests to retrieve, cancel or delete what those requests created, and fetching the result and usage of a Customer's request that finishes later, such as a background response, so we can record and bill it. We never use a Customer's key for our own requests or for anyone else. A replaced key is kept encrypted, and never used again, until the Customer's data is erased. Keys are write-only: the dashboard shows only the provider and the last four characters.
  • Gateway keys. These are the keys a Customer's software uses to call Phantm. Each one is shown once, when it is created, and we store it only as a hash. We keep the hashes of revoked keys too, so that past requests can still be traced to the key that sent them.

4.5Data that must not be sent#

Customers must not send protected health information, payment card data or other data that needs special legal protection through the Service, unless we have agreed to it in writing. On the Self-serve plan, they also must not send personal information about children under 16, or content from a product or service directed to children. Our Terms of Service set out the details.

5How we use information#

We use personal information for the purposes below. The last column gives the legal basis we rely on under the GDPR and UK GDPR, for people in the European Economic Area and the United Kingdom.

PurposeExamplesLegal basis (EEA and UK)
Provide the ServiceCreate and run accounts, sign Members in, forward and optimize requests, and show usage and savings in the dashboard.Our contract with you, or with the Customer you act for. Our legitimate interest in providing the Service.
Measure savings and billCalculate Verified Savings, run the measurement sample, issue statements and invoices, charge the card on file after each Billing period ends, apply Credits and make refunds, and handle billing disputes and disputes raised with card issuers.Contract. Legal obligation, for tax and accounting records. Our legitimate interests in collecting what we are owed and responding to payment disputes.
CommunicateSend service emails (sign-up codes, invitations, password resets, billing reminders and notices), answer support requests and messages, and tell our team when a new Customer signs up so we can offer help.Contract. Legitimate interests in running and supporting the Service.
Keep the Service secureRun bot checks and rate limits, keep records of account activity, and investigate and prevent misuse and fraud.Legitimate interests in protecting Phantm, our Customers and their End users. Legal obligation.
Improve the ServiceImprove our routing and optimization, including by evaluating and training our own models with Customer Content under the Collaborative data terms (section 4.1).Our legitimate interest in improving the Service, with the safeguards in section 4.1. You have the right to object to it (section 14). The Customer authorizes this use of its Customer Content in the Collaborative data terms, and is responsible for telling its End users about it (section 2.4).
HireReview job applications and contact applicants.Steps you ask us to take before a possible contract. Our legitimate interest in hiring.
Meet legal dutiesComply with law, respond to lawful requests, enforce our agreements and defend legal claims.Legal obligation. Legitimate interests.
With your consentAnything else we ask your permission for.Consent, which you can withdraw at any time.

We do not make decisions about individuals based solely on automated processing that have legal or similarly significant effects on them.

6How we share information#

6.1Who we share it with#

We share personal information only as follows:

  • Service providers. Companies that process information for us, for example for hosting, payments, email, sign-in and savings measurement. Section 7 lists each one, what it does, the information it handles and where it is based.
  • Card networks and banks. When a payment is disputed with a card issuer, or a card issuer asks about a charge, we share through Stripe the records needed to respond, such as invoices, statements, usage records, the record of the Customer's acceptance of our Terms and of its card authorization, and the Customer's contact details.
  • Within a Customer's account. Every Member of a Customer, whatever their role, can see that Customer's account information, such as request records (including stored prompt and response text on the Self-serve plan) and savings. Admins can also see the Customer's Members and their roles.
  • Advisers. Our lawyers, accountants and auditors, under a duty of confidentiality.
  • Legal and safety reasons. Authorities or others, when the law requires it, or when we need to protect the rights, property or safety of Phantm, our Customers or others.
  • Business transfers. A buyer or successor, as part of a merger, acquisition, financing or sale of assets.
  • With consent. Anyone else, when you ask us to or agree to it.

6.2AI providers#

Each request goes to the AI provider the Customer called (OpenAI, Anthropic or DeepSeek), through the Customer's own provider account and under the Customer's own agreement with that provider. That agreement governs what the provider does with the request. We may answer a request with a different, lower-cost model from the same provider, but we never send it to a different provider.

Separately, we use Phantm's own accounts with AI providers for the measurement sample and routing checks (section 4.3) and for Benchmarks (section 4.2), and our own OpenAI account for the demo on our website. For those, the AI provider is our service provider (section 7).

6.3No selling or targeted advertising#

We do not sell personal information. We do not share it for cross-context behavioral advertising, and we do not use it for targeted advertising.

7Service providers#

These companies process personal information for us. The table shows what each one does for us, the information it handles and where it is based. For Amazon Web Services, it also gives the regions we use. "Worldwide network" means the company serves content from locations around the world.

ProviderWhat it doesInformationLocation
Amazon Web ServicesHosting, databases, storage and content delivery for the Service and the dashboardEverything the Service stores, such as account details and request recordsUnited States: us‑east‑1, with encrypted backups in a second US region
StripePayments, invoices, receipts and billing detailsCard details, which Stripe collects itself; billing email; the company's legal name; invoice amounts, charges, Credits, refunds and payment disputesUnited States
ResendAccount emails: sign-up codes, invitations, password resets and billing remindersRecipients' email addresses and the email contentUnited States
Google WorkspaceHosting our email. Messages to support@getphantm.ai are forwarded to our staff mailboxes thereEmails you send us and our repliesUnited States
SentryError monitoring for the Service and the dashboardError reports, with keys, passwords, prompts and responses removedUnited States
Cloudflare (Turnstile)Checking that email sign-ups come from a person, not a botIP address and browser details of a person signing up by emailUnited States; worldwide network
GitHubSign-in, for people who choose GitHubAccount ID, email address and whether it is verified, profile companyUnited States
GoogleSign-in, for people who choose GoogleAccount ID, email address and whether it is verified, Workspace domainUnited States
OpenAIVerifying savings, checking routing choices when our routing model is unsure (section 4.3), Benchmarks and the demo on our website, from Phantm's own accountA sample of Customer requests; optimized copies of requests during a Benchmark; demo textUnited States
AnthropicVerifying savings, checking routing choices when our routing model is unsure (section 4.3) and Benchmarks, from Phantm's own accountA sample of Customer requests; optimized copies of requests during a BenchmarkUnited States
DeepSeekBenchmarks for Customers that use DeepSeek, from Phantm's own accountOptimized copies of requests during a BenchmarkChina
VercelHosting our website, getphantm.aiVisitors' IP addresses and browser detailsUnited States; worldwide network
CalendlyBooking calls with usDetails entered when booking, such as name and email address; IP address and browser detailsUnited States
Web3FormsDelivering website messages and job applications to usWhat each form containsIndia; servers in the United States
Google FontsServing the fonts our website usesVisitors' IP addresses and browser detailsUnited States; worldwide network
Tailwind CSSServing page styles on our home pageVisitors' IP addresses and browser detailsUnited States
IconifyServing the icons on our home pageVisitors' IP addresses and browser detailsEstonia

We use OpenAI, Anthropic and DeepSeek as service providers only when we call them from Phantm's own accounts (section 6.2). A Customer's own requests go to the AI provider it chose, through its own provider account and under its own agreement with that provider.

We update this list on this page when it changes, and change the Last updated date at the top. If a new service provider will handle Customer Content, we add it here before it starts. To be emailed about changes, or to ask for our full data processing agreement, email support@getphantm.ai.

8Cookies and similar technologies#

  • Essential cookies. The dashboard uses cookies to keep Members signed in and to secure sign-in with GitHub or Google. It also uses browser storage to remember preferences, such as light or dark mode. The Service cannot work without these.
  • No advertising or analytics cookies. We do not use them on our website or in the dashboard.
  • Third-party tools. Calendly, when you open the booking window, and Cloudflare Turnstile, when you sign up with an email address, may set their own cookies or read information from your browser under their own policies. Calendly may collect information about your online activity over time and across websites.
  • Browser signals. Our website does not respond to "Do Not Track" signals. Because we do not sell or share personal information, there is nothing for a Global Privacy Control signal to opt you out of. Where the law requires it, we treat that signal as an opt-out request.

9How long we keep information#

We keep personal information only as long as we need it for the purposes in this policy. These are our retention periods:

InformationHow long we keep it
Request records on the Self-serve plan, including prompt and response textFor as long as the business remains a Customer, with no fixed time limit, to run the Service and to improve our routing. The prompt and response text is erased once the final bill is settled after the Customer ends our Terms, or 90 days after we end our Terms with the Customer (or once the final bill is settled, if later); the rest of each record is kept as a usage record (section 12). We review at least once a year whether we still need them.
Request records under the Enterprise Privacy option (metadata only)30 days from the request, then deleted.
Measurement sampleKept in Phantm's own accounts with the AI provider's batch service, so the measurement can be audited (section 4.3). No fixed period, and kept after the Customer's data is erased.
What our routing has learned from Customer Content: trained models, rules and statistics, and the records it was trained on, which can contain the text of promptsKept after the Customer's data is erased, for as long as we use them to build and check our routing. We review at least once a year whether we still need them.
Benchmark recordsAs agreed in writing with the Enterprise Customer.
Usage and billing records, including the savings measured on each request (End-user ID, models, token counts and costs), statements, invoices, charges, Savings fee, Carried balance, Credit, refund, dispute and payment recordsAs long as we need them to bill, support Customers, resolve disputes and meet tax, accounting and other legal obligations, including after the Customer's data is erased.
Record of a Customer's authorization to charge its cardFor as long as the authorization lasts, and then as long as we need it to answer billing questions and disputes with card issuers.
Account and Member details, sign-in methodsUntil the Customer's data is erased (section 12). A Member can unlink GitHub or Google at any time in Settings. A removed Member's email address stays in the Customer's records until then.
Unfinished email sign-ups (email address, password hash, code hash)Deleted within 2 days. The sign-up code expires after 15 minutes.
GitHub or Google sign-up details, including the company hint, before sign-up is finishedUp to 30 minutes.
Provider keysThe current key, until it is replaced. A replaced key is kept encrypted, and never used again, until the Customer's data is erased.
Gateway key hashes, including revoked keysUntil the Customer's data is erased.
Prompt fingerprints (no text)Up to 30 days after the prompt section was last seen.
Terms acceptance recordsAs long as we need them to show what was agreed, including after the Customer's data is erased.
Records of account activity (actions, times, IP addresses)As long as we need them for security, fraud prevention and compliance, including after the Customer's data is erased.
Service and security logsUp to 15 months.
Demo textNot saved. The usage limits tied to your IP address expire within 2 days.
Website messages, emails to us and call bookingsAs long as we need them to reply and follow up.
Job applicationsAs long as we need them to consider you for the role and similar roles, unless you ask us to delete them sooner.
BackupsEncrypted backups expire automatically. Information we erase or delete can remain in a backup for up to 120 days afterwards. We use backups only to restore the Service.

When a Customer's data is erased (section 12), we erase its Customer Content from our live systems, together with its Members and their sign-in methods, its keys and its billing details, and we email to confirm when it is done. We keep:

  • usage, billing and savings records, records of account activity, and the records of the Terms the Customer accepted and of its card authorization, for as long as we need them to bill, resolve disputes, meet legal obligations, keep the Service secure and enforce our agreements;
  • the measurement sample in Phantm's own provider accounts (section 4.3); and
  • what our routing has learned from Customer Content, including the records it was trained on, which can contain the text of prompts. We never use any of it to reveal Customer Content to anyone.

We may also keep aggregated or de-identified information that no longer identifies any person or Customer, and we will not try to re-identify it.

10Security#

  • Connections to the Service are encrypted with TLS. Our databases, cache and backups are encrypted at rest. Provider keys are encrypted separately. Passwords and gateway keys are stored only as hashes.
  • Access controls keep each Customer's data separate. Phantm staff get access only where their role requires it, and we keep records of sensitive account actions.
  • Our security controls are described in our Trust Center.
  • If a security incident affects a Customer's data, we will notify that Customer without undue delay, and in any case within 72 hours after we become aware of it. We will also notify individuals and authorities where the law requires.

No system is perfectly secure. Please keep your password and keys safe, and email support@getphantm.ai if you think your account has been misused.

11Where we process information#

Phantm is based in the United States. We host the Service on Amazon Web Services in the United States (us-east-1), with encrypted backups in a second US region. Some of our service providers are based in, or process information in, other countries (section 7).

If you are outside the United States, your information will be transferred to the United States and processed there. Privacy laws there may differ from those where you live. Where the law requires a safeguard for these transfers, we rely on an approved mechanism, such as the standard contractual clauses approved by the European Commission and the UK addendum to them.

12Your choices and rights#

  • In the dashboard. Members can manage their own sign-in methods. Admins can manage teammates, keys and the card on file.
  • Emails. Service emails, such as sign-up codes, billing notices and security messages, are part of the Service. If we send you marketing email, each one will include a way to unsubscribe.
  • Ending our Terms and erasing a Customer's data. On the Self-serve plan, a Customer's prompts, responses and request records are kept for as long as the business remains a Customer, and Members cannot delete them from the dashboard. They are erased only after our Terms with the Customer end. For a Customer to end our Terms and have its data erased, an admin Member emails support@getphantm.ai from the address they sign in with. Before acting, we confirm that the request comes from the Customer. We then stop the Service and charge the final bill. Once the final bill is settled, our operators erase the Customer's prompts and responses, its Members and their sign-in methods, its keys and its billing details, and we email to confirm when erasure is done. We keep the records that section 9 lists. If we end our Terms with a Customer ourselves, we erase the same data 90 days after they end, or once the final bill is settled if that is later. An Enterprise Customer's data is kept and deleted as its signed agreement provides.
  • If you are or were a Member. You can ask us to access, correct or delete your own personal information, such as your email address and sign-in methods, whether or not your company is still a Customer. Email support@getphantm.ai from the address on your account, with "Privacy request" in the subject line, and we will respond as the law requires. We keep records of actions you took in the dashboard, and the record of our Terms if you accepted them for your company, because we need them for security and to show what was agreed. These can include your email address.
  • If you are an End user. A Customer decides what it sends through Phantm about you, so please send requests about Customer Content to that Customer. If you contact us instead, we will pass your request to the Customer and help it respond, as section 2.3 describes.
  • Privacy requests. Depending on where you live, you may have the rights described in sections 13 and 14. To use them, email support@getphantm.ai. We will confirm your identity, usually by checking that you control the email address on the account. We acknowledge each request within 10 business days, and respond within one month if you are in the EEA or the UK, or within 45 days elsewhere. Where the law allows us more time, we will tell you why and when to expect a response. You may use an authorized agent; we may ask the agent for proof of your permission. If we decline a request, we will tell you why and how to appeal or complain (sections 13 and 14).
  • Data processing agreement. A full data processing agreement covering personal information in Customer Content is available on request from support@getphantm.ai.

We will not treat you differently for using your privacy rights.

13US state privacy rights#

13.1Your rights#

Residents of California and several other US states have rights over their personal information. Depending on your state, you may ask us to:

  • tell you what personal information we have collected about you, and give you a copy;
  • correct information that is wrong;
  • delete your information;
  • stop selling or sharing your information, or using it for targeted advertising or profiling. We do none of these;
  • limit our use of sensitive personal information. We use it only to provide the Service, as the law permits.

If we decline your request, you can appeal by replying to our decision. If we deny the appeal, you can contact your state attorney general.

13.2Notice for California residents#

In the past 12 months, we collected the categories of personal information below. The sources are described in section 3, the purposes in section 5 and how long we keep each kind in section 9. We disclose each category for business purposes to our service providers (section 7), and to the others listed in section 6. We have not sold or shared personal information, and we do not knowingly sell or share the information of anyone under 16.

CategoryExamples
IdentifiersName, email address, IP address, GitHub or Google account ID, and End-user IDs that Customers send.
Customer records and commercial informationCompany name and legal name, billing email and address, statements, invoices, charges, Savings fee, Carried balances, Credits, refunds, disputes, payment status and the record of a card authorization.
Internet or other electronic network activitySign-ins, actions in the dashboard, browser type, request details and website visits.
Professional or employment informationA Member's role on an account. Job application details.
Sensitive personal informationAccount sign-in details (email address and password, stored as a hash). We use them only to sign you in and protect your account.
Other information in Customer ContentWhatever a Customer sends through the Service. We process it as the Customer's service provider, including for the permitted purpose of building and improving the quality of our services under the Collaborative data terms (section 2), and never to provide services to anyone else with it. On the Self-serve plan, we keep it for as long as the business remains a Customer (section 9).

14EEA and UK privacy rights#

If you are in the European Economic Area or the United Kingdom, Phantm, Inc. is the controller of your account, sign-in, billing, website, contact and job-application information. For Customer Content, the Customer is the controller, except for our own use of it to improve our routing, where we are (section 2). Please send requests about Customer Content to the Customer first (section 2.3). The legal bases we rely on are in section 5.

You have the right to:

  • access your personal information and get a copy of it;
  • have it corrected or deleted;
  • restrict how we use it, or object to our use of it, including use based on our legitimate interests;
  • receive it in a portable format;
  • withdraw consent at any time, without affecting what we did before you withdrew it;
  • complain to your local data protection authority. In the UK, that is the Information Commissioner's Office.

We need your email address to create an account. Without it, we cannot provide the Service. Section 11 explains how we transfer information to the United States.

15Children#

The Service and our website are for businesses and are not directed to children. We do not knowingly collect personal information from anyone under 16. On the Self-serve plan, our Terms do not allow Customers to send personal information about children under 16, or content from a product or service directed to children, through the Service.

If you believe a child has given us personal information directly, for example through our website, email support@getphantm.ai and we will delete it. If you believe a Customer has sent a child's information through the Service, please tell that Customer, or email us and we will pass your message on to it (section 2.3).

16Changes to this policy#

We may update this policy. We will post the new version on this page with a new Last updated date. If a change materially affects how we handle Customer Content, or personal information we have already collected, we will tell Customers by email or in the dashboard at least 30 days before it takes effect, and ask for consent where the law requires it.

17Contact us#

Company
Phantm, Inc.
A Delaware corporation
Email
support@getphantm.ai
Questions and privacy requests. For a privacy request, put "Privacy request" in the subject line.