Back

Privacy Policy

OpenSoftware Network
Effective Date: June 1, 2026
Last Updated: July 16, 2026

1. Introduction

This Privacy Policy describes how Alongside Finance, Inc., a Delaware corporation ("Alongside," "we," "us," or "our"), collects, uses, and discloses information when you access or use the OpenSoftware network and related services (the "Service"). By using the Service, you agree to the practices described in this Privacy Policy.

This Privacy Policy supplements, but does not replace, our Terms of Service. Capitalized terms not defined here have the meanings given in the Terms of Service.

2. Information We Collect

We collect different information depending on whether you are browsing the public marketing site, signing in or managing billing, or using the June desktop app.

2.1 Public Marketing Site

If you browse the public OpenSoftware or June marketing site without signing in, we collect limited website information, including:

  • Site usage: pages you visit, traffic sources (including referrals from AI search services), and June download events, measured through analytics providers such as Plausible Analytics, Promptwatch, Google Tag Manager, and Google Analytics.
  • Device and connection information: IP address, browser type, operating system, and referring URL. Plausible processes this information transiently to count unique visits and does not store it or use it to identify you. Promptwatch uses referral, approximate location, device, and browser information to attribute visits from AI search services.
  • Functional browser storage: preferences such as your selected site theme.
  • Marketing attribution: campaign parameters (UTM source, medium, campaign, content, and term) and an X click identifier (twclid) when they are present in a referring link. We retain first- and last-touch values for no more than 90 days in local storage and a first-party cookie scoped to.opensoftware.co so the public site and account checkout can use consistent attribution. If you sign in during that period, Open Software Accounts may retain those minimized attribution fields for up to 180 days for aggregate campaign measurement and billing reconciliation.
  • Server logs and diagnostics generated by our hosting providers.

2.2 Account, Billing, and Sign-In Surfaces

When you create or use an OpenSoftware account, sign in, manage your profile, or use billing features, we collect:

  • Account information: email addresses, account handle, linked sign-in providers, and display name or avatar URL if provided by you or by a sign-in provider you choose.
  • Profile information: additional email addresses, display name, avatar URL, and similar profile details if you choose to add or update them.
  • Payment and subscription information: billing or receipt email, Stripe customer, subscription, checkout, payment-method, and transaction identifiers, subscription status, trial status, credits, usage charges, and related billing records. Payment-card entry and full card numbers are handled by Stripe; we do not store full payment-card numbers.
  • Communications: messages you send to us via support requests, feedback, or other channels.
  • Usage and billing data: account and billing features you use, model and capacity consumption, credit transactions, timestamps, and similar operational information.

2.3 June Desktop App

June is designed to keep app state, recordings, transcripts, files, sessions, and agent memory on your device by default. We receive or process June app content only in specific cases, including:

  • Model processing: when you use transcription, note generation, dictation cleanup, agent, or similar features that send audio, transcripts, prompts, files, context, or agent messages for processing, June routes those requests through our publicly verifiable confidential-compute backend to privacy-preserving inference providers such as Venice AI. The backend is designed so we do not see the request contents while they are in flight.
  • Metering and operations: model choice, capacity consumption, request timing, credit usage, errors, and similar operational records needed to run and bill the Service.
  • Issue reporting: descriptions, diagnostics, attachment names, and attachment contents that you choose to include in an issue report.

2.4 Information from Third Parties

We may receive information about you from third parties, including Stripe for payments and subscriptions, sign-in providers such as Privy, GitHub, or Google when you choose those sign-in methods, Plausible Analytics, Promptwatch, Google Tag Manager, Google Analytics, and X Ads for website analytics, AI-search referral measurement, tag management, and campaign measurement, and model infrastructure providers when we process model requests you send through June.

2.5 Google Workspace Data Used by June

If you choose to connect a Google account to June, June requests only the permissions you select. Depending on those permissions and the feature you use, June may access:

  • Gmail data, including message and thread metadata, message content, attachment metadata, labels, drafts, and sent messages. June does not retrieve attachment contents.
  • Google Calendar data, including calendars, events, event details, attendees, responses, and free or busy information.
  • Basic Google account information used to identify the connected account, including your email address.

