Privacy policy

This policy explains what Solved Telephony, LLC collects when you buy connectivity from us, what we collect as a by-product of carrying a call or a message, who we hand it to, how long we keep it, and what you can ask us to do about it.

Effective date: September 18, 2026. Last updated: September 18, 2026.

1. Introduction and scope

1.1. This Privacy Policy (this "Policy") is issued by Solved Telephony, LLC, a limited liability company organized under the laws of the State of Nevada ("Solved Telephony," "Company," "we," "us," or "our"). It describes how we collect, use, store, process, share, disclose, and protect information in connection with our voice connectivity, phone number inventory, SMS and MMS messaging, programmable call routing, hosted PBX, recording and transcription, AI Voice Agents, APIs, and the website at solvedtele.com (collectively, the "Service").

1.2. Solved Telephony is a wholesale telephony provider. Our customers are software platforms, dialers and contact centers, call tracking companies, CRM and vertical software vendors, and businesses that buy a phone system directly ("Customers"). Most of the traffic on our network is not ours. It belongs to a Customer, it is generated by that Customer's own users and the people those users call or message, and it crosses our network because the Customer told us to carry it.

1.3. This Policy applies to: Customers and the individuals who administer a Customer account ("Authorized Users"); visitors to solvedtele.com; people who contact us for sales, support, or careers; and, to the limited extent described in Section 2, the individuals on the other end of a call or message that we carry ("End Users"). Capitalized terms not defined here have the meanings given in our Terms of Service.

1.4. White-label use is normal on our network. When a Customer resells our connectivity under its own brand, the End User generally never sees the Solved Telephony name, and the privacy notice that governs that End User's relationship is the Customer's notice, not this one.

1.5. By creating an account, sending traffic, or using the Service, you acknowledge that you have read this Policy and our Terms of Service. If you do not agree with how we handle data, do not send traffic to us.

2. Our role: processor for traffic, controller for accounts

2.1. This is the most important distinction in this document. Our data footprint splits cleanly in two, and different rules apply to each half.

(a) Traffic data: we are a service provider and processor

2.2. When we originate, terminate, route, record, transcribe, or message on a Customer's behalf, we act as a service provider under California law and as a processor in the sense that term is used in other state privacy statutes. We process that data on the Customer's documented instructions and for the purpose of delivering the service the Customer bought. The Customer is the controller or business. The Customer decides who gets called, what is said, whether recording is on, how long media is kept, and what disclosures and consents are given to the people on the call.

2.3. In practical terms this means: we do not decide the purpose of a Customer's calling campaign; we do not build our own marketing profiles out of a Customer's call content; we do not sell Customer traffic data; and we do not use a Customer's call recordings, transcripts, or message content to market to the End Users on those calls.

(b) Account and website data: we are the controller

2.4. For the data we collect to run our own business, we are the controller. That includes account and registration data, billing records, support conversations, credit and fraud screening, and the ordinary analytics on solvedtele.com. We decide the purposes for that data and this Policy is the notice that governs it.

(c) What this means if you were called or texted

2.5. If you received a call or a message that crossed our network and you want to know why, or you want the data about you corrected or deleted, we are usually not the company that can answer you. The company that placed the call holds the record, the consent, and the decision. Section 11 explains how we route your request to that company and what we will and will not do ourselves.

(d) Where the roles overlap

2.6. Some obligations sit on us regardless of role because they are imposed on the carrier rather than on the carrier's customer. Emergency call handling, lawful intercept, industry traceback response, number administration, and the confidentiality rules that apply to customer proprietary network information are examples. Sections 6, 7, and 9 describe those obligations, and we will meet them even where a Customer would prefer we did not.

3. Information we collect

We collect the categories of information described below. Not every category applies to every account; several of them exist only because a Customer turned a feature on.

(a) Account and registration data

3.1. When a Customer opens an account we collect: legal entity name and any trade names; billing and service addresses; the names, business email addresses, business telephone numbers, and job titles of Authorized Users; login credentials, including usernames and hashed passwords; multi-factor authentication enrollment data; API keys and token metadata; account roles and permissions; tax identification and business registration details where required; and the information needed to screen an account for toll fraud risk and sanctions exposure before we open a path to the public telephone network.

(b) Device and technical data

