Privacy information
Your business data should remain understandable and controlled.
This page explains the information used by Zarak Client Portal client accounts and Zarak’s owner workspace. Client access is linked to the services agreed with Zarak.
Sign-in and account security
Clerk provides our sign-in and session management. It processes your account identity, email address, chosen sign-in method and security/session information to authenticate you and protect your account. If you choose Google or Apple, that provider handles its own sign-in and shares the identity details you authorise. Zarak stores the linked account identifier and verified contact details needed for your portal access. Zarak does not receive your Google or Apple password. Necessary cookies or device storage keep your session signed in. Contact Zarak about access, correction or deletion of your portal account.
Business contact details
After payment, onboarding collects your contact name, business name, phone number, business/contact address and business brief. These details are required to complete onboarding and are stored with your client account so Zarak can identify your business and contact you about your website. You can update your contact details and address in Account and your project materials in Requests & photos. They are visible to your authorised client account and linked Zarak team, alongside your account email. They do not replace your billing address or change your saved payment agreement.
Website requests and photographs
Your messages, request history, photo-review decisions and website-preview approvals are stored with your project. Photographs are held in private Cloudflare R2 storage and are available only to the authorised client and linked Zarak team through authenticated routes. Photos are resized and saved as JPEG; location and other application metadata is removed. Keep original files separately. Uploading or approving a photograph does not automatically publish it, send it to AI, or copy it to Google Drive or OneDrive. Zarak may download approved photographs to prepare your agreed website changes. Contact lenin@zarakmarketing.com to request removal of uploaded materials, subject to necessary project and legal records.
Project messages and phone alerts
Each linked project has a private conversation shared by its client account and the Zarak team. Camera photographs and selected files are shared only when you tap Send. Message attachments are stored privately with the project; photographs are converted to JPEG with application metadata removed. Documents retain their contents. PDFs can be viewed inside the portal on your device; other documents can be saved and opened in a compatible app. PDF viewing does not activate embedded scripts or actions, and files are not sent to an external document-viewing service. Unsent upload reservations expire and are removed after 24 hours. We store messages, their sender and recipient, timestamps and read status with the project. Opening visible messages marks them read. You control phone alerts in your device’s notification settings. Encrypted device notification tokens and delivery records are used with Expo and Apple or Google push services. Chat alerts contain a generic notice, not private message text or contact details. Preview and launch alerts describe the service milestone. A team announcement may include its opening text on the phone lock screen only when Zarak explicitly chooses that option. Delivery depends on your device settings and connection. Signing out ends alerts for that session; turning phone alerts off does not delete your project messages.
Unpaid enquiries and delivery records
Unpaid website enquiries close after their communicated 30-day payment window and leave the active work list. Existing unpaid clients receive a fresh notice and full window. Closing an enquiry does not delete your sign-in account. We retain necessary agreement, payment-attempt, notice and audit records for reconciliation and applicable legal obligations or claims; account erasure is a separate verified process. Website delivery records include your preview and domain approvals, launch status, and service email and notification delivery results.
Deleting a message
You can delete a chat message you sent for both people. Its text and attachment disappear from the conversation. Unreported text is cleared and its file is queued for removal. A minimal record of the deletion remains. Existing safety reports, recovery backups and copies already saved by a recipient may remain.
Message safety
You can report messages and attachments or block a sender from the conversation’s Safety controls. Reports store the message reference, your account, reason, time and review outcome for the linked Zarak team to investigate. Reported content is hidden from the person reporting it; authorised Zarak reviewers can still inspect the evidence. Removed content is hidden from conversations but may be retained with the report for investigation and necessary records. Blocking stops project messages and requests between the current participants while leaving project and payment records available. Contact info@zarakmarketing.com for help or questions about retained reports. A limited text filter checks for some harmful phrases; messages and files are not sent to an AI service for moderation.
Website projects and payments
Private project records contain the agreed scope, terms, upfront payment amount, invoice reference, delivery updates and Revolut payment references. We record who accepted the project and when payment was confirmed, either through server verification with Revolut or a receipt recorded manually by Zarak. These records are restricted to Zarak and the designated linked client account. Revolut handles card entry through its checkout; Zarak Client Portal does not store raw card or bank details. Integrated checkout records provider order references and, when you authorise recurring payments, Revolut customer and saved-payment-method references, your consent and billing dates. Website Care requires explicit recurring-card authorisation at checkout; existing saved agreements retain their terms.
Who is responsible
Zarak Marketing Ltd operates Zarak Client Portal. The registered office is 18 Albert Gate, Middlesbrough, North Yorkshire, TS5 6JA. Privacy questions can be sent to lenin@zarakmarketing.com.
Information used
Depending on the features you use, this may include account identity, business and website details, enquiries, messages, uploaded photographs, approvals, audit records and payment references. Optional reporting separately uses the Google account and website data described below. Beta issue reports also record the page, browser/device description and viewport size you submit so faults can be reproduced.
Connected services
Clients do not need to connect Google or social accounts to use website projects, messages or requests. Clients invited to connect reporting accounts choose whether to authorise each provider. Zarak Client Portal uses Cloudflare for hosting and protected storage of workspace records, reporting data and encrypted connection tokens. Business administration and Zarak’s own connections remain restricted to the authorised Zarak owner. Zarak does not ask you to hand over a provider password.
Optional Google website reporting
Zarak Portal Reporting is the Google connection used by Zarak Client Portal. The Zarak owner and invited clients can separately authorise read-only Google Analytics and Search Console reporting. Google supplies the authorised account’s email address and identity, available website properties or verified sites, and reports for the selected website. Analytics supplies aggregate active-user counts; Search Console supplies search clicks and impressions with their reporting dates. We save the selected resource, these dated figures, connection status and encrypted access and refresh tokens so reports can update while the app is closed.
Client reports are available to that authorised client workspace and its linked Zarak team for the agreed website reporting service. They are not shared with other clients. Zarak’s own reports remain in the owner workspace. These permissions cannot edit Google properties, publish content, change advertising campaigns or read email. The retired website assistant does not receive this data, and it is not used to train AI models, sold, or used for personalised advertising.
Google data is handled under the Google API Services User Data Policy, including its Limited Use requirements. You can revoke access in Google Account connections or ask Zarak to disconnect the service. Revoking access stops future authorised retrieval; it does not automatically erase reports already saved in the portal. Contact lenin@zarakmarketing.com to request deletion of saved reporting data and connection records. We process deletion requests within 30 days, subject to necessary legal or security retention; copies in recovery backups may remain until their retention period ends.
Zarak business email notices
The separate Zarak Portal Email connection is restricted to Zarak’s business account and requests permission to send email only. It sends website enquiry alerts and billing notices through Gmail. These notices can contain the contact details, enquiry text, payment references and service dates needed for the notice. It does not authorise reading the business inbox, and clients are not asked to connect their Gmail to receive the website service.
When enabled by Zarak, Loops delivers website-launch and invoice-window service emails. It receives the recipient’s email address, the notice content and relevant project links and service dates. These emails do not add you to a marketing mailing list. Email providers process delivery information; contact Zarak about access or deletion of associated records. Private chat attachments and passwords are not included in these automated notices.
Why information is used
Information is used to provide the workspace and authorised website reports, manage approved work, maintain security and audit records, support billing, and respond to requests. Marketing use requires an appropriate basis and choice.
Stored records
The website assistant has been removed and its retired task and chat records have been deleted. Client account, project, photograph, payment and necessary security records remain protected. No new assistant requests are processed. You can request account deletion through Info & support or our public deletion page. Requests go to Zarak for manual processing within 30 days. We confirm completion by email. Necessary financial and legal records may be retained; we will explain any retention. Contact Zarak for data export requests.
Control and security
Client workspaces have separate access permissions from the Zarak owner workspace. Connection tokens are encrypted at rest. Client accounts can access only their authorised projects, messages, materials and reports. Google reporting does not publish content or change Google accounts.
Your choices
You can ask about access, correction, deletion, restriction, objection, portability or provider disconnection where applicable. Email lenin@zarakmarketing.com without including secrets. We may need to verify your identity. Deletion is not automatic and some records may need to be retained for legal obligations or claims. You can also raise a data-protection concern with the Information Commissioner’s Office.
Earlier pilot records
The existing commitment for beta feedback and its diagnostic device/browser metadata remains: deletion within 90 days after the beta closes, unless a shorter deletion request applies or a longer period is required for a documented security or legal reason. Product records and uploads are not automatically erased by signing out or disconnecting a provider. Contact Zarak about retention or deletion of your account records.
Cookies and tracking
Necessary storage supports secure sign-in, authorisation and saved privacy choices. If Google Analytics 4 is configured, it remains unloaded until you allow Analytics and is limited to public product pages. No advertising tracker is currently active. See the cookie information and use the persistent control to change or withdraw optional choices.