Privacy Policy
Last updated 6 November 2026
This notice explains how Use Fluency, Inc. and Farmor Software Pty Ltd handle personal information in running Fluency's business and providing its services. It also explains the different responsibilities that apply when we process workforce information on a customer's instructions. The regional rights provisions below apply where the relevant law covers the processing.
Privacy at a glance
- Who is responsible: Use Fluency, Inc. is the US customer contracting entity. Farmor Software Pty Ltd is the Australian operating company. The responsible controller for a business activity is identified in the next section. For customer workforce information, the customer normally decides the purposes and Fluency processes the information on its instructions.
- What we use: Business contact and account information, recruitment and personnel records, website information, and information processed through customer deployments. Customer platform information can include screenshots, work events, application names, window titles, URLs, identifiers and derived work information.
- Why we use it: To answer enquiries, administer relationships and accounts, provide support, manage recruitment and payments, secure our systems, operate our website and provide the customer-configured service.
- Who can receive it: Authorised personnel, the relevant customer, group service companies and service providers for the relevant purpose. Appendix A identifies customer platform providers, including AI processing providers, their functions and processing locations. Website technologies are described in the Cookie Policy.
- Where and how long: Fluency operates in the United States and Australia, with customer storage deployments in Australia, the United States and Singapore. Other processing locations and transfer arrangements are identified below and in Appendix A. Retention depends on the record, purpose, law and applicable customer instructions. Seven-day raw-image expiry does not apply to every other record or copy.
- Security and choices: We use access controls, encryption and other safeguards appropriate to the system, including configurable capture exclusions and redaction. These controls reduce risk but do not guarantee that all personal information is removed. Contact privacy@usefluency.com to ask a question or exercise a right. For an EEA or UK request, we normally respond within one month, subject to the lawful exceptions explained below.
Who is responsible for your information
In this notice, "we" means the Fluency entity responsible for the activity concerned. The two operating companies have the following contact details:
Use Fluency, Inc.
1475 Folsom Street, San Francisco, CA 94103, United States.
Farmor Software Pty Ltd
ACN 667 892 855. Business correspondence: 36-38 Gipps Street, Collingwood, VIC 3066, Australia.
Our privacy contact for both entities is privacy@usefluency.com. Luke de Castro, Operations Lead, is our Privacy Officer. You may also contact support@usefluency.com, which will route privacy enquiries to the privacy team.
Our business activities as a controller
A controller decides why and how personal information is used. The responsible entity depends on the relationship and activity:
Administration of a customer contract, business relationship, account, payment or support enquiry with Use Fluency, Inc.
Responsible controller: Use Fluency, Inc.
Administration of a customer contract, business relationship, account, payment or support enquiry with Farmor Software Pty Ltd
Responsible controller: Farmor Software Pty Ltd
Operation of usefluency.com and its general website enquiries, analytics and marketing technologies
Responsible controller: Farmor Software Pty Ltd
Recruitment and employment or contractor administration
Responsible controller: The entity identified as the prospective employer, employer or engaging company in the vacancy, offer, employment agreement, contractor agreement or separate personnel notice. This is Use Fluency, Inc. for its engagements and Farmor Software Pty Ltd for its engagements.
Security, legal compliance and administration of each entity's own business systems and records
Responsible controller: The entity responsible for the relevant business system, obligation or relationship. This does not change the processor role for customer-controlled content.
Each entity is responsible for the controller activities allocated to it above. Being members of the same corporate group does not itself make the entities joint controllers. For customer-controlled information, the processor roles below apply.
Customer workforce information
For workforce activity processed through the Fluency platform on a customer's instructions, the customer is normally the controller. It decides why it uses Fluency, the people and workflows in scope and its lawful basis, and must explain that use in its own privacy information, including any employment-law requirements.
The Fluency entity that contracts to process that information acts as a processor under the customer's processing agreement and documented instructions. Where Use Fluency, Inc. is the contracting processor and Farmor Software Pty Ltd operates the platform on its behalf, Farmor Software's role is governed by the applicable subprocessing arrangements. Where Farmor Software Pty Ltd contracts directly with the customer, it is the customer's processor for that service. This operational processing does not give us an independent right to use customer workforce information for our own purposes.
If a request concerns information captured for your employer or another customer organisation, contact that organisation's privacy team first. If you contact us, we will route the request to the relevant controller and assist under its instructions. We will verify authority before disclosing records and will not disclose another organisation's information to an unverified requester.
Information we collect and where it comes from
The information depends on your relationship with us. We do not collect every category about every person.
Business contacts and accounts: Names, work contact details, employer, role, account identifiers, correspondence and service-use information. We receive these from you, your organisation, related companies and the business systems used for the relationship.
Applicants and personnel: Contact details, applications, CVs, qualifications, work history, interview notes, references and information necessary for an employment or contractor engagement, including payment and administration details. Sources include you, nominated referees and authorised recruitment, payroll or other personnel providers.
Website visitors: Device and browser information, IP addresses, cookie or similar identifiers, pages and events, form submissions and information generated by enabled analytics, session-replay or advertising technologies. The Cookie Policy describes the technologies and choices that apply.
Customer platform information: Screenshots and image content, work events, application names, window titles, URLs, paths, identifiers and derived work or process information from the customer deployment. Screen content can include information about people who do not use Fluency, including a customer's customers, patients, clients or counterparties.
We collect information directly, from a person's organisation, from providers and related companies and, for relevant business or recruitment purposes, from publicly available professional information. Where applicable law requires us to give information about an indirect collection, we provide it within the required period.
Why we use information and our lawful bases
For our controller activities covered by EU or UK data protection law, the lawful basis depends on the purpose and your relationship with the responsible entity. We use contract as a basis only where processing is necessary for a contract with the individual, or steps the individual requests before entering a contract. A commercial agreement with an individual's employer does not by itself supply that individual's contract basis.
Enquiries and business relationships: We use business contact details and correspondence to answer requests, arrange demonstrations and manage relationships. Our legitimate interests are communicating with people who ask about or use our services and administering business relationships.
Accounts and support: We use account information, communications and relevant diagnostics to provide and support the service. The basis is contract where the individual is a party, or legitimate interests in administering and supporting the organisation's service. Customer content remains subject to processor instructions.
Billing and financial administration: We use contact, subscription and payment-related information to administer payments and records. We rely on contract where applicable, legitimate interests in payment and business administration, and legal obligations where an applicable law requires reporting or retention.
Recruitment and personnel administration: We use applications, interviews and references to assess candidates and take requested steps towards an engagement. We use contract and legal obligations for necessary employment or engagement administration, and legitimate interests where applicable for fair recruitment and protecting the business. Keeping an unsuccessful candidate's details for future opportunities beyond the ordinary recruitment period requires their agreement.
Security and compliance: We use identity, access, device and event information to protect accounts and systems, investigate incidents and maintain compliance records. Our legitimate interests are preventing misuse and protecting people and information. Particular records may also be required by a statutory duty.
Website operation and optional technologies: Necessary technologies support essential functionality and record privacy choices. Optional analytics, session replay and advertising operate according to the regional settings and choices described in the Cookie Policy. Where consent is required, we obtain it before enabling the relevant technology.
Business marketing: We use relevant business contact information for permitted business communications based on our legitimate interest in explaining our services, subject to applicable electronic-marketing rules. Where consent is required, we obtain it. You can object or unsubscribe at any time, and we keep enough information to respect that choice.
You may ask us to explain our legitimate interests and object to processing based on them. Where consent is the basis, you may withdraw it without affecting earlier lawful processing. If necessary account, contract or billing information is not provided, we may be unable to supply the requested service or complete a transaction. We will explain any applicable statutory requirement when it arises.
Customer platform information and sensitive records
Fluency processes activity within the customer's configured deployment to reconstruct work, identify process opportunities and support customer-authorised automations. Screenshots and associated metadata can contain personal information both before and after processing. Exclusions and redaction reduce exposure but do not guarantee removal of every identifier or sensitive item, or make every resulting record anonymous.
The customer must define permitted workflows, applications, observation periods and exclusions. People should use the agreed pause and reporting routes when working with information that should not be captured. The supported controls and their behaviour depend on the software and deployment configuration, which the customer must assess for its use.
Screen content can incidentally contain health information, religious beliefs, trade-union membership or other special categories of personal data. Criminal-offence information is subject to additional restrictions. The customer must assess the processing and establish the required lawful basis, additional legal condition, permissions and safeguards. A platform participation agreement does not itself establish valid GDPR consent for employee monitoring, and redaction alone does not establish the necessary legal conditions.
Customer agreements and instructions determine permitted uses, including restrictions on model training and use for other purposes. Appendix A identifies the AI processing providers used for customer platform processing.
Children
Our website and services are intended for professional and organisational use and are not directed at children. We do not seek children as website or account users.
Customer-controlled records can incidentally include information about children or other people who are not platform users. That information remains subject to the customer's instructions, applicable legal requirements and the deployment's capture and exclusion rules. If you believe information about a child has been collected inappropriately, contact privacy@usefluency.com or the responsible customer's privacy team so the matter can be assessed and addressed.
Who receives information
We share information for the relevant purpose, under applicable agreements and law. Access is restricted to authorised people who need it, including relevant personnel of the customer and Fluency service providers where their role requires access.
Recipients can include group operating companies; cloud and application infrastructure providers; AI processing providers; identity and security services; support and communications services; recruitment and payroll providers; payment and accounting providers; and professional advisers, auditors and insurers.
Corporate activities use providers such as Microsoft 365, Ashby, Rippling, Stripe, Xero and AWS for their respective services. Website technologies include the providers identified in the Cookie Policy. Appendix A forms part of this notice and identifies the customer platform providers and subprocessors, including AI providers, their purposes, data categories and processing locations.
We may also disclose information where required by law, to protect legal rights or safety, or in a proposed business transaction subject to appropriate restrictions. Customer subprocessor authorisation and notice terms continue to apply to information processed on the customer's behalf.
International processing and safeguards
Fluency operates in the United States and Australia. Customer platform storage deployments include Australia, the United States and Singapore. Some model, gateway, support and diagnostic services process information globally, including outside those three countries, as described in Appendix A. Selecting a storage region does not itself limit those separate services to that country.
The recipients and locations for customer platform processing are set out in Appendix A and the applicable customer processing arrangements. Website providers and their processing arrangements are described in the Cookie Policy. The customer agreement and authorised configuration determine which platform routes may be used for a particular deployment.
Where EU or UK personal data is subject to restricted-transfer requirements, the transfer must have an applicable legal mechanism. This can be an adequacy decision covering the recipient and transfer, or an appropriate safeguard such as the European Commission's Standard Contractual Clauses and, for UK transfers, the UK International Data Transfer Addendum, with the necessary assessment and supplementary measures. The applicable mechanism must cover the receiving legal entity, service and transfer.
Appendix A identifies the relevant transfer arrangements for customer platform recipients. You may ask privacy@usefluency.com for the countries, recipients, applicable safeguard and a copy of the relevant transfer terms for your information, subject to proportionate redaction to protect other people and confidential information. For customer-controlled records we coordinate with the controller.
How long information is kept
We retain information for the relevant purpose, applicable legal duties and the period necessary to establish or defend legal claims. We apply the rule to the relevant records and do not use a legal hold as a reason to retain unrelated information.
Our controller records
- Employment and contractor records are ordinarily kept for seven years after the engagement ends, subject to applicable law and a properly scoped legal hold.
- Unsuccessful recruitment records are ordinarily kept for twelve months after the hiring decision, unless the candidate agrees to a longer talent-pool period or a legal obligation requires particular records.
- Closed support tickets are ordinarily kept for twenty-four months after closure, unless a contract, dispute or legal obligation requires a different period.
- Security, system and network logs for our own business are ordinarily kept for one year; vulnerability scan results for six months, subject to the particular system and a justified incident or legal hold.
- Business relationship records are kept while the relationship is active and afterwards only where needed for outstanding transactions, contractual obligations, complaints, record-keeping duties or legal claims. When the relevant matter or duty ends, records are deleted or de-identified unless another documented purpose still applies.
- Marketing suppression details are kept as needed to honour an objection or unsubscribe. They are not used to restart marketing to someone who has objected.
- Website analytics and session replay have separate retention rules. The PostHog website project has a configured event-retention period of seven years. Expired events may remain longer because the provider does not guarantee immediate deletion on expiry. Person profiles and their properties remain until deleted; the event-retention setting does not remove them. The current session-replay setting is ninety days for new recordings. Older recordings retain the period in effect when they were captured, and deletion is not immediate on expiry. The Cookie Policy gives the rules for other website technologies. Browser cookie or local-storage expiry does not itself delete server-side events, profiles or recordings.
Customer platform records
Customer platform retention follows the applicable agreement and documented instructions, including any stricter customer deadline. The configured raw-image stores use seven-day lifecycle expiry. Expiry is asynchronous and is not a guarantee that every copy disappears at an exact hour.
Processed images, metadata, derived information, platform logs and backups are separate records. They are not all covered by the raw-image period. The retention criteria are the purpose for which the customer authorised the record, its instructions, the applicable contractual deletion or return requirement and any justified legal restriction. Personal information in a derived record remains subject to those requirements. There is no single automatic retention period applying to every processed image, derived record, log or backup.
The following retention schedules apply to the specified record classes and stores. They do not apply to every copy of customer information:
| Record class | Retention period or expiry rule |
|---|---|
| Temporary server outputs | One day in the temporary-output store. |
| Generated PDF and Word files | Ninety days in the generated-output prefix. |
| Dagster compute-log objects | Thirty days in the compute-log prefix. |
| Primary application CloudWatch logs | Three hundred and sixty-five days for the nine primary application log groups. This does not describe every database, proxy or archive log. |
| RDS database backups | Thirty days for the shared production database backups. |
| DynamoDB backups | Thirty days for the DynamoDB backups covered by this schedule. |
| Redis backups | Seven days for the Redis backups covered by this schedule. |
| Deleted S3 object versions | No more than thirty days where the version-cleanup rule applies. This does not set expiry for current archive objects. |
| EFS recovery points | Thirty-five days under the recovery-point lifecycle. |
Other platform logs, telemetry archives and database copies remain subject to the relevant purpose, customer instructions and applicable contractual deletion requirement. They are not covered by the one-year primary application log setting or a uniform thirty-day backup rule. An expiry setting for deleted object versions does not delete a current object.
When a customer requests deletion or the service ends, the applicable processing agreement determines the records to return or delete and the deadline. A customer can obtain the schedule relevant to its deployment through its privacy or service contact. We assist the controller with individual requests under those arrangements.
Backups follow the applicable class-specific expiry cycle and access restrictions. Information awaiting backup expiry must remain restricted and must not be returned to ordinary use to defeat a valid deletion instruction. If a backup is restored, applicable deletion instructions must be reapplied before the affected records resume ordinary processing. Where information must be retained by law or for a valid legal hold, we restrict its use to that reason and remove it when the reason ends.
Security and accuracy
Our safeguards include encryption for supported transfers and stored information, identity and access controls, access restrictions based on role and need, secure system configuration, security monitoring and incident-response procedures. For customer capture, exclusions and redaction are intended to minimise unnecessary personal information, subject to the configured deployment and their technical limits.
Security assurance information, including the scope and reporting period of our SOC 2 report, is available through our customer security-review process.
The measures appropriate to a record depend on the system and risks involved. Please report suspected privacy or security issues promptly to privacy@usefluency.com or support@usefluency.com. Nothing in this notice excludes or restricts an individual's statutory data-protection rights or a liability that cannot lawfully be excluded.
Please tell us if your contact or account information is inaccurate. Derived work analysis can contain errors and should be checked before it is relied on. A customer must assess the accuracy, fairness and appropriateness of an output used in a decision about a person.
Cookies and website choices
Our Cookie Policy explains the website technologies, their providers, purposes, durations, regional settings and the choices available through Cookie preferences in the website footer.
For visitors in the EEA, the United Kingdom and Switzerland, optional analytics, marketing and session replay require opt-in. For visitors in the United States and Australia, usage analytics can operate by default, while marketing technologies and session replay remain off until enabled. The Cookie Policy and preferences panel explain the settings applicable in other regions.
You can change or withdraw your choices in Cookie preferences at any time. You can also use browser controls to limit cookies, although disabling necessary technologies can affect essential functionality. We do not treat a decision to use the website as consent to every optional technology.
PostHog website analytics and session replay
We use PostHog US Cloud, hosted in the United States, to measure website use and investigate usability and performance problems. This is website analytics, separate from the workforce information processed in customer deployments.
PostHog can receive browser and device information, page and interaction events, identifiers and IP addresses. The website project is not configured to discard client IP addresses from events. Automatic capture of website interactions and web-performance measurements is enabled, subject to the website choices described above.
Where session replay is enabled for a visit, it can reconstruct page interactions and include page text and images. The configured masking setting masks input fields but does not mask all page text or images. Browser console logs and network-request timings can accompany a recording. Capture of network headers and request or response bodies is disabled, as is canvas capture. These settings do not make every recording or event anonymous.
The retention rules for events, person profiles and recordings are stated in How long information is kept above. You can change or withdraw your choices through Cookie preferences. This does not automatically erase records already held by PostHog. You may contact privacy@usefluency.com about access, deletion or another applicable right.
Your rights and requests
The rights available depend on the law that applies, the information and our role. You can ask questions or make a request at privacy@usefluency.com. Identify the relevant relationship or customer organisation and the right you wish to exercise. We may ask for proportionate information to verify your identity and authority.
EEA and United Kingdom
Subject to the applicable conditions and exemptions, you may request access, correction, erasure or restriction of processing. You may object to processing based on legitimate interests, including profiling on that basis. You have an unconditional right to object to direct marketing. Where processing is based on consent or contract and carried out by automated means, data portability may apply.
You may withdraw consent at any time without affecting earlier lawful processing. You also have protections relating to solely automated decisions producing legal or similarly significant effects. Fluency's work analysis is intended to support human judgement. A customer's separate use of outputs to make decisions about people must be explained and assessed by that customer.
We respond within the applicable statutory period, normally one month. If a lawful extension or exception applies, we explain it. Requests are normally free. Any charge or refusal must be justified under applicable EU or UK law.
You may complain directly to a competent supervisory authority, including the authority in the EEA country where you live or work or where the alleged infringement occurred. In the United Kingdom you may contact the Information Commissioner's Office at ico.org.uk. You do not have to complain to us first.
Australia and other applicable rights
Where the Australian Privacy Act applies, you may seek access to and correction of personal information using the contact details above, subject to the applicable exceptions and identity checks. Any fee for an Australian access request must be permitted by the law applying to that request.
We take privacy complaints seriously. Give us enough information to understand and assess the matter. If you are dissatisfied with the outcome, you may contact the Office of the Australian Information Commissioner at oaic.gov.au. These Australian procedures do not limit the separate EEA and UK rights described above. We also honour rights provided by other laws where those laws apply to our processing.
EU and UK representative contacts
You can use the following contacts for enquiries concerning our Article 27 representation:
European Union
Instant EU GDPR Representative Ltd, Adam Brogden.
Office 2, 12A Lower Main Street, Lucan, Co. Dublin, K78 X5P8, Ireland.
Email: contact@gdprlocal.com. Telephone: +353 1 554 9700.
United Kingdom
GDPR Local Ltd, Adam Brogden.
1st Floor Front Suite, 27-29 North Street, Brighton, England, BN1 1EB, United Kingdom.
Email: contact@gdprlocal.com. Telephone: +44 1772 217800.
You may always contact privacy@usefluency.com directly. Using a representative does not restrict your right to contact a supervisory authority.
Changes to this notice
We keep this privacy notice under regular review to make sure it is accurate and up to date. We provide an updated notice as required when purposes, recipients or other material privacy information changes. The date above identifies this version. Changes to this notice do not override a customer agreement or remove an individual's statutory rights.
Appendix A Service providers and subprocessors
This appendix forms part of this notice. It identifies platform services and optional model and search routes. The customer agreement, authorised configuration and enabled feature determine which optional providers receive a particular customer's information. An optional route is not necessarily active for every customer. The locations below distinguish regional hosting from the broader processing permitted for global services. They are not a promise that every service stays in a customer's selected storage country.
Platform infrastructure and operational services
Amazon Web Services
Purpose and information involved: Customer storage, compute, databases, backups and logs. Data can include captured content, work-event metadata, derived records and relevant account or diagnostics information.
Processing locations and scope: Platform deployments in Sydney, Australia; Singapore; and US East, United States. Separate model, support and provider-control-plane locations are not determined by the storage region.
Anyscale
Purpose and information involved: Management of customer-data compute on Fluency-owned AWS and hosted control-plane and operational metadata.
Processing locations and scope: Customer-data compute in the Australian and US AWS deployments; hosted control plane and operational metadata in the United States. Application-log ingestion is disabled for these Australian and US deployments. Authorised temporary support access is separate from the location of the compute.
Vercel AI Gateway
Purpose and information involved: Model-request routing. Requests can include prompts, images, work information and metadata, depending on the feature.
Processing locations and scope: Vercel's primary processing facilities are in the United States, with processing also possible wherever Vercel or its subprocessors operate. Global gateway routing can use model-provider locations outside Australia, Singapore and the United States.
Datadog
Purpose and information involved: Operational metrics and application-performance diagnostics, potentially including diagnostic identifiers.
Processing locations and scope: Datadog US5 service in the United States. Support access and additional processing locations depend on the applicable service.
Sentry
Purpose and information involved: Error reporting and diagnostics, potentially including error context, logs and attachments containing personal information.
Processing locations and scope: United States region for Fluency's Business account. Collection depends on project and scrubbing settings.
Nango Cloud
Purpose and information involved: Optional integration services, connection management, proxied requests and associated logs. Sync functions are disabled; connection and proxy functions are separate.
Processing locations and scope: United States AWS hosting. Enabled integrations and onward processing depend on the customer configuration.
Stigg
Purpose and information involved: Subscription, entitlement and usage administration, including relevant account and metering information.
Processing locations and scope: United States hosting in Ohio with Oregon failover; CDN replication in the United States, Germany and Mumbai, India.
AI model and search routes
The following providers are available through specific features or configured model and search routes. Only providers selected for an enabled feature receive the information sent through that feature. Model requests can include prompts, images or files, work information and metadata. Search tools can receive the queries and context sent to them.
Google and Google Vertex AI
Role: Configured model routes. Google video and file processing are separate direct paths.
Processing locations and scope: Global routes are not limited to the customer storage country. Subject to service-specific location commitments, Google's processing terms permit processing in countries where Google or its subprocessors maintain facilities. The routing options include global, US and Australian presets; selecting one service's storage region does not restrict every Google feature to that country.
Amazon Bedrock
Role: Configured model route, including use of a Bedrock key.
Processing locations and scope: Service and route dependent. The customer's AWS storage region does not establish the location of the model request.
Anthropic
Role: Gateway options and separate direct model-processing paths.
Processing locations and scope: For its direct commercial services, Anthropic describes US data storage and processing in selected countries in the United States, Europe, Asia and Australia, unless otherwise agreed. Gateway or third-party-hosted models follow the applicable hosting and routing arrangements.
OpenAI
Role: Gateway options and separate direct model-processing paths.
Processing locations and scope: United States and other provider locations under the applicable service and processing arrangements. The Farmor Software DPA provides for OpenAI Ireland's processing of EEA/Swiss-origin data and protected onward transfers; this is not an exclusive Ireland or US residency promise.
Fireworks
Role: Configured model option, including use of a Fireworks key.
Processing locations and scope: Processing countries depend on the route; no fixed country restriction is specified for this optional service.
Thinking Machines
Role: Optional model-provider route.
Processing locations and scope: Use depends on the enabled feature and selected route. No fixed processing-country restriction is specified for this optional service.
Perplexity
Role: Search or tool recipient where that functionality is enabled.
Processing locations and scope: Processing countries depend on the query route and service; no fixed country restriction is specified for this optional service.
Global services may process information outside Australia, Singapore and the United States. Provider location information includes Google's subprocessors, Anthropic's commercial processing locations and Vercel's processing arrangements. A provider's permitted locations are not a statement that every listed location receives every request. Customer-specific restrictions continue to govern which services and routes may be used. You may request deployment-specific transfer information at privacy@usefluency.com.
Transfer agreements
AWS incorporates the European Commission's 2021 Standard Contractual Clauses into its Service Terms for relevant transfers to countries without an applicable adequacy decision. Its UK GDPR Addendum incorporates the corresponding UK transfer terms. These provisions apply automatically to relevant customer transfers using AWS services.
Farmor Software Pty Ltd's signed Anthropic Commercial Terms and DPA, dated 21 January 2025, incorporate EU Standard Contractual Clauses and the UK International Data Transfer Addendum. Its signed OpenAI DPA, dated 15 January 2025, includes EEA/Swiss onward-transfer provisions and EU Standard Contractual Clauses with the UK Addendum for relevant UK transfers.
Transfer protections depend on the contracting parties, service and transfer concerned. These agreements do not extend automatically to a different provider account, gateway or contracting entity. You may request the safeguard and relevant transfer terms for your information through the privacy contact above.