Privacy Policy

Information you provide

We collect information you provide when you enquire about licensing, create or manage an account, configure an integration, use a tool, or contact us. Depending on your use, this may include:

• Name, email address, company name, shop website, and the country your business sells in;
• Organisation name, company number and address, colleague email addresses, invitations, roles, and membership;
• Account credentials, verification-code records, two-step authentication settings, passkey names, and recovery-code records;
• Shop settings, registered listing schemas, tool settings, embed branding such as colours and a logo, and the website addresses allowed to use your embeds;
• Listing titles, descriptions, attributes, seller answers, pricing information, photographs, and references supplied by your integration;
• Questions, recent conversation context, generated drafts, reports, and tool results;
• Device serial numbers or IMEI numbers, which identify a particular device, and related verification information;
• Documents, files, and web addresses your business adds for Ask PCIFIC to answer from, and the address of your own item-lookup service;
• API key records, selected plans, usage, credits, allowances, and billing or invoice records;
• Bring Your Own details for an OpenAI or Anthropic account your business asks us to connect: the provider, model name, provider key, and connection-check results;
• Webhook addresses and their signing secrets; and
• Sales enquiries, feedback, support correspondence, and information you choose to share for an investigation.

Account, authentication, and organisation data

We keep password hashes, not the password itself. A hash is a one-way value used to check a password without storing its original text. We also keep protected two-step secrets and fingerprints of recovery codes, email codes, session tokens, API keys, and other credentials. A hash or fingerprint is not necessarily anonymous information.

Session records include the full network address (IP address) and the browser description your browser sends, sign-in and last-use times, and expiry or revocation. You can see your own sessions in Settings. When a new device signs in, we email you its browser and network address so you can spot sign-ins that are not yours. We do not work out or request your location.

Your organisation's owner and administrators can manage membership and shared resources. Every member of a business can see the names, email addresses, and roles of the other members. Owners and administrators can also see pending invitations and each member's sign-in and security history from the day that member joined, shown with a shortened network address and a device description. Personal passwords, two-step settings, and sessions remain attached to the individual account, not transferred to the owner.

Automatically collected information

We process network addresses, browser and device information, timestamps, technical errors, and security or rate-limit signals to operate and protect the service. Full network addresses are kept in session records and in the security history of sign-ins and account changes, and briefly in short-lived rate-limit records.

For tool requests, we keep a content-free record of the business, API key identifier and kind, shop, tool and address called, outcome and error code, duration, the related charge, and whether it was a test or a repeated request. We also record a shortened network range. The record does not contain the full IP address, API key, prompt, photograph, device identifier, or generated answer. Our server logs separately record technical details such as the AI model used and the amount of text it processed.

For Operational only and Full monitoring, we also keep a separate encrypted copy of valid JSON request and response bodies for 30 days to help your business investigate integrations. This includes Ask PCIFIC questions and answers. Signed-in members of the same business can open these copies in Logs. Its API keys can also read them through GET /api/v1/logs/{requestId} if explicitly given the logs permission, which is off by default. Customer-held and locked contents stay locked to keys. There is no staff reading route. We remove credentials before saving: API and AI provider keys, passwords, cookies, authorization values, one-time verification codes, signing secrets and access tokens. Headers are not kept. Device identifiers such as IMEI and serial numbers, and listing text, are not removed from these copies. Each body is limited to 256 KB. Larger bodies are marked as cut and omitted. Photos and files contribute only their name, type and size. Deleting a business deletes these copies. True ZDR and Customer-held logs do not create these ordinary copies; their separate rules below still apply.

Where you accept optional analytics, Google Analytics also processes page-view and usage events, browser and device information, online identifiers, and the technical information needed to deliver its service. Section 6 explains your choices and the limits on what we send.

Information from third parties

