AribifyDiscuss a project ↗

ARIBIFY / CUSTOMER INFORMATION

Privacy Policy

How your information is used.

Effective 1 October 2026 · Version 2026-10-01-backend-v1

Who this notice covers

This notice explains how Aribify handles information through this website and project enquiries. It also describes matters that must be agreed before we build an invitation or personal website. Contact us at hello@aribify.com or WhatsApp message ↗ about privacy, corrections, withdrawal or a complaint.

Aribify is the business name used on this website. The contracting party and correspondence address must be stated in your project proposal before you accept a paid project.

How we receive and manage your enquiry

When you submit the enquiry form, Aribify saves your name, email, WhatsApp contact number with country code, selected service, project requirements and relevant consent record in a restricted database. We use them to respond, manage follow-ups and prepare a proposal. We use your contact number to respond through WhatsApp; we do not offer instant telephone calls. If you message us through WhatsApp, we use the details you share to respond there. Previously supplied contact details may remain with an existing enquiry for its stated retention period. Enquiries do not subscribe you to marketing or automated WhatsApp messages. We save the enquiry before attempting an email notification, so a delivery failure does not discard it. Budget and timeframe are not collected unless a future form expressly requests them.

Your enquiry permission is separate from analytics, newsletter marketing and any project agreement. The record includes the notice version, form source and server-issued UTC time. Opening a policy is a view, not evidence of reading or contractual acceptance. Internal follow-up notes are kept separately from your original message.

If the form cannot confirm receipt, you can retry safely, download a brief locally or choose to send an email draft yourself. Please leave out passwords, payment-card details, identity documents and private guest information.

Information needed for an agreed project

A project may involve contact and billing details, supplied copy, brand assets, photographs, access permissions, feedback and project communications. We use these to deliver the agreed work, administer payment and support, and handle disputes or applicable record-keeping duties. Access to an account should be granted through suitable limited permissions wherever possible, rather than sending a password in a form.

The project proposal must identify any additional forms, payment providers, booking tools or data-processing services before they are added. We do not promise that every project has the same data flow.

Invitations, photographs and personal stories

Invitation and personal websites can contain names, event dates and venues, photographs, letters, music, guest contact details and RSVP responses. Before collecting or publishing them, we agree what is necessary, who may see it, who can access responses, where it is hosted and how it will be removed or handed over.

You must have appropriate permission to supply and publish another person’s material. Take particular care with children’s photographs, home addresses, guest lists and private messages. Do not supply these through this enquiry form. A site shared through an unlisted link may still be forwarded; it is not the same as authenticated access. Password protection or another access restriction must be explicitly included and tested if required.

Guest-facing notices and consent choices must reflect the actual RSVP or other tools selected. We agree the respective responsibilities of Aribify and the project owner before such collection starts.

Providers and external destinations

This site is hosted using Sites, an OpenAI website-hosting service. Hosting infrastructure may process request information such as IP address, browser/request headers, time and security logs to deliver and protect the site. This notice does not claim that infrastructure logging is disabled. Aribify does not control every provider’s infrastructure retention.

The enquiry form uses Cloudflare Turnstile to check for automated submissions. Cloudflare processes technical browser and request signals, including IP address, for verification. Our backend validates a short-lived verification token before accepting a new enquiry. We do not store that token with your enquiry or include it in notification emails. We temporarily retain a keyed token digest to prevent reuse; it expires after ten minutes and is removed by routine cleanup. See the Cloudflare Turnstile Privacy Addendum ↗ for its processing practices.

Fonts, logos and preview media used on the main page are served as local site assets. Aribify uses first-party analytics only with your permission. Google Analytics 4 is prepared but remains disconnected; Google receives no analytics requests until a property is configured and you give the relevant permission. We have not added advertising pixels, embedded social feeds or third-party video players to the main page. External links are opened only when you choose them. WhatsApp, X, Hostinger and the independent design-reference websites apply their own practices after you leave Aribify.