3.2. When you use the portal, the API, or our website we automatically collect: Internet Protocol addresses; SIP user agent strings and softphone or PBX identifiers; browser type and version; operating system; device type; session identifiers and session timestamps; pages and endpoints requested; API request and response metadata, including rate limit and error records; and authentication events, including failed login attempts and the addresses they came from.

(c) Call detail records and signaling metadata

3.3. Carrying a call produces a record whether or not anyone asked for one, because the network has to know what it did in order to route it, bill it, and answer for it later. For every call leg we collect: the calling number and the called number; call direction; the trunk, sub-account, and route that carried the leg; the carrier or interconnect used; setup, ring, answer, and release timestamps; post-dial delay; talk duration and billable duration; SIP signaling data, including request and response codes, headers, and hangup cause codes; SIP Identity headers and the STIR/SHAKEN attestation level applied to the leg; codec negotiated and media path information; jitter, packet loss, and other quality measurements; queue, conference, transfer, and IVR events; DTMF capture events where a Customer's routing collects digits; and the rate that was applied to the leg.

3.4. Call detail records include information that United States telecommunications law treats as customer proprietary network information, meaning data about the quantity, technical configuration, type, destination, location, and amount of use of the service a Customer buys. We treat call detail records accordingly: access is restricted to the people who need it, access is logged, and we do not use them for marketing beyond the Customer relationship they came from.

(d) Call recording and transcription data, where the Customer enables it

3.5. Recording and transcription are optional network services. They are off unless a Customer turns them on, and the Customer chooses the scope: a whole account, a sub-account, a campaign, a queue, or an individual number. Where they are on we collect and store: audio recordings of the call, including conference recordings and voicemail; recording metadata, including start and end time, file size, duration, participants, and integrity hashes; transcripts produced from that audio, with speaker labels and confidence scores; and, where the Customer also enables them, redaction output, sentiment scores, and call summaries.

3.6. The content of a recorded conversation belongs to the Customer's relationship with the person on the call. We hold it as a processor. Section 8 sets out who is responsible for consent.

(e) SMS and MMS content and metadata

3.7. For messaging we collect: the sending and receiving numbers; direction; message body text and any attached media for MMS; segment counts; carrier delivery receipts and error codes; timestamps for submission, delivery, and failure; the campaign and brand registration the message was sent under; opt-out, opt-in, and help keyword events, including STOP, UNSTOP, and HELP handling; and the consent state we track at the number level so that a Customer's suppression instructions are honored across our network.

3.8. Message content passes through our systems because it has to in order to be delivered, and it is retained for the period described in Section 9 so that delivery can be proven and complaints answered. We do not read message bodies except as needed to deliver them, to operate spam and fraud controls, to respond to a carrier or regulator, or on a Customer's instruction.

(f) Number provisioning, porting, and CSR data

3.9. Provisioning and porting a number requires records about the number and the person or business it belongs to. We collect and process: the numbers searched, reserved, assigned, and released on an account; Letters of Authorization and the signatory information on them; customer service records and customer service record requests obtained from a losing carrier, which can include the account holder name, service address, and account number held at that carrier; port request identifiers, firm order commitment dates, rejection reasons, and cutover status; directory listing instructions; and the end-user name and address a Customer supplies for a number so that regulatory records about that number are accurate.

3.10. Porting data is shared with the carriers and number administration systems described in Section 6, because a port cannot happen without it.

(g) E911 registered location data

3.11. Where a Customer provisions Enhanced 911 on a number, we collect and maintain the registered location associated with that number: street address, unit or floor detail, city, state, and postal code, plus the callback number and the name to be presented. We validate that address against the databases that emergency call routing depends on, and we transmit it to the third-party 911 service providers and public safety answering points described in Section 6.

3.12. Registered location data is only as accurate as what the Customer or its End User provided. It is used for emergency call routing, for the regulatory records we are required to keep about it, and for nothing else.

(h) CNAM and directory data

3.13. We process caller ID name data in two directions. When a Customer sets a calling name for a number it owns, we write that name to the industry CNAM databases so other carriers can display it. When an inbound call arrives and CNAM lookup is enabled, we query a third-party CNAM database with the calling number and receive the name associated with it. We record that a lookup happened, so the query can be billed and audited. Directory listing and directory assistance requests are handled the same way, through the third-party databases that provide them.

(i) Billing data