June uses this data only to provide the user-facing features you choose, such as searching and summarizing email, preparing or sending messages, organizing mail, reading or managing calendar events, preparing meeting briefings, and running routines you configure. June does not use Google Workspace data for advertising, credit or lending decisions, sale to data brokers or information resellers, or training generalized artificial intelligence or machine-learning models.

In local connector mode, Google access and refresh tokens are stored in your Mac's Keychain. Gmail and Calendar API requests originate on your device and go directly to Google. Alongside does not receive or store those tokens. If a June feature uses model inference, content selected for that feature may be sent to the model provider you selected solely to produce the result you requested. Selecting a local model keeps that inference on your device. June identifies this separate inference path in the product before you enable connector features.

Connector responses are processed on your device. Google Workspace data that you choose to save in a local note, conversation, draft, routine, or other June artifact remains in your local June data until you delete that artifact. Disconnecting the account deletes its tokens from the Keychain. You may also choose to revoke June's access with Google.

3. How We Use Information

We use the information we collect to:

  • Provide, operate, and maintain the public website and Service.
  • Measure public-site page views, AI-search referrals, and June download performance.
  • Process transactions, manage subscriptions, and administer capacity and renewals.
  • Authenticate accounts, maintain account profiles, and manage sign-in sessions.
  • Process June app requests, route model calls, and meter model usage.
  • Communicate with you about your account, our Service, and updates to our terms or policies.
  • Respond to your inquiries, support requests, and issue reports.
  • Detect, investigate, and prevent fraud, abuse, and security incidents.
  • Analyze and improve the Service, including through aggregated and de-identified data.
  • Comply with legal obligations and enforce our agreements.
  • With your consent, send marketing communications (which you can unsubscribe from at any time).

4. How We Share Information

We share information in the following circumstances:

4.1 Service Providers

We share information with third-party service providers that perform services on our behalf. The providers differ by surface: the marketing site uses hosting providers and analytics and tag-management providers, including Plausible Analytics, Promptwatch, Google Tag Manager, and Google Analytics; account and billing surfaces use sign-in providers, email providers, and Stripe; and June app features that require remote processing use backend infrastructure, confidential-compute hosting, model infrastructure providers, and issue-reporting or support systems. These providers are bound by contractual obligations to handle information consistent with this Privacy Policy where applicable.

4.2 Legal and Safety

We may disclose information if required by law, subpoena, or other legal process, or if we believe in good faith that disclosure is necessary to (a) comply with legal obligations, (b) protect the rights, property, or safety of Alongside, our users, or others, or (c) investigate or prevent fraud or security incidents.

4.3 Business Transfers

In the event of a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or substantially all of our assets, your information may be transferred as part of that transaction. We will notify you (by email or notice through the Service) before your information becomes subject to a different privacy policy.

4.4 Affiliates and Successor Entities

We may share information with our affiliates and with any successor entity that takes over operation of the Service from Alongside (see Section 17 of the Terms of Service).

4.5 With Your Consent

We may share information with third parties when you direct us to do so or when you otherwise consent to the sharing.

4.6 Aggregated and De-Identified Data

We may share aggregated or de-identified information that cannot reasonably be used to identify you.

4.7 Google API Services User Data

We do not sell Google user data or transfer it for advertising, data brokerage, credit, lending, or other unrelated purposes. We do not permit humans to read Google user data unless you first give affirmative consent for specific data, access is necessary for security or legal compliance, or the data has been aggregated and de-identified for permitted internal operations. Any transfer to a model provider is limited to providing the user-facing June feature you requested and is made with your consent through your connector and model choices.

June's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

5. Cookies and Similar Technologies

