SUBMISSION PRIVACY · 17 OCTOBER 2026

Your context
stays private.

Anyone can request a scoped free engagement without signing in. Saeloun uses engagement submissions to assess fit, prepare requirements briefs, and help Vipul decide the next step.

What we collect

Your name, email, optional organization, preferred week, timezone, requested scope, project context, desired outcome, reference links, and any documents you choose to attach. You must be authorized to share everything you submit.

Who can access it

Submissions and uploads are stored privately, with sensitive fields encrypted in the application database. They are available only to the verified approved Vipul owner account. Other employee accounts do not gain owner access. The daily summary interface provides aggregate counts, requested weeks, aging, and next-step categories without names, emails, project text, or attachment contents. No requests are published or uploaded to public repositories.

Owner inquiry notifications

New requests create a private notification for vipul@saeloun.com through Saeloun’s configured email provider. It contains the offer, preferred week, timezone, duration and a link requiring owner authentication. Your visitor-supplied contact email may be used as Reply-To after syntax checks; its ownership is not verified. The email provider therefore receives that address. Project text and attachments are not included. These owner notices do not book meetings or authorize work.

Receipt acknowledgements

Use a contact address you control. We may send a routine receipt acknowledgement to the address you submit; its ownership is not verified. This message includes only a request reference and fixed receipt text, without your project context, attachments, private owner links or confirmed timing. It is separate from a personal reply, does not accept work or confirm a meeting, and promises no reply deadline. It is not a marketing subscription.

To limit email abuse, we group address variants for receipt limits and permit at most one receipt per recipient group in a rolling 24-hour window, with a separate global delivery budget. Your delivery address stays unchanged. Quota keys use a secret-keyed digest rather than storing another copy of the address. Multiple requests may therefore receive only one receipt. Mail delivery is not guaranteed.

Hosting, email and AI processing

This application does not send request text or files to ChatGPT or other external AI services. Requirements briefs are assembled by application rules, not a language model. Raw brief exports are disabled by default and require an explicit owner-controlled local export. They must not feed external AI or ChatGPT summaries. A local-only AI workflow on Vipul’s machine is planned; a local model is not connected to this intake today.

The website still uses external infrastructure. Cloudflare handles web traffic and may process request content and network/security metadata. Hatchbox manages the application on an external hosting server, where submissions, encrypted database fields, essential cookies and restricted operational backups are handled. Encryption does not remove the hosting operator’s role or imply that nothing is in the cloud. A configured email provider handles the limited owner notification and receipt acknowledgement described above, including the visitor-supplied contact address. No production deployment or provider configuration is verified by this notice alone.

Documents, designs, and summaries

PDF, PNG, JPEG, and plain text uploads are limited to three files and 5 MB per file. Files stay quarantined until a configured malware scanner reports them clean. Downloads require owner authentication. Plain text may be excerpted after scanning to help with a requirements brief; excerpts are untrusted source material, not instructions. Scanned PDFs, images, and unsupported formats are flagged for manual review rather than described with invented content.

This application does not send submissions or files to third-party AI providers. External AI processing of visitor submissions is disabled by policy; any future change would require a new explicit decision and an updated notice. Reference links are stored as text and are not automatically fetched. Do not submit secret sharing links.

Your control and retention

Do not submit credentials, API keys, production data, or unnecessary sensitive personal information. Requests can be withdrawn and deletion requested through the Saeloun contact page, using the same email as your submission and your reference if available. The retention process removes request records and attachments older than 90 days. Restricted operational backups may retain copies according to the hosting backup cycle.

No automatic commitments

A request is not an appointment, acceptance or permission to build. Vipul chooses reply and meeting times. The current pilot is free with a reviewed scope. Demo, preview, deployment or further implementation needs separate explicit approval.

Optional private team sign-in

Public engagement requests do not require a Google account or employee membership. A submitted email does not establish identity, employment or owner access. There is no public account registration.

Private owner and team sign-in requires a cryptographically verified Google identity, verified exact saeloun.com email and Workspace domain, and an administrator-maintained current employee allowlist. Only the verified approved vipul@saeloun.com account receives owner access; other employees cannot review submissions or approve demos. Chatbot, builder and other team tools are not available today and remain restricted to approved Saeloun employees if introduced.

We request only identity, email and profile scopes, with no Gmail, Drive or calendar access. The display name, verified work email, Workspace domain and expiry are encrypted in a private server-side session record. The browser holds an opaque token inside an encrypted HTTP-only cookie, Secure in production and SameSite=Lax. Sessions expire after eight hours, are revoked on sign-out, and employee membership is checked on each protected request. Google tokens and account identifiers are not retained. Missing identity configuration closes private owner and team access. Signing in never links earlier requests or authorizes work.

Operational data

The site uses an essential session cookie for form security and spam prevention. Request limits use the network address to reduce abuse. Submission content is filtered from application logs; hosting providers may retain standard access and security logs. This site includes no advertising trackers.