· Open app

Privacy Policy

Last updated: October 19, 2026

Expecza is operated by Jadyn Design Lab Inc. Contact us about privacy or support at hello@jadyndesignlab.com.

What we collect and why

Email signup gives us your email address, chosen username and a securely hashed password to create and secure your workspace. Google sign-in gives us your Google account identifier and email address. We do not store plaintext passwords. We request identity/profile permissions for authentication. We also process the instructions you enter, your selected connection settings, task schedules, task activity, and generated results so we can perform your requests and show your history.

Connected accounts are optional

Gmail inbox scanning is not offered in the current version. You may provide emails saved as PDF or text, or paste content for a task. Previous broad Google connection grants are retired; affected users must reconnect Calendar and Drive with the current permissions.

Connecting Google Calendar lets Expecza list calendars you can access and read event details such as titles, dates, times, descriptions and locations to answer your questions. It cannot create, edit or delete calendar events.

Where available and enabled, Google Drive uses the non-sensitive drive.file permission with Google Picker. It can search and read only files you explicitly select for Expecza, including previous selections. Supported text files can be read, Google Docs exported as text and Google Sheets as CSV (first sheet only). The Google permission technically allows creating, editing and deleting selected files, but Expecza implements reading only. The short-lived Drive access token is passed to Google Picker in your browser, never to our AI provider. Outlook can search and read messages; attachment contents are not downloaded. OneDrive can search file names and read supported text files. Slack can search messages visible to the consenting user. Notion can search and read pages and child blocks that the user shares with the connection. These connectors do not send messages or edit source content. Availability depends on provider setup and approval.

We retain access tokens and refresh tokens so your connection can work after consent, including for enabled scheduled tasks. You choose which connections are enabled and which tasks are scheduled. We do not share your connection with other users.

Files and voice

You choose individual files or a folder in your browser. Expecza does not upload the entire folder. It sends the text or prepared image/PDF content needed for your task to our server and AI provider. Local file tasks require your browser to remain open with access to the selection. Voice conversations send your microphone audio to our AI provider and may produce saved transcripts and task results. You control when to start and end a conversation.

AI processing and service providers

Expecza uses OpenAI to process task instructions, relevant content retrieved from your enabled account connections or selected files, and voice audio to produce answers. Only use these features with information you are permitted to share for processing. We use Render for application hosting, Neon for database storage, Vercel for our public website, Cloudflare for domain infrastructure, and Resend to deliver account verification and password-reset emails. Resend processes recipient email addresses and the account emails, including time-limited verification or reset links. These providers process information needed to deliver and protect their services and may operate outside your country.

We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Expecza’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. Google content is used to provide the user-facing features you request. Human access is limited to circumstances permitted by that policy, such as your explicit agreement for support, security investigations, legal obligations, or permitted aggregated internal operations.

Storage and protection

We use HTTPS, account-based access controls, and application-level encryption for saved API keys and connection tokens. Tasks and results are stored in our hosted database; they are not all separately encrypted by Expecza at the application layer. Do not treat any online service as risk-free.

Temporary file-tool responses are deleted after consumption or expiry cleanup. Saved instructions, routines, reports, transcripts and results remain until you delete them or your account; there is no automatic expiry for saved task history. Hosting and AI providers may retain operational, security or backup records according to their own retention arrangements. Deletion from the active application does not mean every provider backup is immediately erased. Contact us for help with a specific deletion request.

You control your data

Contact hello@jadyndesignlab.com to request access, correction, deletion, or other privacy rights applicable to you. We may need to verify your identity before acting. Limited usage counters can remain until their short expiry to prevent abuse.

Changes and contact

We will update this page when our practices change. If a change requires new consent, we will request it. Questions or concerns can be sent to Jadyn Design Lab Inc. at hello@jadyndesignlab.com.