Preparing and arranging your scoping call
We use the submission to understand your request, create a private prospect record, and contact you about a scoping conversation.
Privacy
Clear boundaries for every connection.
This notice explains how byProduct handles information submitted through the public website and information accessed through connected services in the private Software Factory.
Eight required fields and an optional phone
We store your full name, work email, company, title, country, annual revenue range, industry, and goal description. If you provide a phone number, we store it with the same scoping brief.
Restricted to byProduct founders
Authorized byProduct founders can access the private intake record. A new submission also triggers an operational email notification so the team can respond.
180 days
We retain a scoping submission or Platform early-access email for 180 days, then remove the submitted personal data. You may ask us to delete it sooner.
No AI enrichment at launch
The launch intake does not run automated external research or AI enrichment about you or your company.
Read-only project context
When an authorized project administrator connects Jira Cloud, byProduct requests read-only Jira access. The customer selects the Atlassian site and the Jira projects that become available inside that byProduct project. The integration does not create, edit, transition, or delete Jira data.
Credentials and the selected boundary
We retain encrypted OAuth access and refresh credentials plus the selected Atlassian site and Jira project identifiers and names. We do not store the connecting user's Atlassian account ID. Credentials are never displayed to project users or exposed through the byProduct MCP connection.
Fetched when an authorized user asks
Within the selected Jira projects, byProduct can return an issue key, summary, description, status, issue type, priority, link, and update time. Issue content is fetched from Jira on demand and is not copied into a persistent Jira issue-content cache.
Project-scoped and permission-bound
Only users and MCP clients authorized for the same byProduct project can use its selected Jira connection. Jira still applies the permissions of the Atlassian user who granted access. Changing the selected Jira scope or disconnecting Jira revokes active MCP grants for that project.
Credentials removed immediately
Disconnecting Jira removes the stored OAuth credentials and prevents new Jira reads through the connection. Limited connection metadata may remain in the project's operational and security records. You can also revoke the grant from your Atlassian account.
Your work email only
The Pricing form stores the work email you submit so authorized byProduct founders can review Platform interest and contact you. It does not create an account, organization, project, or product access.
No raw network address stored
At the edge, a keyed digest of the network address is used only for a shared two-hour rate-limit window. It is not linked to your intake and is removed when that window expires.
YouTube loads only after you press play
Before you press play on the Estonian homepage, the video poster is served by byProduct. Pressing play connects your browser to YouTube to stream the video. YouTube may process playback data under its own privacy terms.
Read-only calendars you choose
Each user can connect their own Google account to a byProduct project. We request permission to list subscribed calendars and read events so you can choose calendars and request event information from them. This connection does not create, edit or delete events and does not request Gmail, Drive or Chrome synchronization access.
Credentials, selections and event metadata
We store encrypted OAuth access and refresh credentials and selected calendar identifiers, associated with your byProduct user and project. We fetch calendar names and access roles to show calendars available for selection. On request, event reads return identifiers, titles, start and end dates or times, status and update time within a window of up to 31 days and up to 50 events per call. This connector does not maintain a persistent event-content cache.
Your account and authorized project tools
Your personal connection and selections are bound to your user and project. Authorized project MCP clients can request Calendar reads using your personal authorization; they do not receive the stored OAuth credentials. We check user, project and selected-calendar access before returning data. Tools you authorize can receive the returned event metadata and retain it under their own handling rules.
Stop future reads and remove local credentials
Disconnecting removes that connection’s stored OAuth credentials and stops new reads through it. Limited connection, selection and security records may remain. Disconnect does not remove Google account-level app authorization or copies already returned to authorized tools or exports. You can revoke the app in your Google Account and contact hello@byproduct.ai to request deletion of information retained by byProduct.
Use for the requested Calendar feature
byProduct’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not sell Google Calendar data or use it to train generalized AI models.
Questions, corrections, or deletion
Email hello@byproduct.ai to ask about, correct, or delete information handled by byProduct.
Ready to describe the outcome you need?
Book a scoping call