Privacy Notice
Ask about remote administrative support without sending the records behind the task. This notice explains what Opryq receives when you use this website, how we use it and the choices you have over advertising storage and your personal information.
The site introduces a virtual assistant for small business, not an account or payment service. A service inquiry is separate from permission to use optional advertising or analytics storage.
Who is responsible
Opryq, trading at opryq.com, operates this website and is the controller of the personal information collected through its inquiry forms and support chat. Our contact location is Austin, Texas, United States.
42 Market Street, Büro 5, Austin, Texas 28921, Austin, Texas, United StatesThis is a contact address. Administrative support is delivered remotely; the address does not identify a walk-in office. For questions about this notice, write to [email protected].
This notice concerns the public website and the discussion of possible work. Access to a client's working systems needs a separate agreement defining the task and the permitted handling of records. Do not use the public form as a way to deliver a customer database.
Information the site receives
The inquiry form records your name and any phone number, email or address you enter. It also records the kind of inquiry, your message, the requested specification and the consent tick. The workload planner can pass the specification you build into an inquiry. An address is optional; a phone number or an email provides the reply route.
With a submitted inquiry, the site automatically records the IP address, browser user-agent string, referring URL, the moment the form was rendered and the moment it was sent. These technical records help distinguish a real inquiry from automated abuse and establish the source and timing of the submission.
Support chat keeps the conversation and a token that lets the same browser return to it. Messages can include the name or reply details you choose to supply. The browser token is an access link to the conversation, not a public account or a password you create.
The browser stores your consent choice under site_consent_v2. Optional advertising identifiers include gclid, msclkid and fbclid. A paid link can contain an identifier before you make a choice; its presence in an incoming URL is different from permission to retain it in optional browser storage. A referring URL recorded with an inquiry can also contain query information.
Server and access logs contain technical request information used to operate and protect the site. There is no account registration, password collection, payment or card-data field. Nothing is sold or paid for on the website. Please do not put those details, health information or private client records into a message.
What each record is used for
Contact details let us answer you. Your task description and specification let us assess the proposed work, discuss an approval boundary and keep track of what you requested. An inquiry is not treated as permission to make decisions on your behalf or to start work without an agreement.
Conversation records let us continue a discussion without asking you to repeat the task. The functional chat token connects your browser to that discussion. A consent record applies your storage preference when you return; it is not an advertising permission inferred from a service inquiry.
Technical submission data and access logs support site operation, abuse prevention and investigation of delivery problems. Optional analytics storage supports measurement of visits. Optional advertising storage and permitted advertising data use help connect paid clicks with activity on this destination and support ad measurement or personalization according to your choice.
Information supplied for a privacy request is used to identify the relevant records and answer that request. We do not need a copy of your identity document through the public website. If clarification is needed, we ask for information proportionate to the request.
The basis for using information
For visitors in Europe, we distinguish consent from the steps needed to answer a requested service inquiry. A lawful basis depends on the purpose, not on whether every field has been filled in. US state privacy rights apply as described below.
| Purpose | Information involved | Legal basis |
|---|---|---|
| Discuss requested work | Name, reply method, task message and requested specification | Contract: steps at your request before entering a service agreement. Consent applies to the permission you give to respond. |
| Continue support chat | Messages, supplied contact details and conversation token | Legitimate interest in responding to a conversation you initiate; consent for the contact details you voluntarily provide. |
| Operate and protect the site | IP address, browser user-agent, referring URL, form timestamps and access logs | Legitimate interest in a functioning site, reliable message handling and prevention of automated abuse. |
| Remember a privacy choice | Consent preference record | Legitimate interest in respecting your choice and legal obligation where consent records are required. |
| Optional measurement and advertising | Permitted analytics storage, advertising identifiers and consent signals | Consent for optional storage and the related permitted uses. Required consent-state handling is distinguished from optional tracking. |
| Respond to privacy rights | Request details and proportionate verification information | Legal obligation where privacy law requires a response; legitimate interest in resolving other privacy questions. |
A legitimate interest is not a blanket permission. You can object to processing based on that interest and explain your circumstances. Withdrawal of optional consent does not stop us answering a service inquiry you have asked us to handle.
Paid traffic and click identifiers
Google Ads, Microsoft Advertising and Meta Ads send traffic to this site. Google links can attach gclid, Microsoft links can attach msclkid and Meta links can attach fbclid. These click identifiers help the relevant platform relate a visit to an advertisement.
Google Ads and Microsoft Advertising identifiers describe a click rather than a field you type into the form. An identifier can still be personal information when associated with a browser, visit or other platform data, so optional persistence follows your storage choice.
Do not assume that arriving through an advertisement grants consent. Optional click identifiers are not persisted before permission. Advertising platforms have their own privacy responsibilities for the information they receive, described in the linked policies in the next clauses.
Consent Mode v2 and denied defaults
The site's consent mode implementation uses Consent Mode v2. Before you allow storage, ad_storage, ad_user_data, ad_personalization and analytics_storage are all held denied. Permitted states are set only after you choose Allow storage. All four return to denied the moment you decline or withdraw permission.
Denied does not mean a promise that no tag loads or no network request occurs. Consent-state signals and denied-mode, storage-limited measurement signals can still be sent to communicate the choice. Those signals are distinct from permission to place optional advertising or analytics identifiers in this browser.
Use Cookie preferences in the footer to reopen the controls and choose Decline optional storage to withdraw. The inquiry form remains available. Consent to answer a task inquiry does not override a denied advertising state. Browser controls can also remove stored information, but deleting a preference can mean the site no longer has that earlier choice to read.
Read the storage inventory and choice controlsWho receives information
Recipients depend on what you do on the site and the permissions you give. Advertising recipients are not the people answering your task inquiry. Platform companies can determine their own purposes for platform data; they are not all described here as processors acting only on our instructions.
- Google Ireland Ltd / Google LLC receives Google Ads consent signals and permitted advertising or measurement information associated with
gclid. See Google's Privacy Policy. - Microsoft Ireland Operations Ltd handles Microsoft Advertising information associated with
msclkid. Its handling is described at privacy.microsoft.com/privacystatement, also available in the Microsoft Privacy Statement in English. - Meta Platforms Ireland Ltd handles Meta Ads information associated with
fbclidwhere a campaign runs there. See Meta's Privacy Policy. - The hosting provider serves the website and stores the inquiry database and technical records needed for that service.
- The mail provider carries inquiry notifications and replies to or from the operator's inbox.
Opryq receives the inquiries and conversations so a person can consider the requested work. Ask [email protected] for details about the hosting or mail provider handling your submission.
Processing across borders
Opryq is in the United States. A visitor contacting us from another country sends information to a US-based operator. Hosting, mail and advertising services can also process information outside the country where a visitor first provides it, including in the United States and countries used by those providers.
Where GDPR rules apply to a restricted international transfer, the transfer must use a lawful mechanism, such as an applicable adequacy decision or contractual safeguards including standard contractual clauses, with additional safeguards where needed. We do not claim that every recipient participates in a particular certification or that every destination provides identical protections.
You can ask which transfer arrangements apply to your information and request information about the safeguards. The platform policies describe their own international processing. A link to a platform policy is not a waiver of your rights against Opryq.
Retention periods
Records have different purposes and different periods. The inquiry record is retained for 36 months, not indefinitely because a conversation might someday restart. A chat has a shorter retention period even when the browser still holds a token.
| Record | Period | Purpose during that period |
|---|---|---|
| Inquiries and their email copies | 36 months | Follow-up and a record of the requested work and correspondence. |
| Chat transcripts | 12 months | Continuation and review of the task conversation. |
| Server and access logs | 60 days | Operational diagnosis and protection against misuse. |
| Record of a consent choice | 12 months | Applying and recording the visitor's storage preference. |
These are record-retention periods, not a statement that every browser storage item expires on the same schedule. The local chat token can remain until browser storage is cleared. It does not extend the transcript period. Optional identifiers follow the relevant permission and removal controls; platform-side retention is explained in the platforms' own notices.
A deletion request can affect information before the listed period ends, subject to applicable exceptions. A legal duty or an active legal claim can require particular records to be retained separately. If an exception prevents deletion of information you request, we explain the reason rather than treating it as a general extension for all records.