We may receive information from your organisation or integrating business, including from its own item-lookup service when Ask PCIFIC looks up a listing; AI and web-research providers; device-verification providers; and email delivery services. Public product research may include information from websites used to answer a requested tool call. A business sending another person's information must have a lawful reason and provide the required notice.

We process information to:

• Respond to licensing enquiries;
• Create, authenticate, secure, review, and manage accounts and organisations. New accounts are reviewed by PCIFIC staff, unless they join through an invitation or an approved business email domain;
• Issue and revoke API keys, key requests from coding tools, invitations, webhooks, and permitted integration credentials;
• Configure and provide requested AI, listing, buyer-answer, device-check, and photo-check tools;
• Provide embeds, PixelTrace phone capture, and public certificate verification;
• Research public product facts and answer from the documents your business adds;
• Measure service usage, administer credits, allowances, plans and invoices, and diagnose failures;
• Assess listing quality where Full monitoring is selected;
• Respond to feedback, support requests, privacy requests, and security reports;
• Send account, security, billing, and service notices, including release and incident notices and announcements about PCIFIC Business to account holders;
• Protect accounts and infrastructure against misuse, fraud, and security incidents; and
• Comply with legal obligations, resolve claims, and enforce our agreements.

Providing a requested AI result, retaining a certificate, monitoring quality, and sending marketing are separate purposes. Information needed for one does not automatically become eligible for the others. We do not sell personal information or use customer tool requests to train models.

Performance of a contract

Where we act as a controller, we use this basis when processing is necessary to provide a service under our contract with you or take steps you request before a contract. Examples include creating a business account, administering a requested subscription or licence, and supplying a tool result. This basis does not automatically apply to every employee's information simply because their employer has a contract with us.

Legitimate interests

We may rely on legitimate interests in operating and securing our business service, managing business relationships, preventing misuse, handling support, and assessing service reliability or permitted quality signals. This applies only where processing is necessary and our interests are not overridden by your interests, rights, and freedoms. Where required, we assess necessity, less intrusive alternatives, reasonable expectations, and the effect on people before relying on this basis.

Consent

We seek consent where required for optional communications, cookies or similar technologies, or other optional processing. You can withdraw consent without affecting the lawfulness of earlier processing. Using a tool, accepting terms, or continuing to use PCIFIC does not by itself constitute consent to new processing. A workspace administrator choosing a setting does not replace any lawful basis or notice needed for the personal information of its customers.

Legal obligations and vital interests

We process information where necessary to meet applicable accounting, tax, regulatory, and other legal obligations. In limited circumstances, processing may be necessary to protect someone's life or prevent serious harm.

Processing on a business's instructions

Where we act as a processor, the business decides the relevant purpose and lawful basis. We process the information under its documented instructions and the applicable agreement, rather than treating this notice as permission for unrelated use.

Sensitive information and anonymisation

Special category data, such as health information, needs an additional legal condition as well as a lawful basis. Criminal-offence information is subject to additional restrictions. Please do not send this information unless a specifically agreed service requires it and the necessary conditions have been met.

Removing a name, hashing an identifier, or replacing an account ID does not necessarily make information anonymous. Information is genuinely anonymous only when a person cannot reasonably be identified. Collecting or anonymising personal information still requires a lawful basis.

AI-powered services

Orbit assists with listings, Safeguard reviews listing evidence, and Ask PCIFIC answers listing-specific buyer questions. Depending on the task, the model receives prompts, relevant listing context, your business's documents and settings, seller answers, photographs, recent conversation, and tool results. AI output can be inaccurate. Review generated details, reports, and suggestions before publishing or relying on them.

Ask PCIFIC questions, supplied context and answers appear in the encrypted 30-day request contents on Operational only and Full monitoring. True ZDR and Customer-held logs are excluded from these ordinary copies. Separately, while chat history is on, which is the default, Ask PCIFIC keeps chats, meaning questions, answers and sources, for 30 days after the last question on every privacy tier, including True ZDR. Your business can turn chat history off in Ask PCIFIC's settings. Full monitoring records and unanswered questions follow the periods in the retention section. The integrating business or your browser may also retain its own copy.