3.14. We collect: usage records derived from call detail records, message records, and feature usage; prepaid balance, recharge, deduction, adjustment, and refund history; invoices, statements, and payment history; purchase order and billing contact details; tax exemption certificates and jurisdiction data used to calculate taxes and regulatory fees; and payment method information. Card and bank details are collected and stored by our third-party payment processor. We retain tokens and the last four digits, not full card or account numbers.

(j) Support and sales communications

3.15. When you contact us we keep the communication and what it was about: emails, support tickets, messages in a shared support channel, notes from calls with our engineers, packet captures and SIP traces produced to investigate a specific issue, demo and sales inquiry records, and newsletter subscription state. A trace or capture produced to debug your traffic can contain signaling for real calls, which is why it is handled under the same access restrictions as call detail records and deleted on the schedule in Section 9.

(k) Cookies on the marketing site only

3.16. Cookies and similar technologies are used on solvedtele.com and in the authenticated portal. In the portal they are limited to what makes a logged-in session work: authentication, session integrity, security, and interface preferences. We do not place advertising or cross-site tracking technology into the call path, into the API, or into a Customer's own product. Section 14 has the detail.

(l) Information we do not want

3.17. We do not ask for, and Customers should not send us, government identification numbers, payment card numbers, health information, or other sensitive categories of personal information in support tickets, contact forms, or free-text account fields. If you send us something we did not ask for and do not need, we will delete it.

4. How we use information

4.1. We use the information described above for the following purposes and for purposes compatible with the context in which we collected it:

• Delivering the Service. Originating, terminating, routing, and bridging calls; selecting and monitoring carrier routes; delivering and receiving messages; provisioning and porting numbers; running recording, transcription, conferencing, PBX, and AI Voice Agent features that a Customer has turned on.
• Emergency call handling. Routing 911 and E911 calls, transmitting registered location and callback information, and maintaining the records that emergency call routing requires.
• Network quality and operations. Measuring answer rates, post-dial delay, and media quality per route; withdrawing failing carrier paths; capacity planning; diagnosing a specific call or trunk when a Customer asks us to.
• Billing and collections. Rating usage, maintaining prepaid balances, producing invoices and usage exports, calculating taxes and regulatory fees, and pursuing unpaid amounts.
• Fraud, abuse, and toll fraud prevention. Detecting compromised credentials, traffic pumping and access stimulation patterns, artificially inflated traffic, robocalling patterns that draw complaints, message spam, and unusual destinations or volumes, and acting on what we find.
• Identity and attestation. Signing outbound calls under the STIR/SHAKEN framework at the attestation level the traffic has earned, which requires us to know which Customer originated a call and whether the calling number legitimately belongs to that Customer.
• Regulatory and legal obligations. Responding to industry traceback requests, regulator inquiries, and lawful process; meeting the record-keeping, number administration, and lawful intercept obligations that apply to us as a carrier.
• Support. Answering questions, working an incident, producing a trace, and keeping a history of what was already tried.
• Service improvement. Understanding how the API and portal are used so we can fix what is confusing and build what is missing. Where this involves traffic data we work from aggregated and de-identified measurements rather than the content of anyone's conversations.
• Our own marketing, to businesses. Sending product and rate updates and occasional newsletters to business contacts who asked for them, with an unsubscribe link in every one.
• Enforcing our agreements. Investigating suspected breach of the Terms of Service, suspending traffic, and resolving disputes.

4.2. Model training. We do not use Customer call recordings, transcripts, or message content to train general-purpose artificial intelligence or machine learning models for our own benefit or for other customers, unless the Customer has separately agreed in writing that we may. Where a Customer uses our AI Voice Agents or transcription features, the audio and text are processed to deliver that feature for that Customer, and any tuning of a Customer's own agent stays within that Customer's account. Aggregated, de-identified network measurements, such as route quality and error-code distributions, are used to operate and improve the network and do not contain conversation content.

4.3. What we do not do. We do not sell personal information. We do not share personal information for cross-context behavioral advertising. We do not use a Customer's traffic data to compete with that Customer or to market to that Customer's End Users.

5. Legal basis for processing

5.1. Where a legal basis framework applies to our processing, we rely on the following:

