Last reviewed: 2026-11-18
Login bot protection
Where enabled on an authentication form, Cloudflare Turnstile processes security signals including your IP address, browser details and the page origin to distinguish automated traffic from legitimate requests. We use this check to protect accounts, not for advertising. We send the resulting short-lived verification token to Supabase for validation. Our integration does not send your password or form content to Turnstile. Cloudflare may process security signals internationally under its Turnstile Privacy Addendum (https://www.cloudflare.com/turnstile-privacy-policy/).
Encrypted backups
Automatic backup jobs temporarily process account and website records on GitHub Actions and save encrypted archives in Cloudflare R2. These services may process data outside your country. Backup copies have a separate retention cycle and are not instantly erased by account deletion. Necessary restoration must reapply completed deletions and restrictions before restored data is used.
Domain and email testing
OpenSRS provides domain and hosted-email sandbox services. For enrolled test websites, the integration processes the domain, registrant and contact details, and mailbox settings submitted for the test. Paid production provisioning remains disabled.
Seller verification and review records
When the business owner asks to enable selling, we collect the legal business name, country and legal form, commercial registration and licence numbers, licensed activity, licence expiry, representative name and role, and the accuracy and authority declarations. We use these details to assess eligibility to sell on Webinku, reduce misuse and keep review decisions accountable. We record application revisions, decision reasons, dates, the reviewer account and verification references, including separate payment-provider approval references and the connection reviewed. The owner can see their application, decision reasons and review history. Internal evidence references and reviewer identities are restricted to authorised platform review and technical administration; other businesses, ordinary employees and designers cannot read the application. Visitors receive only the selling-availability result, not the verification records. These records are not automatically sent to AI. This flow does not collect Civil ID or passport scans or identity-document numbers; submit identity evidence directly to your payment provider when it requests it, under its own privacy notice. Do not place identity documents in website images or free-text fields. Review records have no automatic age-based deletion in this version and follow the account-record access, correction and deletion process below; we explain any necessary retention when handling a request. Business review is separate from payment-provider KYC and does not certify government approval or guarantee against fraud.
Exit requests and optional feedback
We keep the website/account reference, confirmation date, deletion progress and any optional reason you submit so we can complete and audit the request. Cancellation and plan-change feedback is optional. Do not include passwords or sensitive documents in a reason.
Free account deletion
Deleting your Webinku account is free, including during the preview. No paid plan, account upgrade or deletion fee is required. Use Website settings or Personal profile to review and confirm deletion without emailing support. Deleting one website preserves your other websites; deleting the account removes all websites you own. Cancel renewing Webinku subscriptions and disconnect or move connected addresses before confirming. Save any exports first. A recent sign-in and explicit confirmation are required; a reason is optional. Cleanup runs in the background with a progress page and automatic retries. Domain registrations and third-party services are managed separately. Necessary billing and security records and backups may follow separate retention rules. Deletion is not an automatic refund. Platform staff responsibilities and resources shared with another owner must be resolved before account removal.
Optional Apple sign-in
When available, you may choose Sign in with Apple instead of a Webinku password. Apple supplies an account identifier and a verified email, which may be an Apple private relay address if you choose Hide My Email. Apple may share the first and last name you approve on your first authorization only. We verify the Apple identity through Supabase, use the email to identify your account and save available name fields as editable profile information without replacing a name already supplied. A repeat sign-in may provide no name; you can add it yourself. Apple and Google sign-in do not supply your postal address or phone number. These remain optional private profile fields or are requested separately when needed for an order. We do not request your Apple password, iCloud files, contacts, messages, payment cards or location. Signing in does not accept terms for you, join every business, grant staff access, activate a subscription or publish your profile. Use the same sign-in method for an existing account; a private relay email may identify a different account from your Google email. We do not merge accounts based on names. Provider tokens are used only for sign-in verification and are not retained in browser storage. The signed-in Webinku session uses the necessary storage described in our Cookie Policy.
Optional Google sign-in
You may use Google instead of an email and password. Google supplies a verified email and, when available, your name and profile photo to our authentication provider, Supabase. We use these to identify your account and prefill your name; you can review the name before saving your customer profile. This does not provide access to your Gmail, contacts or calendar, and we do not request birthday or company information from Google. New accounts still accept the relevant business or customer terms. A temporary sign-in return context and security verifier are held in the initiating browser tab; the return context expires after 15 minutes. Signing in does not register you with every business or grant staff, business-owner or paid-plan permissions.
Business employees and permissions
The business owner supplies each invited employee’s name, work email, optional department and assigned role. We allocate a business-specific employee number and retain invitation expiry, acceptance or revocation and security audit records. The owner shares the private invitation link; invitations are not emailed automatically. Employees use their own verified Webinku account. Their assigned role determines access to website drafts, orders, invoices or other permitted tools within that business. It does not disclose another business’s records. Removing access preserves business and audit history; these records have no automatic age-based deletion and follow the account-record retention process below. A pending private staff invitation is held in the current browser tab until accepted, declined or the tab session ends.
Product-photo suggestions
When you choose this optional feature and confirm, Webinku sends the selected product photo and facts you enter to OpenAI to suggest an editable title, description and category. The AI copy of the image is re-encoded without metadata. Normal product uploads have public asset URLs, including while the product is a draft; do not upload confidential documents. The suggestion is not saved to the product until you apply it and save the form. Check all claims yourself; the feature does not establish sizes, materials, ingredients, safety, prices or availability from appearance alone. Requests use the existing AI allowance and retention rules below.
Receipt assistance
You can enter an expense manually or keep an original document in the private financial library. With your separate confirmation, the selected document and note are sent to OpenAI to suggest editable details. The supported library formats are PDF, JPEG, PNG, WebP, TXT and CSV, up to 4 MB per file; AI extraction is available only for supported inputs and within your allowance. Review the supplier, invoice reference, dates, currency, amounts and classification. Keeping a file does not itself record an expense: confirm the reviewed record before posting. Exact-file and supplier/reference checks help prevent duplicate entries; equal prices alone are not duplicates, and altered or numberless invoices still need your review. Website sales must not be uploaded again as expenses. Originals and saved details follow the private-document and retention rules below. AI output is not proof of payment, an audit or an official XBRL filing. Keep your own backup of source documents.
Website setup and draft images
Website setup is available after sign-in. Your submitted business name, activity, description, language and design preferences become part of your website draft. Guided setup does not send the brief to AI. Choosing AI setup requires a separate choice to send the brief and starting design to the assistant; the browser handoff described in our Cookie Policy is valid for 30 minutes. Draft page text is not published automatically. Uploaded and AI-generated website images have public asset URLs, including before page publication. Do not use confidential or personal information in image requests or website images. Menu QR images are generated locally without an external QR provider or scan tracking.
Articles and public author information
The business chooses the article text, author label, category, images, image descriptions and search information it enters. Draft article text is private to the business owner; publishing makes the selected article version and its author label public on that business website. Saving later draft changes does not publish them. Unpublishing removes the article from the public website and keeps its draft; deleting the article removes its application record. Uploaded images have public URLs and may remain accessible separately, including before article publication or after an article is removed. Do not put private customer details or confidential documents in articles, author labels or images. Article records have no automatic age-based deletion in this version and remain subject to the account-record retention process below; provider backups and copies already collected by visitors or search engines are separate.
Service appointments
When you confirm an appointment, you agree to share your name, email, chosen service and appointment time with the selected business to manage that booking. We record the language, status, time of acceptance and disclosure version. This does not create a marketing subscription or share your appointment with other businesses. The form does not request medical history, an address or payment-card details. The business owner can see and manage its appointments. A private cancellation code lets you cancel before the appointment starts; we store its hash, a retry reference and an input fingerprint for security and safe retries. Keep the code private. Booking confirmations are shown on screen and can be printed; automatic booking email is not provided in this version. An owner can remove the customer name and email from a cancelled, completed or missed appointment after its scheduled end; the appointment time, service, status and security references remain. Cancellation or passage of time does not automatically delete booking records. Other access or deletion requests follow the account-record process below.
Designer invitations and review notes
A business owner supplies the invited designer’s email. We keep the invitation issuer, email, hashed private token, expiry and acceptance or revocation status; accepted access is linked to the verified designer account and the individual business. The owner shares the invitation link; it is not emailed automatically. A pending invitation token is temporarily kept in that browser tab’s session storage during sign-in and is removed when accepted or declined, or when the browser session ends. Designers can access the invited website’s draft, catalogue preview and image uploads. They cannot access private customer records, orders, invoices, payment credentials, subscriptions or business management through the designer role. Review and handover records contain the designer’s notes, the owner’s feedback, the relevant draft revision and review status; the owner and the relevant designer can view those notes while authorised. Avoid personal customer information and secrets in notes. Removing access or finishing handover stops designer access but does not delete invitation or review history. Those records have no automatic age-based deletion in this version and follow the account-record retention process below.
Unified customer accounts
A Webinku customer account works across participating business websites. Webinku manages the shared login, profile and private address book. Signing in does not disclose your account to every business. Choosing Register with a business shares your name and verified email with that business; placing an account order also registers that relationship. Only the contact details and delivery address used for an order are shared with its seller. Sellers cannot access your address book or orders at other businesses. Previous guest and imported orders are not automatically claimed by matching an email. You can edit your profile, delete saved addresses, and remove a business registration in your account; existing order records remain with the seller. Use Personal profile for account deletion; contact hello@webinku.com for other access or correction requests. There is no shared product marketplace or automatic marketing subscription.
Contact messages and receipts
Submitting a contact form shares your name, email, subject and message with the selected business so it can respond. This does not subscribe you to marketing. Messages and invoice snapshots stay private to that business and authorised account holders. Transactional emails use fixed templates; contact acknowledgements do not repeat your message. Sales receipts contain sale details and are sent to the checkout email when provided. Daily keyed abuse counters expire after 48 hours; inbox, invoice and delivery records follow the business-record retention rules. Email delivery requires a configured provider; queued or accepted is not confirmed delivery.
Business rewards data
Joining a loyalty program records a separate membership, points balance and points history for that business. That business can see its own member name, email, balance and activity. Another business cannot see or redeem these points. Loyalty membership does not subscribe you to marketing. Points records support purchase rewards and refund reconciliation and are retained with the relevant order records. Webinku runs this feature without an external loyalty provider.
Who handles your data
Webinku is operated by شركة ويب ان كو لتصميم وادارة المواقع الالكترونية, a Kuwait one-person company, commercial registration 510486, commercial licence 2024/25537. Location: Kuwait. Contact hello@webinku.com for privacy requests. We determine how account, support and security information is used. A merchant determines how its customers’ order and marketing information is used; Webinku supplies the platform. Contact that merchant about its products and customer records, or contact us for help identifying it.
Webinku support
The automated help guide matches reviewed guidance without sending your question to a paid AI model. A human support request saves the summary you review, attempted steps and your contact details in the private support conversation. Requests for a real agent require first name, last name, email and a contact number. The team reviews the reason and replies by email or in the signed-in conversation, or calls when needed. These contact details are not displayed publicly. Main-website help can prepare an email draft to hello@webinku.com: nothing is sent until you send it from your email app. These details are used for support, not marketing. The owner receives a minimal Resend email with the request category and a link to the authenticated admin conversation. Support messages and delivery records follow the account-record retention rules. The separate owner AI adviser is not active in this release; it does not receive customer messages automatically.
Information and purposes
We use your email, authentication credentials and preferred language to create and protect an account; your business name and content to provide the builder; and support messages to answer requests. Signup records the version and time of your terms acceptance and adult/business-authority declaration. We do not request a date of birth, civil ID, passport, bank password or card PIN for normal account setup. Storefront image uploads have public asset URLs, including in drafts: do not place private documents there. Use only the designated private financial-document or product-artwork feature for the relevant files, under the separate disclosures below.
Optional delivery location
When you choose Use my location and allow browser access, Webinku sends your coordinates to Google Maps to suggest a delivery address. No name, phone or cart is sent for this lookup. Review and correct the result; it may not identify your building or apartment. The shop receives your confirmed address and optional pin with your order. We do not keep a shared address-lookup cache or use these coordinates for marketing. You can remove the pin or enter the address manually. Google may process information internationally under its privacy policy (https://policies.google.com/privacy); the Google Maps terms (https://maps.google.com/help/terms_maps/) also apply.
Customers and optional choices
Checkout needs a customer name and phone for fulfilment; email is optional, and a delivery address is requested only for delivery. Order items, choices, prices and payment references support fulfilment and reconciliation. Customers enter card and bank authentication details on the payment provider’s checkout, not in Webinku content fields. A merchant separately enters its gateway integration credentials in the authorised Payments settings; these are held in encrypted server-side storage and used for that website’s payment connection. Do not send them in chat or publish them. Newsletter registration requires a separate marketing choice and can be withdrawn. Optional visitor analytics remain off unless allowed in Privacy choices; rejecting them does not stop shopping or account access. Live payments remain disabled during private testing.
Service providers and international processing
Supabase provides authentication, database and image storage; the platform database is hosted in Frankfurt, Germany. Vercel hosts the application and may process traffic and security logs internationally, including in the United States. Resend delivers account verification and recovery messages through Supabase and, when configured, transactional receipts, sale notices and contact acknowledgements. OpenAI processes inputs you choose to send for the relevant AI feature and website text for automatic translation when enabled. Cloudflare provides login bot protection and encrypted backup storage; GitHub Actions runs the encrypted backup workflow. OpenSRS provides the enrolled domain and email sandbox. The existing Lemon Squeezy subscription integration is for testing; a live platform payment provider has not been activated. A merchant payment connection processes checkout data only when that connection and selling are authorised; saving its settings does not enable live payments. External links have separate privacy practices. We do not install advertising pixels or sell personal information. We do not promise Kuwait-only storage. Google provides optional Google sign-in and, where configured, address lookup after you request location access. Its role and the limited data sent are described in the feature-specific sections. These services may process data internationally under Google’s privacy policy (https://policies.google.com/privacy). Provider names are transparency disclosures, not endorsements or claims of certification.
Website translation
Automatic Arabic/English translation sends the visible text you save (page headings, descriptions, labels and product text) to OpenAI. It does not send customer lists, payment credentials, prices, inventory, analytics or image files. You can disable it in the editor and edit both languages yourself. Source text and translations are saved with your website. Content edits update generated translations when automatic translation is enabled. Your manual corrections are preserved and marked for review if the original changes; you can explicitly request a new translation. Visitors switch between saved languages without an AI request. Review names, meaning and claims before publishing. OpenAI processing and retention are described below.
AI website design and generated images
With your separate choice, the design assistant sends your messages, recent conversation and selected page or whole-site draft content to OpenAI to prepare text, translations, layouts and image descriptions. This design context excludes private customer/order records and payment credentials. Image descriptions and a hashed account safety identifier go to OpenAI for image generation. Generated images are saved to website image storage with public URLs even while the page is a draft; undoing an edit does not by itself delete an image file. Asset identifiers, source/output hashes, sizes, status and usage/budget records support access control, duplicate prevention and limits and follow account-record retention. Changes apply to your editable draft; saving and publishing are separate actions. Review accuracy, rights, product claims and visual suitability. Generated content may resemble other outputs and is not guaranteed exclusive or legally cleared. Do not present generated people or illustrative product images as actual staff, customers or exact products unless that is true.
Private financial documents
Business owners can save original invoices, business documents and reviewed details in a private library. Files remain with the website until its deletion completes, subject to applicable record-retention requirements and backup expiry. Optional AI extraction sends only the selected document and note to OpenAI with your confirmation. Extraction is a draft; verify the supplier, reference, dates, currency, amounts and classification before saving. Exact-file and supplier/invoice-reference checks help prevent duplicates but cannot reliably identify every rephotographed, edited or numberless invoice.
AI privacy
Before sending a message, you choose whether to use the OpenAI-powered assistant. Do not include personal customer records, health information, passwords or payment secrets. Optional store context includes store details, up to 30 products and a summary of recent verified payments. Business review has a separate optional choice to share selected-period receipt and expense totals, monthly amounts, expense category totals, reconciliation counts, trial-balance import status and up to 10 product names, stock levels and paid-unit counts per review list. Customer records, expense descriptions and trial-balance account names and values are excluded from this generated business summary. Conversation text is held in the current browser view; our application does not save a chat history in its database. We request that OpenAI not store Responses as application state; this is not zero retention. Provider abuse-monitoring logs may retain content for up to 30 days by default, or longer where law or safety requires, subject to its policies. API content is not used for model training by default.
Customer website AI and finance records
A merchant may publish an optional customer assistant. Visitors choose AI chat before sending messages to OpenAI alongside limited public website content; it has no access to private orders or customer records. The same AI retention limits apply. Chat is kept only in the current browser view by our application. For abuse prevention we keep short-lived request counters with a daily keyed hash of the network address, not the raw address or chat text. Counters are removed by daily cleanup after their day becomes more than one day old. Finance expenses and trial-balance imports are private owner records stored for accounting preparation. Voiding an expense preserves its original entry and correction reason. These records are retained under the account record rules below. Do not upload personal identifiers, bank secrets or health data in accounting descriptions.
Custom product artwork
When you personalize a product, the seller receives your exact text and confirmed image with the order. Uploaded images are stored privately and may be accessed by authorized order staff. Images are converted to lossless WebP and stripped of embedded metadata; keep your original file. Unordered uploads expire after 24 hours and are removed by scheduled cleanup. Ordered artwork follows the order-record retention and deletion rules. Only upload material you have permission to use; do not upload identity documents or unrelated sensitive information. No AI processing or automatic printing is performed by this feature.
Checkout recovery and security
To recover an interrupted checkout without creating another order, we retain a hash of its random reference and an input fingerprint linked to the order. We do not duplicate contact details in that record. Temporary abuse counters use a daily keyed hash of the network address, not the original address. Hourly cleanup removes checkout counters older than 24 hours. Payment checks retain status, references and essential verified amounts, not card details or full provider responses. These records follow the account and order retention rules below.
Retention
Account and merchant records remain while needed to provide the account and resolve disputes, subject to applicable record-keeping obligations. Use Personal profile or Website settings for self-service account or website deletion. Other privacy requests, including copies and corrections, remain available by email. Necessary billing and security records may be retained separately; deletion progress is shown in the app. Optional analytics events expire after 90 days through daily cleanup; their browser identifier expires after 30 minutes or when you withdraw consent. Consent preferences expire after 180 days. Provider logs and backups have separate retention schedules; deletion may not immediately remove backup copies. No indefinite retention is justified solely by this policy.
Your choices and rights
Write to hello@webinku.com to request access, correction, a copy, deletion, restriction or to object, as applicable to your location and our role. You can withdraw optional analytics through Privacy choices and marketing through the unsubscribe link or the merchant’s contact. Withdrawal does not undo earlier lawful processing. We do not make decisions producing legal or similarly significant effects solely through AI. Where applicable you may complain to CITRA or your local data-protection regulator. We use contractual necessity for requested services, legal obligations where required, legitimate security/service interests where permitted, and consent for optional analytics and marketing. Material changes will be described here and new consent requested where needed.
Personalised preview before sign-up
You may enter a website name, select a website type and choose a design before registering. The preview runs in your browser without a paid AI request or publishing a website. When you choose Save & continue, your choices are kept in that browser tab for up to 30 minutes to carry them through sign-in and email confirmation. They are bound to the verified account when you reach setup and cleared after successful draft creation. Closing the tab, clearing browser storage or waiting past expiry can remove them. Your saved draft is created only when you confirm setup.
Personal account profile
You may save your first and last name, phone number and personal address in Personal profile. These optional details are private account contact information, separate from website business settings and payment-provider billing records. Saving a profile does not publish it, copy it to websites or change an invoice. Do not enter passwords, card numbers or identity documents. We retain the details while you keep them in your account, include them in verified account export or deletion requests, and apply the encrypted-backup retention process described here.
Marketing, newsletters and product updates
Marketing, newsletters and optional product-update emails require an appropriate permission or other valid basis under the law that applies. They are separate from receiving the service. You can opt out of each optional category or all optional emails using the unsubscribe link or by emailing hello@webinku.com. You do not need to log in, pay or explain why. We suppress further optional mail when the request is processed and retain a minimal suppression record to honour the choice. Essential password, account-security, order, billing and legal notices may still be sent where necessary; they must not be used to disguise marketing. Marketing sending remains disabled in this preview.
Access, correction, export and deletion requests
Delete your website or account directly from Website settings or Personal profile; no routine email approval is needed. For other privacy requests, send a request from your registered email to hello@webinku.com. We use proportionate identity checks and never ask for your password or verification code by email. We aim to acknowledge requests within two business days and respond within 30 calendar days, or an earlier applicable legal deadline. If the law permits an extension, we explain the reason and expected date within the initial deadline. We provide your information through a private channel and protect other people’s data. Deletion is free, including when a billing dispute is handled separately. We explain the data removed, any specific records lawfully retained and the reason. The support email link opens a draft; the request is submitted only when you send it.
Merchant data and transfers
Webinku handles account and platform-security data for its own service purposes. For personal information that a business uploads or collects about its customers, the business normally determines the purpose and Webinku processes it under that business’s instructions, subject to applicable law. The data-processing agreement, provider terms and required international-transfer safeguards must be completed before onboarding production customer data, whether access is free or paid. A privacy notice alone does not establish a lawful transfer. These contractual and country-specific assessments remain a launch gate; private evaluation uses fictional data.
Optional passkeys
You can register a passkey after signing in to your Webinku account. We store its public key, credential identifier and the security metadata needed to verify sign-ins and manage registered passkeys. Your fingerprint, face scan, device unlock code and private key are not sent to Webinku. Your device or passkey provider performs the local verification; any syncing follows that provider’s settings. You can remove a registered passkey in your account. Removing it does not delete your account or other sign-in methods. Passkeys for the Webinku dashboard do not grant access to another business or to platform administration.