OpenRouter and Cerebras

Standard requests use OpenRouter, which passes them to models made by Anthropic, OpenAI, Z.ai, and DeepSeek, tried in turn if one fails. OpenAI models are fixed to Microsoft Azure in the United States. For the other models, OpenRouter chooses a host. Every Standard request asks for zero data retention and refuses provider data collection, so OpenRouter only uses hosts that accept those conditions. These settings concern the model request, not every PCIFIC service record.

Ultra Fast requests, which your integration asks for, use Cerebras where available, including any photos. Ultra Fast does not yet support True ZDR, so this route is used whatever privacy tier the tool is on. A tool on True ZDR should use Standard until it does. The providers receive the content needed to return a result. Their service arrangements and applicable terms also govern their processing.

A provider not retaining a model request does not mean that PCIFIC keeps no accounts, usage records, certificates, photo fingerprints, or records permitted by your privacy setting. We do not give providers unrestricted permission to train their models on customer requests.

Bring Your Own

At your business's request, PCIFIC staff can connect your own OpenAI or Anthropic account, using the provider's official address. Requests then go to that provider under your business's account and agreement. We keep the provider and model, a protected provider key, a masked key hint, connection-check results, and acceptance of the trade-offs. Connection checks send short test prompts to your provider.

Your provider's retention and training practices may differ from our managed settings. Our True ZDR label is not a guarantee about a provider you connect yourself. Where your business explicitly enables fallback, a failed request can be repeated on PCIFIC Standard. Web research and device-verification services remain separate from the chosen AI provider.

Training and quality monitoring

We do not use your customer requests to train models. Full monitoring is for service quality assessment, including validation retries, reported edits, and comparison of Orbit's first draft with the final listing your integration reports. It does not authorise training.

A future change to training practices would require a separate lawful assessment, appropriate notice, and consent where required. Publishing different wording would not by itself override an earlier no-training commitment or permit reuse of historical information.

Please keep personal information out of AI submissions

Do not include unnecessary names, contact details, identity documents, account identifiers, passwords, payment credentials, medical information, or other sensitive or confidential material in prompts, notes, photographs, screenshots, or documents. Check image backgrounds, labels, receipts, and message threads before uploading. Use the designated account or support channel when personal information is necessary.

This guidance does not remove our responsibility for personal information we receive and is not a guarantee that submissions or outputs are anonymous.

We share information where needed for the stated purpose. Depending on the feature, recipients include:

• DigitalOcean, which hosts PCIFIC and its databases; our published hosting arrangement places the databases in London;
• OpenRouter and the hosts it selects for models made by Anthropic, OpenAI, Z.ai, and DeepSeek, including Microsoft Azure for OpenAI models, and Cerebras for Ultra Fast requests;
• OpenAI or Anthropic for Bring Your Own requests on your business's own account;
• Cloudflare, which runs web searches through Exa for product, pricing, and buyer-question research, and the websites whose pages we then read;
• Cloudflare R2, which stores tool photos and PixelTrace photos; people viewing those photos load them from Cloudflare;
• IMEI.org for device identifiers and verification results;
• Resend, which delivers our emails, including invoices;
• Google Analytics for consent-based measurement of page visits and website usage;
• Your business's own systems: its webhook addresses receive event notices containing identifiers and status, and its item-lookup address receives the item and buyer account identifiers your integration supplied;
• Authorised colleagues and administrators within your workspace; and
• Professional advisers, authorities, and other recipients where a legal obligation or justified security or claims purpose requires it.

Model providers receive the content necessary for the requested AI task. Research services receive the search terms the AI model writes for the task, up to 400 characters. Web research is on by default for Ask PCIFIC and Safeguard, and your business can turn it off. Do not include private customer details in content that may be researched. Email services receive recipient information and the message being delivered.

