Name the change you want.

01 / Scope

A short description is enough to begin. Tell us whether you want to see data we hold about you, correct a detail or ask for deletion. If you want more than one action, select the combined request option and explain the actions in the notes.

For a team workspace setup inquiry, useful context is the reply address you used and the general subject of your message. For support, say that the information relates to a chat conversation. Do not paste a chat-session token: it can be used to continue that session.

Access
Ask whether we hold personal data about you and request a copy or an explanation of the processing that applies. Identify the correspondence or support context rather than sending the whole conversation again.
Correction
Describe which detail is inaccurate and give the replacement detail only where it is necessary. Correcting an old reply address is different from asking us to disclose information to a new, unverified address.
Deletion
Say what you want removed. We assess the request against the purpose for holding the information and any applicable legal obligation. A request does not automatically erase records another organisation holds independently.
Withdrawal or another right
Ask to withdraw consent, object to a use or restrict processing where the applicable law provides that right. You can describe the outcome you want without naming a legal provision.

Send a data request.

02 / Request form

Your name and processing consent are required. Give either a phone number or an email address so we can reply; each is optional on its own. This form does not subscribe you to advertising or grant optional storage permission.

Choose the closest description. Use the notes to explain any additional action.

Use the name associated with your correspondence, where possible.

Provide at least one reply route. Using the email address from your original inquiry can help us match the request without collecting extra information.

Leave this blank unless an address is relevant to your request. It is not required for verification at this stage.

Describe the records and the requested action. You may include an inquiry reference and an approximate correspondence date. Do not include passwords, identity documents, payment details, chat tokens or sensitive information about you or anyone else.

Permission to handle this request

Submission starts a request. It does not confirm that records have been disclosed, corrected or deleted.

Verification should fit the request.

03 / Protecting disclosure

Before disclosing personal information or making a change that affects it, we may need to check that the request comes from the person concerned. The check should be proportionate to the information and the risk. We start with correspondence context and a reply route, not a demand for an identity-document upload.

If your contact details have changed, tell us that without adding unrelated personal history. We may ask a focused follow-up question or explain why the available information is not enough to make a disclosure safely. Sending more sensitive material unprompted does not make that check safer.

Asking for someone else

If you act for another person, state that relationship and the action requested. We may need to establish your authority before disclosing that person's information. Do not attach their identity records to the initial message.

A shared workspace can contain information about more than one person. An access request does not entitle a requester to another person's private correspondence. Where that affects a response, we consider whether information can be separated or limited instead of treating the whole record as freely disclosable.

Change optional storage without waiting for a reply.

04 / Withdrawal

Open Cookie choices to change the allowance saved in this browser. Choose Decline optional storage to withdraw both analytics and advertising allowances, or save separate choices. That control is different from requesting deletion of information already held in correspondence.

Consent Mode v2 keeps ad_storage, ad_user_data, ad_personalization and analytics_storage denied until the corresponding storage or use is allowed. Choosing Decline optional storage or withdrawing both allowances returns all four signals to denied. When you change only one category, the other category keeps its saved choice. Saving withdrawal also clears known optional first-party storage under the site's control; it does not erase records held independently by a provider.

Google Ads and Microsoft Advertising send visitors here; Meta Ads may also send traffic. Their click identifiers are gclid, msclkid and fbclid, respectively. An identifier can arrive in a visit URL before storage is allowed. Optional storage of attribution identifiers waits for permission; denied consent restricts storage and personalisation, not the existence of advertising.

If your request concerns a provider's own records, its privacy information explains its independent processing and request routes. See the Microsoft privacy statement, Google privacy policy and Meta privacy policy. You can still ask Moxby about the processing under our control.

For withdrawal of consent connected with an inquiry or support conversation, use the form or email us. State which processing you mean. Withdrawal does not undo processing lawfully carried out before it, and information may still need to be retained where another lawful basis or obligation applies.

Receipt starts the review, not the outcome.

05 / Handling & retention

An accepted form submission provides a receipt. It confirms storage of the request, not completion of the action. If the form reports a connection failure or cannot confirm receipt, do not assume it succeeded. Contact us before resending if you want to avoid a duplicate.

We consider the request under the law that applies, including any applicable response period and permitted extension. We do not promise a single deadline for every request. Clarification or verification may be needed; where a legal time limit applies, it governs how that is handled.

If we cannot carry out all or part of a request, we explain the reason as far as we can lawfully do so. You can ask us to reconsider or clarify the response. Any applicable right to appeal or complain to a competent authority remains available.

The form is not the only route.

06 / Contact alternatives

Email your request to [email protected] or call +1 (656) 555-6275. Say that it is a personal data request rather than a new Moxby browser assistant inquiry. The same proportionate verification guidance applies whichever route you choose.

26 Mill Street, Werkstatt 2, Austin, Texas 12918
United States

The privacy notice explains the uses and recipients of personal data. For help operating this website or describing an obstacle, read Accessibility & Getting Help. Product questions belong on the contact page.

Storage choices

Choose analytics and advertising separately. Declining does not prevent reading the site or sending an inquiry.

Essential operation

We keep your choice under site_consent_v2. A support session you start uses a separate chat token so you can return to the conversation. These are not advertising choices.

Allows optional storage used to understand visits to this website.

Allows optional advertising storage, advertising user data and personalisation. Google Ads and Microsoft Advertising send traffic here; Meta Ads may also send traffic.

Consent Mode v2 keeps ad_storage, ad_user_data, ad_personalization and analytics_storage denied until you allow the corresponding use. Choosing “Decline optional storage” withdraws both allowances and returns all four signals to denied. Advertising choices control the first three signals; analytics controls the fourth.

Google's gclid, Microsoft's msclkid and Meta's fbclid can arrive in a visit URL before permission. Optional storage of these identifiers for attribution waits for permission. Advertising continues under denied consent signals, which restrict storage and personalization. Read the cookie statement and the Microsoft privacy statement.