Protection and its limits
The site uses HTTPS for transport. Submission checks and technical records help detect invalid requests and automated abuse. Access to inquiry records is limited to the handling of those records, rather than made available through the public service directory.
Your browser also matters. The chat token lets that browser return to a conversation. On a shared device, clear the site's stored data when you no longer want another user of that browser to reopen it. Keep passwords and private records out of both the form and the chat.
No website or email route can offer absolute security. If you believe a message has exposed information it should not contain, contact us with a description of the problem, not another copy of the sensitive material. Limited task access and approval boundaries for actual service work are discussed in the working method.
Rights for visitors in Europe
Where the General Data Protection Regulation applies, your GDPR rights include access to your personal data and information about its use; rectification of inaccurate information; erasure in qualifying circumstances; and restriction of processing while a relevant issue is resolved.
You may also request portability of information you provided where processing is automated and based on consent or contract. You can object to processing based on legitimate interests, including explaining why your circumstances require us to stop. Objection to direct marketing does not require that explanation.
You can withdraw consent at any time. Withdrawal does not make earlier lawful processing unlawful, and it does not cancel another lawful basis for records we must retain. Rights are subject to the conditions and exceptions in the applicable law. We explain a restriction or refusal in our response rather than asking you to accept it without a reason.
US state privacy rights
US state privacy law applies, including California's CCPA/CPRA and the other state laws in force. Where applicable, these rights let you know or access the personal information held about you, obtain a copy, correct inaccurate information and request deletion.
California visitors can exercise CCPA rights to opt out of the sale or sharing of personal information. Other state laws provide rights to opt out of targeted advertising and certain profiling, and rights concerning sensitive information where those uses occur. An advertising disclosure can count as sharing under a privacy law even when no money changes hands. Declining optional storage is available without making a service inquiry.
You may exercise applicable rights without discrimination for doing so. An authorized agent can submit a request, subject to proportionate verification of their authority. If a request is refused, you can ask us to reconsider and use any appeal right under your state's law. State rights have eligibility rules and exceptions; this notice does not remove them or invent a narrower set.
Global Privacy Control
We honor Global Privacy Control. The Sec-GPC header is treated as an opt-out without asking again. A global privacy control signal does not need to be accompanied by a name or an inquiry to express that choice.
The signal concerns privacy choices, not a request to delete every record of a past conversation. For deletion or access, use the data request route. Browser signals can be specific to a browser or device, so check the setting on each device you use.
Not a service for children
This website is for business inquiries and is not directed to children. We do not knowingly collect personal information from children and do not ask them to submit messages. A business task description should not contain information about a child.
If you believe a child has sent personal information, tell [email protected] enough to locate the message. Do not send further sensitive details. We will review the report and remove information collected from a child as required by applicable law.
Complaints and regulators
You can complain to a data protection authority where GDPR applies, including the authority in your place of habitual residence, place of work or the place of an alleged infringement. You do not have to complete a conversation with Opryq before using that right.
In the United States, you may complain to your state Attorney General. California visitors may also complain to the California Privacy Protection Agency. You can contact us as well if a privacy response seems incomplete or does not address the information you requested.
Make a request without sending identity documents
Use the data request form or write to [email protected]. A data request is answered within 7 days. State which right you want to exercise and, if possible, the reply details used for the earlier inquiry so we can locate the record.
We use proportionate verification before disclosing or deleting information. We may need to confirm control of the contact method already associated with a record. Do not upload or email an identity document merely to start a request. If more information is needed, the response explains what is missing and why it is relevant.
You can also write to Opryq at 42 Market Street, Büro 5, Austin, Texas 28921, Austin, Texas, United States. Changing your browser choice is immediate through Cookie preferences; it is not necessary to wait for a data-request response to decline optional storage.
Changes to this notice
We publish changes on this page and update the version and last-updated date in the document masthead. The effective date identifies which notice applies; it is not a claim about how long Opryq has operated.
A material change in a purpose or a consent requirement is brought to visitors' attention through an appropriate notice or renewed choice before the new consent-dependent use. Continuing to read a service page does not by itself supply permission for a new optional purpose.
A person can answer your privacy question
Contact Opryq about a privacy question or a record you have already sent. Include the subject of your inquiry and an approximate submission date if you know it; you do not need to repeat the whole message.
42 Market Street, Büro 5, Austin, Texas 28921United States
For a new administrative task, use the general inquiry form. The Service & Website Terms explain the status of an inquiry and the separate agreement needed before work begins.
Opryq / Privacy Notice / Version 1.0 / Published October 10, 2026. Storage controls are described separately in Cookies & Storage Choices.