This business app does not use Sharetribe shop infrastructure, Facebook sign-in, a Stripe checkout, or shipping or map integrations. Those names in a consumer shop notice do not make them recipients of this app's information.

Providers may act on our instructions or independently for activities such as their own legal duties. Their notices apply to independent processing and do not replace our responsibility to explain ours. Your integrating business controls its own website and may use additional providers.

Public certificates disclose information as described in sections 8 and 17. Ordinary PixelTrace matching is confined to your workspace and does not share registered fingerprints with other businesses. We may also disclose relevant information under valid legal process, to protect against fraud or security incidents, to enforce rights, or in a business transfer subject to applicable safeguards.

Cookies and browser storage

Yes. Session cookies keep you signed in. Temporary cookies connect a pending sign-in or passkey verification step to the browser that started it. A PixelTrace capture cookie ties a camera link to the phone that opened it. These cookies are protected against access by page scripts and sent only over secure connections.

Browser local storage can remember the selected shop, animation preference, dashboard appearance, overview traffic filter and recently used pages, dismissed service notices, analytics choice and cross-tab sign-out notifications. Session storage remembers a running Orbit listing in an embed. Browser database storage, known as IndexedDB, can retain the demonstration's photos, drafts, answers, reports, and certificate information so you can continue across tool pages. On a PixelTrace capture phone, it holds the phone's signing key and photos not yet sent, for up to 2 days.

Our separate Cookie Policy lists the storage names, providers, purposes, lifetimes and available controls. Information saved only in the browser is not automatically uploaded. Information you submit to run a demonstration or tool is sent for that request, and the feature may then create its disclosed server records.

Google Analytics and your choices

With your permission, Google Analytics 4 uses cookies to measure page visits and usage on the PCIFIC Business website. It helps us understand which pages are useful and improve the site. We send approved page names and route patterns, not actual page addresses containing customer values, search parameters, certificate codes, or referring addresses. We also send named events, such as signing up, signing in, starting a sales enquiry, creating an API key or webhook, adding a shop or document, inviting a colleague, and trying a tool demonstration, with the tool name where relevant. We do not send form answers, account details, passwords, API keys, verification codes, or tool content. Advertising features stay off.

The Google script loads only after an accepted analytics choice is recorded, and only on the configured analytics website origin. We save your accepted or declined choice in browser local storage. You can choose Decline analytics or Accept analytics, and reopen Analytics preferences to change your choice. Declining does not prevent you from using the site. If the browser cannot save your choice, analytics stays off.

Withdrawing consent stops future analytics processing based on that choice and clears this site's Google Analytics cookies. It does not by itself erase information already received by Google. Contact us if you also want to exercise a privacy right over previously collected information.

Google's analytics service processes the technical information needed to deliver measurement, including browser and device information and cookie identifiers. Its own privacy information also applies to processing it undertakes independently. Operational records needed to secure tools and administer usage remain separate from optional website analytics.

Managing storage

Some storage is needed for requested functions; other preferences may be optional. Calling storage useful does not automatically make it strictly necessary. Browser settings can clear or block stored data, although that can sign you out or remove saved progress. Clearing browser data does not delete existing server records or your account.

If we introduce or change optional tracking or storage, we must provide the necessary information and choices before using it where consent is required.

PCIFIC Business does not currently offer sign-in through Google, Microsoft, Facebook, or any other provider, and no social login provider receives information about you from us. You sign in with your email address and password, an emailed code, an authenticator app, or a passkey.

If we add provider sign-in or organisation provisioning, we will update this section before it is offered, explaining what the provider sends us and what we keep.

Plans, credits, and invoices

We keep the selected plan, credit movements, usage allowances, spending limits, invoices, and administrative records needed to manage the business service. Invoices show your business name and address, are emailed to the business's owners and administrators through Resend, and are paid by bank transfer. We keep invoices and credit records for tax and accounting purposes, including after a business is deleted. The app does not collect payment card details or use a payment provider. Do not put payment credentials in tool requests or feedback.