Information sent by email is processed by the relevant mail providers. Hosting and mail infrastructure can involve processing outside India. We assess additional project and marketing providers before activation and describe material changes here. We do not sell enquiry details or add them to a marketing list automatically.

Newsletter and marketing choices

Newsletter registration remains unavailable while outgoing email is unconfigured. In that state the form does not save your email. The prepared delivery integration is Resend; it must be connected, its sender verified and delivery checked before subscriptions are enabled.

When enabled, a separate unchecked marketing choice and email confirmation are required. We store your normalized email, requested preferences, consent wording/version and request/confirmation dates. Personal confirmation and unsubscribe links contain secure tokens. A subscription request is not a confirmed subscription. A new enquiry never adds you to marketing.

You can unsubscribe from the link in a subscription email or contact hello@aribify.com. Withdrawal stops future newsletter jobs; a send already handed to the mail provider cannot be recalled. Unsubscribed addresses are not silently re-added. Re-subscription requires a fresh request and confirmation; complaints and bounces remain suppressed. Minimal keyed suppression references protect against accidental re-addition.

Cookies, browser storage and retention

Your browser privacy choice is stored for up to 180 days under aribify.privacy.v1. An HTTP-only privacy cookie associates changes with a pseudonymous consent record; it contains no form values. Necessary hosting security and these choice records are not optional analytics. Use “Cookie preferences” to reject analytics or change your choice later. Form entries remain in the open page until you submit, clear or reload it.

With analytics permission, we measure registered pages, meaningful clicks, section exposure, selected scroll milestones and form progress. A random 30-minute session separates visits. We do not record keystrokes, pointer paths, message contents, names, email fields, precise location or hardware identifiers in analytics. We keep only approved campaign fields and referring domains, excluding URL queries from page paths. We do not identify a visitor across devices or connect browsing histories to enquiry records.

Withdrawal clears unsent event batches and stops optional collection. Server checks also reject events associated with withdrawn permission. Previously permitted records expire under the schedule below. Blocking tools and failed requests mean these measurements are incomplete; device and browser categories are approximate.

  • Raw analytics: 90 days; anonymous daily event totals: 400 days.
  • Enquiries: closed/lost records are erased after 12 months without an update unless a documented hold is needed. Open and won records receive an annual necessity review.
  • Unconfirmed subscriptions: 30 days. Unsubscribed or suppressed email addresses: removed after 30 days; minimal keyed suppression references: up to three years.
  • Consent evidence: up to two years, or while linked to a retained enquiry/subscription.
  • Abuse-limiting IP references: keyed hashes, normally expiring within one hour; never added to marketing analytics. Infrastructure providers may retain separate security logs.
  • Operational logs: 90 days; administrative access/change logs: one year; encrypted application backups: 30 days.

Deletion jobs run through maintenance. Their last completion and backup status are visible to administrators. Provider backups and legally necessary project/payment records may follow separate duties. Contact us for the handling of a specific record. Administrative sign-in uses ChatGPT; its authentication service controls its own session and security practices.

Google Analytics remains off. Before activation, its property settings and retention must be verified, this notice updated where needed and consent requested again. No advertising pixels are active. Hosting may use technical security cookies such as Cloudflare __cf_bm.

Requests, security and changes

Contact hello@aribify.com to request access, correction, deletion, withdrawal or help with a privacy concern. Describe the request without including unnecessary sensitive information. We may ask for proportionate evidence to confirm that we are dealing with the right person. Available statutory rights and response duties depend on the applicable law and its commencement; this page does not certify legal compliance.

We aim to restrict project information to people and providers who need it and use the controls appropriate to the selected tools. No website or email service can promise absolute security. If you believe information has been exposed, contact us promptly.

Material changes to these practices will be reflected in an updated notice. Changes will not be used to silently convert an existing enquiry into marketing consent. For a project-specific processing arrangement, use the agreement applicable to that project.

Aribify · hello@aribify.com
WhatsApp ↗