• Performance of a contract. Providing the Service to a Customer, administering the account, and billing for usage.
• Compliance with a legal obligation. Emergency call handling, lawful intercept, number administration, traceback response, tax and accounting records, and responses to lawful process.
• Legitimate interests. Network security and quality, fraud and toll fraud prevention, abuse and spam controls, service improvement from aggregated measurements, business-to-business marketing to contacts who have a relationship with us, and establishing or defending legal claims. We weigh these against the interests of the people whose data is involved and we limit the processing accordingly.
• Consent. Marketing email to contacts who opted in, non-essential cookies on our marketing site, and any processing we have asked you to agree to separately. You can withdraw consent at any time, and withdrawal does not affect processing that already happened lawfully.
• Customer instruction. For traffic data, our processing is grounded in the Customer's instruction and the Customer's own legal basis for the communication. It is the Customer's responsibility to have one.

6. Sharing and disclosure

6.1. Carrying a phone call is a multi-party act. A call cannot reach its destination without handing signaling data to another network, and several of the disclosures below are not optional for us. We share information with the following categories of recipients:

• Downstream and upstream carriers and interconnect partners. Calling and called numbers, SIP signaling, identity headers and attestation, and the technical data required to complete a call or deliver a message go to the carriers that terminate or originate the traffic. Different destinations use different carriers, and a call may traverse more than one.
• 911 service providers and public safety answering points. Registered location, callback number, and presented name are provisioned into the databases used for emergency call routing and are delivered to the answering point that takes the call.
• CNAM and directory database operators. Calling name records a Customer sets are written to industry CNAM databases so other carriers can display them. Lookup queries are sent to a third-party CNAM provider. Directory listing and directory assistance requests go to the operators that maintain those listings.
• Number administrators and porting counterparties. Number assignment, port requests, Letters of Authorization, and customer service record data are exchanged with number administration and pooling systems and with the losing or gaining carrier on a port. A port cannot be completed without this exchange.
• Messaging aggregators and registries. Brand and campaign registration data for 10DLC, and verification packets for toll-free messaging, are submitted to the registries and aggregators that authorize messaging traffic, along with the message traffic itself.
• Regulators and industry bodies responding to traceback. When an industry traceback request or a carrier complaint identifies traffic on our network, we identify the originating account and produce the relevant call records. Section 7 describes how this works and what we tell the Customer.
• Law enforcement and courts, under lawful process. We disclose information in response to a subpoena, court order, warrant, civil investigative demand, or other valid legal process, and where we reasonably believe disclosure is necessary to prevent imminent physical harm. We review what we receive, we produce the narrowest set of records that answers it, and we tell the affected Customer unless we are legally prohibited from doing so or unless doing so would defeat an emergency.
• Subprocessors and vendors. Cloud infrastructure and storage, media storage and delivery, speech recognition and large language model providers used to deliver transcription and AI Voice Agent features, payment processing, tax calculation, email delivery, error monitoring, and customer support tooling. Subprocessors are engaged under written terms that limit them to processing for us and are subject to security review before they touch Customer data. A current list is available to Customers on request at contact@solvedtele.com.
• Professional advisors and insurers. Counsel, auditors, accountants, and insurers, under confidentiality obligations, where they need the information for a legal, audit, or insurance matter.
• Affiliates. Our parent and sister companies within the Solved Ventures group, where an affiliate performs a function for us or is a Customer on the network in its own right. An affiliate that is a Customer is treated like any other Customer and gets no additional visibility into another Customer's traffic.
• A successor in a corporate transaction. In a merger, acquisition, financing, reorganization, or sale of assets, information may transfer to the acquiring entity, which remains bound by the commitments in this Policy for the data it receives until it provides notice of a different policy.
• With Customer direction or your consent. Where a Customer instructs us to send data to a named third party, such as a warehouse destination for CDR exports or a webhook endpoint, or where you have asked us to share something.

6.2. We do not sell personal information, and we do not disclose Customer traffic data to data brokers, advertising networks, or list vendors.

7. Lawful intercept, CALEA, and industry traceback

7.1. Lawful intercept. As a provider of telecommunications service we are subject to the Communications Assistance for Law Enforcement Act and the implementing rules under it. That means we maintain the capability to isolate and deliver communications and call-identifying information to a law enforcement agency when we are served with a valid court order or other lawful authorization, and to do so without alerting the subject of the order. We maintain internal procedures, designated personnel, and records for handling such requests, and we screen every request for legal validity before acting on it.