Support and feedback

We process enquiry and feedback text, your contact or account details, the relevant page, our reply, and follow-up history. Authorised staff may also keep internal notes and records of actions needed to resolve an issue. An email you send us can contain attachments or other personal information, so share only what is needed.

Customer-held support access is limited to requests covered by a code you deliberately provide, checked against its expiry and revocation, and recorded in your audit history. Content is decrypted in server memory while an authorised person views it. We cannot open other encrypted requests with that code or reset a lost master code. Your business can switch PCIFIC support access off in its dashboard.

Device checks and certificates

Checkup is not yet available. When it opens, Checkup will send the supplied IMEI or serial number to IMEI.org. Results can include model, storage, colour, lock, blacklist, warranty, and activation information. We keep check and provider-order records, verification results, a hashed and masked identifier, account and shop references, and any seller or listing reference you supply.

Each check issues a certificate, valid for 14 days unless your integration chooses between 1 and 30 days. Checks made with a test key also create a certificate. Anyone with its code can request the public verification record, including the masked identifier, check results, and the masked IMEI.org report. Seller and listing references are not public. A certificate's validity is not a promise that its stored records are deleted when it expires.

Photo checks and PixelTrace

Ordinary PixelTrace registration keeps image fingerprints, identifiers, and related listing references rather than the original uploaded image. A fingerprint is a value used to recognise an identical or similar picture; it can still be linked to a listing and is not automatically anonymous.

The PixelTrace camera-certificate flow is different: it stores processed photographs and a dated capture record. The capture record also keeps the capturing phone's browser description and touch support. After completion, anyone with the certificate code can see its published photos and public certificate details, such as the shop name, listing title, dates, and supplied listing link. Retraction deletes the stored photographs and their fingerprints; the certificate page then shows that it was retracted, and the capture record without photographs remains. Ordinary matching remains confined to your own workspace; it is separate from public certificate access. Do not photograph personal documents or information you do not intend to disclose.

Section 17 explains the difference between workspace matching and a public camera certificate. A match does not prove copyright ownership or wrongdoing, and a missing match does not prove originality.

We must keep personal information only for as long as necessary for its stated purpose, subject to applicable legal obligations. We consider the purpose, sensitivity, account or service relationship, disputes, security needs, agreements, and privacy requests. We do not treat possible usefulness for unspecified future models as a reason for retention.

Periods currently implemented

The current service has the following specific limits. Scheduled deletion normally runs hourly, unless a different schedule is stated below:

• Ended sign-in sessions, including their network address and browser description, are deleted 90 days after the session ends. They support account security review;
• Content-free request records are kept for 90 days from the request, to measure usage, spot outages, and flag unusual activity. They do not include the prompt, photograph, device identifier, or generated answer;
• Full monitoring run and outcome records, including Orbit drafts and reported final listings, are deleted after 30 days, to limit the content kept for quality review;
• Customer-held encrypted request and response logs are deleted after 30 days. They support your own review and any support access you choose to grant. Your master code protects them as described in the security section;
• Ask PCIFIC questions it could not answer are deleted after 30 days, so you can identify gaps in your documents. Ask PCIFIC chats are deleted 30 days after the last question. Questions kept on Full monitoring are deleted after 30 days;
• AI model attempt notes used to investigate provider failures are deleted after 7 days. Saved answers used to return the same result when a request is retried are deleted after 24 hours;
• Temporary Orbit listings and Safeguard reviews expire 30 minutes after their last change, and uploaded tool photos 30 minutes after upload or after the listing or review using them finishes, whichever is later. These records let the tool finish and return its result. A clean-up runs every minute. Any separate Full monitoring copy follows the 30-day period above;
• Encrypted request and response contents are inaccessible after 30 days and removed by the hourly privacy clean-up. Deleting a business also deletes its stored contents;
• Embed sessions last 60 minutes unless your business chooses between 5 and 120 minutes. Expired sessions are deleted when your business next starts an embed session. Key requests from coding tools expire after 30 minutes unless approved, and 60 minutes after approval, and are then deleted. Webhook events are deleted after 30 days;
• Rate-limit records for PixelTrace capture and certificate pages, which include the full network address, are deleted when their window of up to 10 minutes ends;
• Email codes expire after 10 minutes, passkey checks after 5 minutes, and invitations after 7 days. Expired codes and passkey checks are deleted hourly. A record of each invitation, including the invited email address, is kept while the business exists; and
• Unfinished PixelTrace camera captures are deleted after their expiry by a clean-up that runs every minute. Test groups and their photos are deleted 24 hours after the group starts, and demo groups a day after publication. Completed live photo certificates, their photographs and fingerprints are kept until the certificate is retracted, unless the business chose not to keep photos. After retraction, the capture record without photographs remains.

