Foro
Privacy Policy
Foro.live Privacy Policy
Glen Strand Corporation | Version 1.0
Effective date: October 25, 2026
1 Who is responsible
This Policy explains how Glen Strand Corporation, a Washington corporation operating Foro.live, handles personal information relating to our website, application, APIs and services. Our address is 8201 164th Ave NE #200, Redmond, WA 98052, United States. Contact support@ryarc.com for privacy enquiries.
Foro is a business platform connecting advertising buyers with companies operating advertising networks. Those Network Operators are responsible for their own advertising sales and data practices. The physical venue and the Network Operator may be different businesses.
Glen Strand determines the purposes of processing for its own account administration, security, billing, compliance and permitted product analysis. For personal information processed solely on a customer’s instructions, that customer may be the controller and Glen Strand its processor or service provider. The relevant data processing agreement governs that activity where required. This Policy does not replace such an agreement.
This Policy describes our practices; it does not require individuals to waive privacy rights or treat their acceptance of our Terms as blanket consent.
2 Information we collect and its sources
Account and business information. We collect names, business names, email addresses, account roles, billing addresses and information supplied when registering, administering an organisation or contacting support. An employer, Network Operator or other authorised administrator may supply account information about its users.
Commercial records and content. We hold campaign and booking details, transaction and billing records, uploaded advertising media and related operational information. These may contain personal information supplied by customers, agencies or their authorised users.
Constitutions and customer-agent messages. Customers can store, edit and update a “Constitution” containing general instructions for their chosen AI. We also store messages an AI leaves for customers and messages customers leave for their AI within Foro. We do not receive or retain the user’s full external AI conversation history merely because an assistant is connected. These stored items may contain personal information or confidential business instructions.
Technical and security information. We collect IP addresses, authentication and access information, browser or device information needed to operate the service, errors and technical logs. Booking and transaction records exist separately from the stored customer-agent messages; we do not describe these as a transcript of every AI interaction.
Payment information. Stripe processes payment-card details. Foro does not store full card numbers or card security codes. We receive transaction status and billing or payment references needed for reconciliation, account administration and support.
Delivery and audience information. We receive player-level reports, audience estimates and aggregate impression counts from Network Operators or third-party measurement systems. Foro does not itself collect viewer camera footage, facial data, mobile identifiers or profiles of individual screen viewers. These reports are not independently verified proof that a person saw an advertisement.
3 How we use information
We use personal information to create and administer accounts; authenticate users and apply permissions; support inventory, bookings, payments and credit controls; transmit authorised media and instructions; communicate operational information; provide support; investigate delivery and payment disputes; maintain security; diagnose faults; prevent misuse; and comply with legal obligations.
We also process information to create anonymised data for analysis and product development as described in section 5. Authorised staff and contractors may access stored Constitutions and customer-agent messages when necessary for support, security, dispute resolution or that permitted analysis and anonymisation.
Information required to operate an account, authenticate a user, complete a booking or meet a legal requirement must be provided for the corresponding function to work. Optional information should be limited to what you need for your chosen workflows.
4 Customer selected AI connections
You choose whether to connect an external AI provider and which provider to use. Within your permissions and enabled workflows, that connection can allow the provider to receive your Constitution, customer-agent messages and relevant account, inventory or transaction information.
External AI providers you select handle information under their own terms and privacy policies. Review those terms, including their retention and model-training practices. Foro does not grant those providers an additional right to use identifiable customer data for their own model training.
Revoking a connection stops future authorised access once effective. It does not recall information already received by the provider, cancel existing bookings or necessarily delete copies held under that provider’s rules.
Private instructions and messages are available only to authorised users in the relevant account or organisation, authorised AI connections and authorised Foro personnel or contractors for the purposes described here. They are not published to unrelated customers.
5 Anonymised analysis and AI model development
We reserve the right to create and use anonymised versions of agent behaviour, transaction outcomes, Constitutions and stored customer-agent messages. This includes the contents of instructions and messages, not only usage statistics. We use the resulting material for analytics, research, benchmarking, product development and training, evaluating and improving Foro’s own AI models and services.
We address identifiers and identifying context within free text as well as account fields. Replacing a name with an identifier is not, by itself, anonymisation. Information that can reasonably be linked to an individual remains personal information and continues to be protected under this Policy and applicable law.
We may use third-party AI or analysis providers to process anonymised material for Foro under contracts restricting them to our purposes and prohibiting independent reuse, including training their own models. We do not use this permission to publish identifiable customer confidential information.
We do not attempt to re-identify anonymised material and require recipients acting for us to observe the same restriction. Lawfully anonymised datasets, insights and models may be retained after account closure. Personal information used in preparing those datasets remains subject to applicable lawful-basis, retention and rights requirements until effectively anonymised.
Where law requires consent for a particular processing activity, we obtain it before that activity. The contractual permission to use anonymised material does not eliminate that requirement or override a customer data processing agreement.
6 Legal bases where required
Where applicable law requires a lawful basis, we process information to perform a contract with you where you are personally a party, to meet legal obligations, or for legitimate interests that are not overridden by your rights. For business representatives who are not personally contracting, account and service administration generally relies on legitimate interests rather than a contract with that individual.
Our relevant interests include operating and securing a business advertising platform, facilitating authorised transactions, supporting customers, resolving disputes and improving our services through appropriately protected analysis. We assess necessity and privacy impacts before relying on legitimate interests for anonymisation or product analysis.
We rely on consent where the law requires it and allow its withdrawal for future processing. Processing carried out before withdrawal remains subject to the legal basis that applied at that time. Where we act solely as a processor, we follow the customer’s lawful instructions and applicable agreement.
7 Who receives information
Authorised users and transaction counterparties. Organisation administrators can access information consistent with their roles. Network Operators, Buyers and authorised agencies receive the information needed to negotiate, fulfil and administer their transactions. An organisation’s administrators may manage users, access and records within that organisation.
Service providers. We use Microsoft Azure for hosting and infrastructure and Stripe for payment processing. Providers supporting our operations receive information needed for their services, subject to appropriate contractual and security restrictions. Third-party providers analysing anonymised material are subject to section 5.
Personnel and advisers. Authorised staff, contractors and professional advisers may receive information where necessary for support, security, legal, accounting or other purposes described in this Policy, under confidentiality and access restrictions.
Legal requirements and business changes. We may disclose information where legally required, to establish or defend legal claims, or as reasonably necessary to address fraud or security threats. In a merger, acquisition or business transfer, relevant information may be disclosed under appropriate confidentiality protections and transferred subject to applicable law and notice requirements.
We do not sell personal information or share it with third parties for their own advertising or cross-context behavioural advertising. Customer-authorised AI connections and operational service-provider disclosures are described separately above.
8 Cookies and similar technologies
Foro uses cookies and similar storage for functions such as authentication, security, session operation and application preferences. We use Azure operational monitoring to maintain and troubleshoot the service.
We do not use advertising trackers or session-recording tools. Browser settings can restrict storage, but blocking essential technologies may prevent sign-in or other functions. If we introduce optional tracking that requires consent, we will provide the required notice and choice before activating it.
Because we do not sell personal information or share it for cross-context behavioural advertising, there is no such activity to disable through an opt-out preference signal. We honour applicable legally required signals and choices.
9 Hosting and international access
Customer data is hosted in Microsoft Azure’s United States regions. Authorised staff or contractors in the United States, Australia and North Macedonia may access it where needed for the purposes described in this Policy. External providers selected by a customer may process information in other locations under their own policies.
Privacy laws differ between countries. Where international-transfer restrictions apply, we must put the required transfer safeguards in place before the restricted transfer, such as an applicable adequacy mechanism or approved contractual safeguards with supplementary measures where necessary. We do not rely on acceptance of these Terms or this Policy alone to authorise restricted transfers.
Contact support@ryarc.com for information about the safeguards applicable to your data and a copy where the law provides that right, subject to appropriate redactions.
10 Retention and deletion
We retain active-account information for as long as needed for the stated purposes, subject to applicable legal limits. On account closure, ordinary account data, media, Constitutions and stored customer-agent messages are deleted or effectively anonymised from live systems within 90 days, unless a specific legal or dispute-related retention requirement applies.
Transaction and billing records are generally retained for seven years after the relevant transaction or record date for accounting, compliance and disputes, to the extent lawful and necessary. This does not authorise retaining all message contents or uploaded media for seven years merely because the account made a transaction.
Technical and security logs are retained for the period reasonably needed for troubleshooting, security and investigation, based on their purpose, sensitivity and legal requirements. Records subject to an active dispute, legal hold or legal retention duty may be kept longer; access and use are restricted to that purpose.
After deletion from live systems, residual copies may remain in backups for up to 90 additional days. Backups are isolated from ordinary use. If a backup is restored, applicable deletions are reapplied. A shorter statutory deadline or valid deletion right takes precedence where required.
Lawfully anonymised analytics, datasets and models may be retained indefinitely. They are not treated as anonymous if they remain reasonably capable of identifying an individual. Closing an account does not delete another party’s independently held transaction records or copies held by a customer-selected AI provider.
11 Security
We use encrypted connections, Azure encryption at rest, role-based access restrictions and backups. Authorised access is limited according to operational need. No system can guarantee absolute security.
Customers must protect credentials, control organisation and agent permissions and report suspected compromise promptly to support@ryarc.com. We handle and notify personal data incidents as required by applicable law and relevant agreements.
12 Privacy requests and regional rights
Depending on the law that applies, you may have rights to access or obtain a copy of personal information, correct it, request deletion, restrict processing, object to processing, receive portable data, withdraw consent or appeal a refusal. These rights are subject to statutory conditions and exceptions; they do not automatically entitle a person to every business record held by Foro.
Send requests to support@ryarc.com. We may request proportionate information to verify identity or an agent’s authority and clarify the request. We respond within applicable statutory periods. We charge a fee or refuse a request only where the applicable law permits and provide the required explanation. We do not discriminate against individuals for exercising protected privacy rights.
If we process information solely for a Network Operator or another customer, we may direct the request to that organisation and assist as required by law or our agreement. You can also contact that organisation directly.
Where EU or UK data protection law applies, rights may include objection to processing based on legitimate interests, restriction and portability in the circumstances defined by law, and complaint to a competent supervisory authority. Responses are generally due within one month, subject to lawful extensions. These rights are not waived by the Terms.
Where Australian privacy law applies to our handling of your information, you may request access or correction and raise a privacy complaint with us. You may also contact the Office of the Australian Information Commissioner where it has jurisdiction.
Where California or another US state’s privacy law applies, the relevant access, correction, deletion, portability, authorised-agent, appeal and other statutory rights apply as provided by that law. We do not sell or share personal information for targeted advertising. The categories, sources, purposes, recipients and retention practices are described in this Policy. We do not use sensitive personal information to infer personal characteristics.
You may challenge our response through support@ryarc.com and complain to the relevant regulator where the law permits. This Policy does not promise a bespoke reporting or migration service beyond legal requirements.
13 Automated actions and children
Customer-selected agents can negotiate and make commitments within permissions expressly authorised by the customer. Network Operators decide whether to extend credit. Foro does not itself provide credit or use this Policy as consent to automated decisions requiring separate legal safeguards. Where applicable law gives rights concerning a solely automated decision with legal or similarly significant effects, those rights remain available.
Foro is intended for business users aged 18 or older. We do not knowingly register children or solicit their personal information. Contact support@ryarc.com if you believe a child has supplied personal information through an account so we can investigate and take appropriate action.
14 Changes and contact
We may update this Policy to reflect changes in our services, practices or legal obligations. We will identify the updated version and provide advance notice of material changes where required. Where a new purpose requires consent or another lawful basis, publishing a revised Policy alone does not provide it.
Privacy enquiries, requests and complaints: support@ryarc.com.
Postal contact: Glen Strand Corporation, 8201 164th Ave NE #200, Redmond, WA 98052, United States.