7.2. We cannot tell you about an intercept. Where an order prohibits disclosure, we will not tell the Customer, the End User, or anyone else that an interception is occurring. Nothing in this Policy or in a contract with us can require us to breach that prohibition. Where an order does not prohibit disclosure and no other legal constraint applies, we notify the affected Customer.

7.3. Industry traceback. The telephone industry operates a traceback process for identifying the origin of suspected illegal robocall traffic. When a traceback request or a carrier complaint reaches us, we identify which account originated the leg, and we produce the call detail record, the route, the attestation applied, and the recording where the Customer had recording enabled and it is responsive. We answer traceback from records rather than from memory, which is one of the reasons those records exist.

7.4. What traceback means for a Customer. We tell you when your traffic is the subject of a traceback and what we sent. Repeated or unresolved traceback activity, sustained complaint rates, or persistent illegal traffic will get an account's traffic suspended and, where it continues, disconnected. That obligation comes with holding carrier interconnects, and it is set out in our Terms of Service.

7.5. Regulatory record-keeping. We keep the records that federal and state telecommunications regulation requires us to keep, including records related to number assignment, emergency call handling, attestation and identity, and complaint response. Those retention obligations override a Customer's shorter retention preference for the specific records they cover.

7.6. Our security program, including how access to records and media is restricted and logged, is described on our security page.

8. Call recording, monitoring, and transcription

8.1. Recording is a feature, not a default. Recording and transcription run in the network, but they run only where a Customer has enabled them, at the scope the Customer chose. We do not record calls for our own purposes.

8.2. Who can hear a recording. Access to recordings and transcripts is restricted to the account and sub-account that owns the call and to the small number of our engineers who need it to work a specific issue. Playback links are time-limited signed URLs rather than permanent addresses. Access by our personnel is logged.

8.3. Third-party processing of audio. Transcription, redaction, sentiment scoring, summarization, and AI Voice Agent features send audio or text to the subprocessors described in Section 6. Those subprocessors are contractually limited to processing for us and are not permitted to use Customer audio or transcripts to train their own models except where we have configured the service so that they cannot, which is our default posture.

8.4. Redaction. Redaction of personal and payment data from transcripts is available at no additional charge. It is a control we recommend and a control the Customer has to turn on. It reduces exposure; it does not eliminate it, because redaction is automated and imperfect.

8.5. Deletion. Deleting a recording removes the media. The call detail record that references the call is a separate record on a separate schedule, because it is a billing and regulatory record. Section 9 explains both.

8.6. Rates, scope controls, and the operational detail of recording and transcription are on our recording and compliance page.

9. Data retention

9.1. We keep information for as long as we need it for the purpose it was collected, and then we delete it or de-identify it. Where a Customer sets a retention window, we honor it, except where a longer period is required by law or is necessary to resolve a dispute that is already open.

• Call detail records and signaling metadata. Retained for at least twenty-four months, and longer where a specific record is subject to a regulatory obligation, a traceback, a billing dispute, or legal process. CDRs are billing and regulatory records, so they survive the deletion of the media they reference and they are not deleted on request while a retention obligation applies to them.
• Call recordings and voicemail. Retained for the window the Customer configures on the account or sub-account. Where the Customer sets no window, our default is twelve months. Recordings under legal hold are retained until the hold lifts.
• Transcripts, summaries, and sentiment output. Retained on the same schedule as the recording they were produced from, and deleted with it.
• SMS and MMS content and metadata. Message metadata and delivery records are retained for at least twenty-four months for complaint response, carrier disputes, and regulatory inquiry. Message bodies and MMS media are retained for twelve months unless the Customer configures a shorter window or a longer one is required.
• Number provisioning, porting, and CSR data. Retained for the life of the number assignment on the account and for twenty-four months after it is released or ported away, because port disputes and number history questions arrive after the fact.
• E911 registered location data. Retained while the number is provisioned with E911 and for the period the applicable rules require afterward, so that a record of what location was registered at the time of a call exists.
• CNAM lookup records. The fact and billing record of a lookup is retained with the call detail record. We do not maintain a separate history of names returned.
• Account and registration data. Retained for the life of the account and for twenty-four months after closure, then deleted except where a longer period is required.
• Billing and financial records. Retained for seven years, as tax and accounting rules require.
• Support communications, traces, and packet captures. Support history is retained for thirty-six months. SIP traces and packet captures produced for a specific investigation are retained for ninety days and then deleted, because they contain signaling for real calls and there is no reason to keep them longer.
• Security and access logs. Retained for at least twelve months for incident investigation.
• Aggregated and de-identified network measurements. Retained indefinitely. These do not identify a Customer, an End User, or the content of a conversation.