Records without a fixed period

The following records do not currently have an automatic age-based deletion period. This is a limitation of the current system, not permission to keep personal information indefinitely:

• Security history of sign-ins and account changes, including email address, full network address, and browser description. Anonymous failed sign-in records are deleted after 24 hours;
• The email log of messages we sent, including the recipient, subject, and some message details such as a new sign-in's network address or a support reply. Codes and links are removed from it;
• Feedback and support messages and our replies, until the account is deleted;
• Invoices, the credit ledger, and daily usage totals, which are kept for accounting;
• Records of actions taken by PCIFIC staff and of privacy setting changes, which are kept so they cannot be quietly altered;
• Ask PCIFIC documents, until your business removes them;
• Checkup certificates, including test certificates;
• Completed PixelTrace capture records, as described above; and
• Server logs, which can include technical details such as a phone's browser description.

Financial records, Ask PCIFIC documents, certificates, and photo fingerprints have their own purposes and are not governed simply by a tool's request-log setting. Contact us for the retention arrangement applicable to your service or to request deletion or restriction. A change of privacy tier applies to subsequent requests and does not erase records already stored.

Local browser data can remain until overwritten, cleared, or removed. When an account is deleted, its sessions, passkeys, codes, feedback, and memberships are deleted with it, but security history, the email log, staff action records, and invoices remain. Any lawful exception for accounting, claims, or security must be limited to what remains necessary. Independent providers may have separate obligations.

We use technical and organisational measures designed to protect against unauthorised access, accidental loss, alteration, and disclosure. Measures include secure authentication, two-step verification, role-based access, rate limits, encrypted connections, protected credentials, and records of sensitive administrative actions.

Business records are protected by database access rules that limit each request to the records of the business making it. A separate staff console uses individual verified staff identities and access permissions. Separation limits access; it does not itself mean the hosting provider cannot process the stored information.

Customer-held records use a master code created in your browser, which is not sent to PCIFIC. Each request is encrypted under its own key. A support code can open only the requests whose keys your browser wrapped for that code. Losing the master code makes those logs unrecoverable through PCIFIC.

No website, API, email service, or internet transmission can be guaranteed completely secure. Protect your credentials, restrict integration access, and do not send unnecessary sensitive information.

PCIFIC is based in the United Kingdom and our published database hosting arrangement is in London. That does not make every request UK-only: AI hosts, research services, email services, identity providers, and your own connected provider may process information in the United States, European Economic Area, or other countries. Our current Azure model endpoints are in the United States.

Where data protection law requires a transfer safeguard, the processing must be covered by an appropriate mechanism, such as an applicable adequacy decision, the UK International Data Transfer Agreement, the UK addendum to European standard contractual clauses, or applicable European standard contractual clauses, together with any required assessment and supplementary measures.

A data processing agreement alone is not necessarily an international transfer mechanism. Contact us for the safeguards and provider arrangements applicable to your service, or to request relevant information subject to necessary confidentiality and security redactions. This notice is not a representation that every optional provider your business connects has the same location or contractual protections.

