ARKQON
Privacy policy
The information ARKQON handles, why it is used and how to contact us about it.
Version 2026-11-11.1On this page
Who you are dealing with
ARKQON
ABN 42 839 638 864
Legal and privacy: legal@arkqon.com
General enquiries: hello@arkqon.com
ARKQON and customer businesses
This policy covers information handled for ARKQON's website, accounts and service operations. A business using ARKQON also decides what customer information it records and shares. Its own privacy information applies to its activities. Using ARKQON does not merge the records of separate businesses.
A business using ARKQON is responsible for the lawful collection, accuracy, purpose and sharing instructions for personal information it supplies, including required notices and consents. ARKQON is responsible for its own handling and legal obligations. A customer instruction does not authorise unlawful processing.
Information we handle
When you make an enquiry, we receive your email and the name, business, industry and message details you choose to provide. An Enterprise quote request can also include your team size, required features, integrations, white-label preferences, timing and other requirements you supply. Required fields are identified in the form. We use these details to review and answer the enquiry. Website enquiries are recorded in ARKQON and an email copy is sent to ARKQON's hello@arkqon.com mailbox, hosted by Proton. The email delivery service and mailbox provider process the information needed to deliver and hold that copy. Do not include passwords or unnecessary customer, worker or other sensitive information.
Account and workspace use can involve identity and contact details, access permissions, quotes, invoices, customer records, uploaded files and action histories. We also handle technical information needed for sign-in, security and diagnosing errors. Provide only information needed for the task and which you are authorised to share.
Depending on the enabled workflow, records may include worker and supplier details, qualifications, attendance, site location, safety or incident information, photographs, signatures and associated time, IP address and browser evidence. Some records can contain sensitive information. Do not upload government identifiers, health details or other sensitive material merely because a text field or attachment permits it; the responsible business must establish a lawful need and any required notice or consent.
Customer links can record visits and actions for the business that shared the link. The Tracking policy explains the identifiers and limits of this evidence. The public sample demo keeps its sample work in the page. Resetting or reloading clears that sample work; this does not mean the website or hosting service has no technical logs.
Information can come directly from you, from the business that invited or dealt with you, from authorised workspace users, from connected providers and from the browser or device used to interact with the service. We do not assume that information supplied by another person is correct or that it proves your identity. Tell us when a relevant record is wrong.
You can make a general enquiry without opening a workspace and may use a pseudonym where practical. We may need verified identity or authority for account access, payments, signatures or a request involving someone else's records. If necessary information is not provided, the affected service or request may not be able to proceed; this does not justify collecting unrelated information.
A billing, refund, support, privacy or closure request can include the affected account and payment reference, your description, necessary evidence, replies, status changes and the decision. We use this information to resolve the request, check authority, reconcile payments and meet relevant legal obligations. Do not submit full card details or unnecessary sensitive information. A privacy request is not permission to copy your whole workspace into a support ticket.
How information is used
Information is used to respond to requests, operate accounts, provide business workflows, deliver authorised messages, manage billing and investigate service or security problems. A connected integration handles the information needed for the selected feature and permissions.
Do not treat a sample demo or an access request as permission to collect unrelated personal information. A separately introduced research or marketing use needs its own clear explanation and any required choice before it begins.
Information may be disclosed to authorised members of the relevant workspace, recipients you or that business select, connected service providers and advisers who need it for the relevant purpose, or where a lawful requirement applies. A public portfolio or business card can be viewed and copied by people outside the workspace. Check its audience before publishing. Private workspace access and public publication are different permissions.
Optional page and control activity
ARKQON offers optional product activity recording to understand which pages and controls people use. If you allow it, we record a safe page category, an approved action name, the selected control's position where available, a safe destination category, a general referring-site category, the input type, a browser timestamp and a server receipt timestamp. We do not record what you type, message contents, customer photos, passwords, login codes, payment details, or private link tokens through this feature.
In the signed-in app, these observations are associated with your authenticated account and current workspace. The workspace owner and authorised ARKQON administrators can review that workspace's observations. Website observations are anonymous and are available only to authorised ARKQON administrators. We do not treat an account, forwarded link or referrer as proof of the physical person using a device. A recorded click is not proof that a business action completed.
This recording is off by default. You can allow or decline it in Activity Privacy on the website or Privacy and Support in the app. Your choice lasts 90 days in that browser and is separate for the website and each app account/workspace. Declining does not stop your work. Necessary security records, saved-work history and existing customer-link tracking retain their separate purposes and controls. Changing this choice stops future optional collection; it does not rewrite previous receipts.
Optional activity is visible in its report for 30 days. Daily maintenance removes expired observations in bounded batches. If maintenance fails or is backlogged, removal may take longer; expired observations are not shown in the report. Security controls limit request and storage volume. The service may therefore have incomplete observations, and these records must not be treated as a complete attendance record, exact traffic count or proof of a person's actions.
Providers and connected services
Hosting, database, authentication, email, payment and AI providers can process information needed for their part of the service. Connecting a mailbox permits the requested mailbox access; it does not automatically authorise sending through that mailbox. Review the connection permissions and the provider's own privacy information.
When you connect Gmail, ARKQON uses your Google account identity to identify the connected mailbox. With your permission, ARKQON reads messages, images and attachments so you can view them in the application. With Gmail management permission, actions you choose in ARKQON can mark mail read or unread, star or unstar it, archive it or return it to Inbox, and move it into or out of Spam and Trash in Gmail. Gmail folder and message flags are synchronised back into ARKQON. This integration does not permanently delete Gmail messages or replay old local filing actions. Outgoing business email and delivery tracking use Resend.
ARKQON follows the Google API Services User Data Policy, including its Limited Use requirements, when using or transferring information received from Google APIs.
For a connected Gmail mailbox, ARKQON keeps a small index of message and conversation identifiers, dates, folder/read flags and verified links to messages sent through ARKQON. This supports folder totals and avoids counting the same send twice. The index does not contain email bodies, subjects, addresses or attachments. Message content is processed temporarily when you read mail or when ARKQON verifies a received copy against its own send. Disconnecting Gmail, replacing the connected account or removing reading access in ARKQON removes its active index. Revoking access in Google stops further authorised reads but does not instantly erase stored metadata in ARKQON; disconnect in ARKQON to remove that index. Independently saved ARKQON records and applicable backup retention remain separate.
Where Stripe checkout or billing is used, Stripe handles payment details and the customer information needed to process the payment. This can include your name, email, billing address, business tax identifier or tax status, selected service, transaction amount and technical information. Billing location and relevant tax details are used to calculate applicable tax. ARKQON receives the payment, subscription and tax results needed to administer the agreed service. Do not send card details to ARKQON by email.
Stripe processes information for payment services and also for its own fraud prevention, security and legal obligations. Its published data-processing terms describe transfers to the United States and other countries used by its affiliates and service providers. Stripe has its own privacy information. This is separate from permission to publish your business address or contact details on an ARKQON public page.
When enabled and used, email and messaging services receive the selected recipients, message content and relevant attachments or action links. A Telegram connection uses a linked chat identifier. Browser or device push delivery uses subscription identifiers and notification transport; permission and subscriptions can differ between devices. Security challenge services, including configured Cloudflare Turnstile checks, can process challenge tokens and relevant technical information such as an IP address to protect forms and sign-in.
Map, route and weather features can send requested map areas or relevant coordinates to the service used for that feature. Source integrations include OpenFreeMap or OpenStreetMap maps, OSRM routing and MET Norway weather. This does not mean every integration is enabled in your workspace. A location entered for a route or site feature can be information about a person or private site; provide it only when authorised and needed.
Palm features can send relevant conversation, selected attachments, workspace context, retrieved records and tool results to an AI provider to answer or review a task. Configured integrations include Anthropic and TypeSafe. Recorded audio can be sent to Deepgram for transcription when voice features are used. Do not submit information you are not authorised to disclose. The public sample demo does not submit its sample brief to live AI.
Providers may process information outside Australia, including for infrastructure, support and the selected feature. A database region alone does not establish the location of every provider copy or support interaction. Provider locations, contractual safeguards, retention and AI data-use settings must be checked for the services actually enabled; this policy does not promise Australian-only processing or that every provider uses the same settings.
The primary Supabase project is configured in Sydney, Australia. Recovery snapshots use a private Cloudflare R2 bucket configured in Oceania. That regional setting does not identify a specific country for every copy. Vercel hosts the application. These infrastructure locations do not establish where provider support, logs, subprocessors or an optional integration process information.
Transactional email uses Resend, whose published security information identifies the United States as the location of stored email data, regardless of the sending region. ARKQON's own contact mailboxes use Proton. Sending a message to ARKQON's contact addresses is separate from authorising access to your own business mailbox. Your selected recipients and their email providers can keep their own copies.
For enabled AI features, TypeSafe's published privacy policy identifies United States hosting, storage and processing. Anthropic's commercial privacy information identifies United States storage, with processing potentially routed through countries in the United States, Europe, Asia and Australia and additional support or safety processing where its group operates. Those provider statements do not establish that ARKQON has a custom regional-routing or zero-retention agreement. The selected feature and verified account arrangement determine the actual handling.
Ask legal@arkqon.com for information about the providers and overseas handling relevant to your use before providing sensitive information. A provider's separate privacy terms do not remove obligations that apply to ARKQON. Connecting an optional service does not authorise unrelated uses of your records.
Security and retention
Access controls help limit who can use workspace information. No online service can guarantee that an incident will never occur. Do not share private links or account access with people who should not receive the information.
We will take reasonable steps to destroy or de-identify personal information when it is no longer needed for a permitted purpose and applicable law does not require its retention. An identified legal hold or retention obligation must be assessed for the affected records. Technical ability to keep a copy is not by itself a reason to retain it indefinitely.
Different records have different purposes and retention needs. Removing a browser identifier is not the same as deleting a server event. Closing a link cannot recall a PDF or other copy already obtained by its recipient. The Data policy explains these distinctions.
Report a suspected privacy or security incident to security@arkqon.com. Describe the issue without including secret keys or another person's full records. We will assess the incident, take appropriate containment and recovery steps and make notifications required by applicable law. An automated alert or successful service check alone is not proof that an incident is resolved.
Access, correction and privacy concerns
You can update editable account details in the application. Use Settings > Privacy and support to request access, correction, deletion, an accessible policy copy or review of a privacy complaint. The request shows its receipt and progress. Email legal@arkqon.com remains available if you do not have an account, cannot sign in or cannot use the control. Identify the relevant interaction and outcome sought. We may request proportionate evidence of identity or authority to protect other people's information. Do not email identity documents unless an appropriate verification process has been agreed.
We will review the request, clarify the affected records if necessary, consider the rights of other people and explain the outcome. Where access or correction cannot be provided, we will explain the applicable reason and available complaint options, subject to lawful restrictions. A correction may need an additional explanatory record where an original transaction or signature must be preserved. We do not charge for making a privacy request or complaint, correcting personal information or associating a statement. If the law permits a charge for providing access, we will explain it beforehand.
If your request concerns a business that sent you a quote, invoice or card, identify that business so responsibility can be established rather than assuming ARKQON controls every decision about its records. For a complaint about ARKQON, describe what happened, when and the resolution sought. We will investigate and respond, explaining any need for more time. If dissatisfied, you can seek internal reconsideration and, where the matter is within its jurisdiction, complain to the Office of the Australian Information Commissioner through oaic.gov.au. The OAIC generally asks that you first complain to the organisation and allow 30 days for a response; this is not a promise to resolve every request in that time.
Communication choices and policy changes
Use the application's notification preferences for available choices and the unsubscribe control provided with marketing. Use in-app support or notifications@arkqon.com if a preference is unavailable or not working. Necessary account, security and transaction messages may be handled separately from marketing. Blocking notifications on one device does not necessarily change another device, an email preference or a workspace automation.
We review this policy when features, providers, purposes, legal obligations or handling practices change. The displayed version identifies the text. A revised notice is not retroactive consent to a new use; any required notice or choice must be provided before that use begins. Contact us for the version relevant to an earlier interaction.