9.2. Backups are retained on their own cycle and are overwritten in the ordinary course. Deleting a record from our active systems does not instantly remove it from backup media, and we do not restore a backup to delete a single record.

10. Security

10.1. Controls. We maintain administrative, technical, and physical safeguards appropriate to the sensitivity of what we hold. Those include: encryption of data in transit and at rest, with media and storage encryption on by default at no additional charge; per-trunk credentials and IP allowlists; role-based access control and sub-account isolation, so that a token scoped to one tenant cannot read another; multi-factor authentication for administrative access; toll fraud limits and destination controls; least-privilege, logged access to recordings and call records; vulnerability management and vendor security review; and a documented incident response process.

10.2. No completed audit. We do not hold a completed SOC 2 report or a HIPAA attestation, there is no named auditor behind this page, and there is no certificate to send you. Formal audit readiness work is underway, including control documentation, evidence collection, and access reviews. When that changes we will say so plainly and state the scope and period covered. What you can get today is a completed security questionnaire, a written description of the control set, and a conversation with the engineers who operate it. The full description is on our security page.

10.3. Breach notification. If we confirm an incident involving unauthorized acquisition of personal information that triggers notification obligations, we notify affected Customers without unreasonable delay, with what happened, what data was involved, what we have done, and what we recommend they do. Where we act as a processor, notice goes to the Customer so the Customer can meet its own obligations to its End Users. We notify regulators where the law requires it, including under Nevada's breach notification statute.

10.4. Limits. No network, no storage system, and no security program is impenetrable, and we do not claim otherwise. Our commitments are the controls we run and the way we respond when something goes wrong.

11. Customer and end-user rights

(a) If you are a Customer or an Authorized User

11.1. You can ask us to tell you what account, billing, and technical data we hold about you; correct it; delete it, subject to the retention obligations in Section 9; export it; and stop sending you marketing email. Most of this is self-service in the portal. For anything that is not, write to contact@solvedtele.com. We verify that a request comes from someone entitled to make it, and we respond within forty-five days, extending once with notice where a request is complex.

(b) If you were called or texted and want to exercise a right

11.2. This is the part people most often need. If a call or a message reached you and you want to know why, get the record corrected, be deleted, or be added to a suppression list, the company that placed the call is the one that can act. It holds the consent record, the list, the campaign, and the decision. We carried the traffic on its instruction.

11.3. What we will do: if you write to contact@solvedtele.com with the number that called or texted you, the number it reached, and the approximate date and time, we will identify the Customer that originated the traffic, route your request to that Customer, and tell you that we have done so. Where the law requires us as a service provider to assist the controller in responding, we assist. Where we hold data about you only as a processor, we will not unilaterally delete it out of a Customer's records, because doing so could destroy the very consent and suppression records that protect you.

11.4. What we will also do, on our own account: honor an opt-out you send to a number on our network through the standard keywords, so that the suppression state is recorded at the network level, and act on a complaint pattern under Section 7 if a Customer's traffic warrants it.

11.5. We will not charge you for any of this, and we will not treat you differently for asking.

(c) Nevada residents

11.6. Nevada law lets a resident submit a verified request directing an operator of a website or online service not to sell covered personal information. We do not sell personal information. Send a request with the subject line "Nevada privacy request" to contact@solvedtele.com and we will confirm that position in writing.

(d) California residents

11.7. Under the California Consumer Privacy Act as amended by the California Privacy Rights Act, a California resident has the right to know what personal information a business collects, uses, discloses, and sells about them; the right to delete it; the right to correct inaccurate information; the right to opt out of sale and of sharing for cross-context behavioral advertising; the right to limit the use of sensitive personal information; and the right not to be discriminated against for exercising any of these.

11.8. Two things shape how those rights work here. First, we do not sell personal information and we do not share it for cross-context behavioral advertising, so there is nothing to opt out of. Second, for traffic data we act as a service provider under the statute, which means requests about that data belong with the business that engaged us. We will route them as described above and assist the business as the statute requires. Much of the account-level information we hold also falls within the statute's business-to-business and employment-context provisions, since it describes people acting for a company rather than as consumers.