PCIFIC Business is intended for business users, not children. Account holders must be legally able to enter the relevant business arrangements. We do not knowingly seek children's personal information for ordinary business use.

An integrating business is responsible for identifying any additional requirements where its own service is used by children. Do not submit children's personal information to general AI tools. If you believe information about a child has been supplied improperly, contact us so we can investigate and take appropriate action.

Depending on applicable law and the circumstances, you may have the right to:

• Request access to your personal information and information about its use;
• Correct inaccurate information or complete incomplete information;
• Request deletion or restrict certain processing;
• Object to processing based on legitimate interests on grounds relating to your situation;
• Object to direct marketing, including related profiling;
• Receive a portable copy of certain information;
• Withdraw consent where we rely on it; and
• Receive protections concerning certain solely automated decisions with legal or similarly significant effects.

Objections and withdrawal of consent

Where we rely on legitimate interests, we will stop processing following a valid objection unless we demonstrate compelling legitimate grounds overriding your interests, rights, and freedoms, or the processing is needed for legal claims. For direct marketing, you can object at any time.

Withdrawing consent does not affect the lawfulness of processing before withdrawal. It does not prevent a separate use supported by another valid basis, such as keeping necessary accounting records.

Requests and complaints

Contact support@pcific.co.uk. You do not need special wording or a particular subject line. We may ask for proportionate information to confirm your identity and locate records. If your request concerns information your business submitted as controller, we may direct it to that business and assist it under our agreement.

UK users can complain to the ICO. Users in the European Economic Area or Switzerland may also have complaint rights with their local supervisory authority. You do not have to contact us before complaining, although we welcome the chance to help.

We respond within the period required by law, generally one month under UK and European data protection law, subject to applicable identity checks, clarification rules, and permitted extensions. If an extension or lawful limitation applies, we will explain it.

Some browsers offer a do-not-track signal. We do not currently implement a standardised response to that signal. This does not replace your privacy rights or any required storage choices. Where applicable law requires recognition of a particular privacy or opt-out signal, we must comply and update our disclosures accordingly.

We may update this notice when the service, providers, legal obligations, or processing practices change. The date at the top identifies the latest revision. Where required, we will give additional notice of material changes before new processing begins.

An updated notice is not a substitute for a valid lawful basis, a required customer agreement, or consent. Continued use does not by itself mean you agree to new personal-data processing. A new notice does not automatically authorise reuse of historical requests collected under a no-training commitment.

For questions, concerns, or privacy requests, contact:

• Pcific Marketplaces Limited
• 71-75 Shelton Street
• London WC2H 9JQ
• United Kingdom
• Email: support@pcific.co.uk

You can review profile and security settings, manage sessions, passkeys, and API keys, and use the data-download controls in Settings. Workspace owners and administrators can include shared organisation data; other members receive their own permitted personal records.

A download excludes credentials and cannot include content the service never stored. Customer-held logs remain encrypted unless you unlock them in your browser with your master code. A technical download is not a substitute for your legal right to ask for access to personal information.

Contact us to request correction, deletion, restriction, or other rights. Describe the account, feature, or information concerned without sending unnecessary sensitive material. We may need to verify your identity and coordinate with the integrating business or relevant providers.

Accounts and businesses are deleted by PCIFIC staff on request; there is no self-service delete button. An owner's account can be deleted only after their business is deleted. Deleting a business deletes its records and photos, but its members keep their own accounts. Removing a member revokes the API keys they created and does not transfer the owner's resources to that person. Closing an account, leaving an organisation, clearing browser storage, revoking support access, changing a privacy tier, and retracting a public photo certificate are different actions. One does not automatically perform the others.

Any necessary retention for accounting, legal duties, claims, or security must be assessed separately. If we cannot fulfil all or part of a request, we will explain the applicable reason and complaint rights.

Scope and purpose