The public marketing site and account surfaces use different browser technologies. We use cookies, local storage, and similar technologies to operate the Service, remember preferences, and measure usage. The technologies we use include:

  • Strictly necessary: required for account, authentication, security, and billing surfaces to function.
  • Functional: local storage that remembers public-site preferences such as your selected site theme.
  • Analytics on the public site: Plausible Analytics counts aggregate page views and June download events; Promptwatch measures visits referred by AI search services, including landing pages, sources, approximate locations, devices, and browsers; and Google Tag Manager may load Google Analytics or related measurement tags to help us understand site traffic, referrals, campaigns, and download performance.
  • Marketing attribution: a first-party cookie namedos_marketing_attribution, scoped to.opensoftware.co and retained for no more than 90 days, carries first- and last-touch UTM fields and twclidbetween the public site and account surfaces. When a signed-in account receives those fields, the account service may retain them for up to 180 days.
  • X campaign measurement: the X Pixel receives page telemetry and may receive conversion telemetry together with campaign and click identifiers. We do not send hashed email addresses or phone numbers to X unless we separately enable that feature and update this notice as required.

You can manage cookie preferences through your browser settings. Disabling cookies may affect your ability to use certain features of the Service.

6. Data Retention

We retain account, billing, subscription, metering, support, issue report, log, and diagnostic information for as long as needed to provide the Service, comply with legal obligations, resolve disputes, and enforce our agreements. Local June app content, including the local app database, recordings, transcripts, files, sessions, and agent memory, remains on your device by default unless you send it to us for model processing, support, issue reporting, or another requested service. When information is no longer needed, we delete or de-identify it in accordance with our retention policies and applicable law.

7. Your Rights and Choices

Depending on your jurisdiction, you may have the following rights with respect to your personal information:

  • Access: request a copy of the personal information we hold about you.
  • Correction: request that we correct inaccurate or incomplete information.
  • Deletion: request that we delete your personal information, subject to certain exceptions.
  • Portability: request a portable copy of your information.
  • Restriction or objection: request that we restrict or stop certain processing.
  • Withdrawal of consent: where processing is based on consent, you may withdraw consent at any time.
  • Marketing opt-out: opt out of marketing communications by following the unsubscribe instructions or contacting us.

To exercise these rights, contact us at support@opensoftware.co. We may need to verify your identity before fulfilling your request.

8. EEA, UK, and Swiss Users

If you are located in the European Economic Area, the United Kingdom, or Switzerland, you have additional rights under applicable data protection law (the GDPR or equivalent). The legal bases on which we process your information include performance of a contract (to provide the Service), legitimate interests (to operate and improve the Service and prevent abuse), legal obligations, and your consent (where applicable).

If our processing is based on consent, you may withdraw it at any time. You also have the right to lodge a complaint with the data protection authority in your jurisdiction.

9. California Residents

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), including the rights of access, deletion, correction, portability, and opt-out of "sale" or "sharing" of personal information. We do not sell personal information for monetary consideration. To exercise your CCPA/CPRA rights, contact us at support@opensoftware.co. We will not discriminate against you for exercising these rights.

10. International Data Transfers

The Service is operated from the United States. If you access the Service from outside the United States, your information may be transferred to, stored in, and processed in the United States or other jurisdictions where data protection laws may differ from those in your country. Where required, we implement appropriate safeguards for such transfers, including standard contractual clauses or equivalent mechanisms.

11. Children’s Privacy

The Service is not directed to children under 13 (or under 16 in certain jurisdictions). We do not knowingly collect personal information from children. If you believe that a child has provided us with personal information, please contact us, and we will take appropriate steps to delete it.

12. Security

We implement reasonable administrative, technical, and physical safeguards designed to protect personal information. However, no method of transmission or storage is fully secure, and we cannot guarantee absolute security.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. Material changes will be posted to the Service or sent to you by email. The "Last Updated" date at the top of this policy indicates when it was last revised. Your continued use of the Service after the effective date of any update constitutes your acceptance of the updated policy.

14. Contact

Questions or requests about this Privacy Policy may be directed to:
Alongside Finance, Inc.
Attn: Privacy
Email: support@opensoftware.co