(e) Other state privacy laws

11.9. Residents of Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Tennessee, Indiana, Iowa, Delaware, New Hampshire, New Jersey, Nebraska, Kentucky, Maryland, Minnesota, Rhode Island, and other states with a comprehensive consumer privacy law may exercise the rights those laws give them, including access, correction, deletion, portability, and opting out of targeted advertising, sale, and certain profiling. Write to contact@solvedtele.com and tell us your state of residence. Where a state law gives you the right to appeal a refusal, our decision letter will tell you how.

(f) Authorized agents

11.10. You can use an authorized agent to submit a request. We will ask for proof that you authorized the agent and, where the law allows, we will verify your identity directly.

12. Children's privacy

12.1. The Service is a business product sold to businesses. It is not directed at children, we do not market it to children, and we do not knowingly collect personal information from anyone under the age of eighteen through our website, our portal, or our sales process.

12.2. Traffic is a different matter, and we are honest about the limits of what we can see. A Customer's calls and messages may reach any member of the public, and we have no way to know the age of the person on the other end of a leg we carry. A Customer that communicates with minors is responsible for the consent and legal requirements that apply to that, including the Children's Online Privacy Protection Act where it applies to the Customer's own service.

12.3. If you believe we hold personal information about a child under eighteen that we collected directly, write to contact@solvedtele.com and we will investigate and delete it.

13. International transfers

13.1. Solved Telephony operates from the United States. Our systems, our records, and our stored media are hosted in the United States, and our personnel and subprocessors that access them are located in the United States except where a specific subprocessor has support personnel elsewhere, in which case access is under written terms and the same restrictions.

13.2. If you access the Service or send us information from outside the United States, that information will be transferred to and processed in the United States, where privacy law differs from the law of your country and may give you fewer protections.

13.3. International calling is by its nature international. A call to a destination outside the United States requires us to hand calling and called number information, signaling, and identity data to a carrier in or serving that destination, and that carrier handles it under its own law. We do not control what a foreign carrier does with signaling we are required to give it in order to complete a call.

13.4. We do not currently offer a data residency option outside the United States, and this Policy does not represent that the Service complies with the data protection law of any jurisdiction other than the United States.

14. Cookies and tracking technologies

14.1. Marketing site. solvedtele.com uses a small set of cookies and similar technologies: strictly necessary cookies for security and load handling, preference cookies to remember display choices, and first-party analytics to understand which pages are read and where people get stuck. Analytics on the marketing site is configured to avoid collecting more than we need, and we do not run cross-site advertising pixels on it.

14.2. Portal. In the authenticated portal, cookies are limited to authentication, session integrity, security, and interface preference. These are strictly necessary; turning them off logs you out.

14.3. Not in the call path. There is no tracking technology in the SIP path, in the media path, in the API, or in messaging. Cookie consent has nothing to do with whether a call connects.

14.4. Your choices. Every current browser lets you block or delete cookies, and mobile operating systems offer similar controls. Blocking strictly necessary cookies will break the portal. Where a law requires consent before we set a non-essential cookie, we ask for it before setting it.

15. Do Not Track signals

15.1. Some browsers send a "Do Not Track" header. There is still no agreed standard for what a website must do in response, so we do not change our behavior based on that header alone, and we say so here rather than implying otherwise.

15.2. We do honor the Global Privacy Control signal on solvedtele.com as an opt-out of sale and of sharing for cross-context behavioral advertising, which is straightforward for us because we do neither. If the standards settle, we will follow them and update this section.

16. Changes to this policy

16.1. We update this Policy when our practices change, when we add a product that handles data differently, or when the law changes. The "Last updated" date at the top of the page reflects the most recent revision.

16.2. For a material change that affects how we handle Customer or traffic data, we give registered Customers at least thirty days' notice by email or in the portal before it takes effect. Continued use of the Service after the effective date means the revised Policy applies to you. If you do not accept a change, you can close your account before it takes effect.

16.3. A copy of a prior version is available on request at contact@solvedtele.com.

17. How to contact us

Privacy questions, data requests, and complaints all go to the same place, and a person reads them.

If you are unhappy with how we handled a privacy request, tell us and we will look at it again. You also retain the right to complain to your state attorney general or another regulator with authority over us.