This section explains the additional controls for licensed business tools, embeds, coding tool connections, webhooks, and photo matching. Read it together with the rest of this notice. This business notice does not govern the separate PCIFIC Safeguard browser extension simply because the licensed tool shares the Safeguard name.

Tool privacy tiers

A workspace owner or administrator can select an available privacy tier for each tool. Operational only is the default. Current choices are:

• Operational only: basic request records and encrypted sent and returned contents for 30 days, without listing-quality monitoring. Separately, Ask PCIFIC keeps the text of questions it could not answer for 30 days, so you can see what your documents are missing;
• Full monitoring: request records plus permitted quality signals. For Orbit, this includes the first draft and the final listing reported as published. Encrypted sent and returned contents are also kept for 30 days. Photos and file contents are excluded from logs. This does not permit model training. Ask PCIFIC keeps the text of questions it could not answer for 30 days, so you can see what your documents are missing;
• Customer-held logs: encrypted request, response, error, and step records in a separate store. Device identifiers are hidden before storage, and photo and file uploads are not kept. Ask PCIFIC conversation content is excluded from these encrypted logs. Separately, Ask PCIFIC keeps the text of questions it could not answer for 30 days, so you can see what your documents are missing. Your master code opens the logs; a separate support code can cover only specific existing requests until expiry or revocation; and
• True ZDR: no request-content logs and no unanswered-question list, arranged with PCIFIC under a signed agreement and enabled by staff. Content-free request metadata still remains, Ask PCIFIC chats are kept while chat history is on, and answers saved for safe retries are kept for 24 hours. Separate records required for a feature, including PixelTrace fingerprints and certificates, are not erased by choosing this tier.

Changes apply to subsequent requests and do not delete earlier records. The privacy setting controls PCIFIC's request logging, not the integrating business's own storage or every outside provider's systems. Do not interpret a tier as preventing transient processing of the content needed to provide a requested result.

PixelTrace matching

PixelTrace compares photos only with your own workspace's registered photos. Your registered fingerprints are never offered for matching to any other business, and other businesses' fingerprints are never searched for you. A match is a cue for review, not proof of ownership, fraud, or wrongdoing, and a missing match is not proof of originality.

A public camera certificate is separate from matching: a person holding its code can see its published photos.

Embeds and capture

An embed shows a PCIFIC tool on your business's website using its branding. It uses a short-lived session tied to that website's address instead of exposing a long-lived API key. We process the input and return results for the business providing the journey. Its own privacy notice also applies.

PixelTrace certificate capture intentionally keeps processed photos for a public dated record. Using a phone camera is not a promise that photos remain only on your device.

Ask PCIFIC item lookup and webhooks

If your business sets up an item-lookup address, Ask PCIFIC calls it with the item identifier and any buyer account identifier your integration supplied, to fetch current listing details. The buyer account identifier is not passed to the AI model. Lookup answers are cached in server memory for as long as your service allows, up to 48 hours.

Webhooks send event notices to the address your business sets, signed with a secret we keep. Notices contain identifiers and status, not tool content. Event records are deleted after 30 days.

Coding tools

A coding tool can ask for a test API key through key link. A manager in your business approves the request in the dashboard, and the key is delivered encrypted so only the requesting tool can read it. We keep the suggested key name, where the tool will save it, who approved it, and the encrypted delivery until the request expires as described in the retention section. Information returned to that tool is also processed under its own arrangements. Revoke a key when no longer needed.

Customer responsibilities and support

Your business must tell its customers what the integration sends to PCIFIC, avoid unnecessary personal information, choose settings consistent with its obligations, and assess any public certificate disclosure. Workspace acknowledgement does not supply consent on every customer's behalf.

Requests for privacy help can concern accounts, tool records, encrypted logs, Ask PCIFIC documents, device checks, photo fingerprints, or published certificates. You are not required to identify the internal model or database. Contact support@pcific.co.uk and explain the feature or record you mean.