Aspire makes everyday apps for everyday people. This policy explains how Aspire Labs, Inc. (“Aspire,” “we,” or “us”) handles personal information across our websites, Swing, and the other services described below. It explains what we collect, why we use it, who receives it, and the choices you have.
For privacy questions or requests, email anish@aspireai.com. For help with your Swing account, you can also contact support@swing.so.
What this policy covers
Aspire Labs, Inc. is responsible for the personal information described in this policy. It covers aspireai.com, our Swing app and related services, the Internet Condom promotional website at internetcondom.ai, our waitlists and recruiting communications, and other Aspire services that link to this policy. This is our current general privacy notice for these Services. Feature-specific notices shown when you use a feature may provide additional details. If an older Aspire or Swing notice describes the same processing differently, this updated notice provides the current description.
The information involved depends on what you use. Browsing Aspire’s homepage is different from creating a Swing account, submitting an application, or joining an invited workspace. Links to the App Store, LinkedIn, X, and other independent services take you to services with their own privacy policies.
Information we receive
- Account information. When you sign in to Swing with Apple or Google, we receive a provider identifier, authentication information, and the name and email address the provider makes available. This can be an Apple relay email address. We also maintain your Aspire or Swing user ID, preferred name, device identifiers, time zone, account settings, and account activity. Signing in with Google does not itself give us access to your Gmail inbox or calendar.
- Settings and content. We receive information you enter or synchronize, such as schedule names, times, active days, preferences, and, where available, the text and presentation settings for your Morning Mantra. Some information is stored on your device and some is stored with your account.
- Purchases. Where paid features are offered, we receive purchase and subscription records needed to establish access: product and transaction identifiers, entitlement, renewal, expiration, cancellation, and refund status. Apple handles App Store payment details; we do not receive your full payment-card number from Apple.
- Communications. We receive emails, support messages, feedback, and any files you choose to attach, including images, video, or audio. We also receive the details you submit to a waitlist, access-request form, or career application.
- Technical information. Our services and providers receive information such as IP address, browser or device type, operating system, app version, requested page or endpoint, request time, identifiers, and security or error information. App interaction events and diagnostics are described below.
These details come from you, your browser or device, the sign-in and purchase services you choose, and providers that help us operate the services. You can decline to provide information, but we may be unable to create an account, respond to a request, or provide a feature that needs it.
Swing and Screen Time
Swing helps interrupt mindless scrolling with app blocking, schedules, and humorous prompts. It uses Apple’s Screen Time frameworks, including Family Controls, Device Activity, and Managed Settings. You choose what to protect and grant the relevant permission through iOS.
Apple represents selected apps, categories, and websites using protected tokens. The current Swing blocking flow uses those selections on your device. Schedule synchronization sends the schedule name, timing, time zone, enabled state, and selection counts. It does not need a server-side list of the apps you selected. Current blocking-event reporting removes protected app names, bundle identifiers, and displayed prompt text before transmission.
We can receive information about how the blocking feature works, such as permission status, session start and end, attempted overrides and their outcome, or a successful redirection. That is different from recording what you do inside the apps you protect. Swing’s replay feature does not record screens outside Swing.
If your account includes Morning Mantra, your written mantra and its settings may synchronize to your account. For device registration and notification delivery, we process a push token and your current notification permission state. Where notifications are enabled, we also process delivery information. You can change Screen Time and notification permissions in iOS Settings.
Analytics, replay, and diagnostics
We use product analytics to understand onboarding, feature use, interaction outcomes, and reliability. Events can include screens visited, buttons used, schedule or session outcomes, subscription interactions, app version, time zone, and a user or installation identifier. PostHog and Mixpanel help process this information.
When Share product analytics is enabled, eligible Swing screens may also be included in a PostHog session replay: a sequence of screenshots and interaction context from within Swing. Replay can include onboarding before you create or sign in to an account, as well as signed-in use. Recording is subject to screen eligibility and server controls. Images and sensitive views are masked or excluded, but not all visible text is masked; ordinary interface text and interaction states may remain readable.
The product analytics setting is enabled by default in current app settings. You can turn it off in Settings → Privacy & Personalization → Share product analytics. Turning it off stops future optional product analytics and replay capture and clears queued optional data on the device. It does not automatically erase information already received by us or a provider; you can request deletion using the contact details in this policy.
Crash reporting, service security, billing, and operational reliability are separate from optional product analytics. We use diagnostics services including Firebase Crashlytics and, where configured, Sentry. Reports can include crash or hang details, app and OS version, device information, installation or user identifiers, screen context, and request identifiers. These reports are not necessarily anonymous, and turning off Share product analytics does not turn off all crash or operational reporting.
Support uploads and optional features
If you send feedback, we store your message and the attachments you select. Support attachments are held in private storage and can be accessed through authorized tools or temporary links. Our support email provider may receive the message, account details, diagnostics, and attachment copies or links so our team can investigate.
If you submit an audio attachment, we may send it to Groq or OpenAI for transcription and keep the transcript with your feedback. Please avoid including passwords, payment details, or other people’s sensitive information in support messages or recordings.
Swing’s core blocking and routine features do not require AI chat or generated feeds. If you use a beta or another Aspire feature that offers AI assistance, the text and context you submit for that feature may be sent through our backend to model providers such as Anthropic, OpenAI, Google, or Groq. The feature’s notice explains the relevant input and use. Processing can include generating a response and recording operational details such as model, request status, and usage. Support-audio transcription is a separate use, described above.
Some earlier or beta builds also offer optional weather or motion features. With the relevant iOS permission, these may process location, locality, weather, time zone, step counts, or activity summaries to personalize the feature. Swing’s core blocking and routine features work without location or motion access. You can revoke permissions in iOS Settings; this does not itself delete information already submitted.
Websites, waitlists, and videos
Our websites use hosting and delivery providers that receive network and request information when you visit. The Aspire homepage does not require an account. Individual features may use cookies or browser storage for sessions, security, or preferences; signed-in workspaces use session cookies. Browser controls can clear or restrict storage, although this may affect functionality.
If you join an Aspire or Swing waitlist or request another platform, we collect the information the form requests, such as name, email, and platform preference. We may also process referral codes, signup source, campaign information, waitlist position, and access status. We use this information to manage the list, prevent abuse, and send the updates you requested. Depending on the form, providers include GetWaitlist, Netlify, our backend, and email-delivery services.
The Internet Condom website is a promotional and demonstration site. Its interactive graphics load through external delivery services. Selecting “See it” loads a YouTube player using YouTube’s privacy-enhanced embed domain. Loading and interacting with the player still sends information, including network and device information, to Google or YouTube; privacy-enhanced mode does not mean no data is processed. See Google’s Privacy Policy. Other Aspire pages may also contain third-party videos.
Following a social link or interacting with an external service is governed by that service’s policies. We may receive the public profile details, comments, messages, and aggregate engagement information you share with our social accounts.
Applications and collaboration
When you apply for an Aspire role, we receive your email, application, résumé or portfolio, attachments, and related correspondence. We use them to review your application, communicate with you, and administer recruiting. Sending an application does not create a public profile or enroll you in product marketing.
If you are invited to an Aspire collaboration workspace, we may process your name, email, college or cohort, role, time zone, assigned social accounts, content submissions, posting evidence, feedback, and activity or performance records. Workspace administrators and authorized collaborators can access information relevant to their work. Where the workspace provides account management, it may store dedicated work-account credentials in encrypted form; do not enter personal account passwords. Optional integrations can process Discord identity or notification information and public YouTube performance data.
Any separate employment, internship, or contractor privacy notice applies to the activities it describes. This policy does not set the terms of an employment or internship arrangement.
Why we use information
We use personal information to provide the features you request; authenticate accounts and synchronize settings; deliver notifications; manage access and purchases; answer support requests; operate waitlists and recruiting; run invited workspaces; investigate errors and abuse; improve our products; and meet legal obligations.
Where European or similar data-protection rules apply, the relevant bases are providing a contractually requested service or taking steps at your request, our legitimate interests in secure and reliable operations, consent where required for optional processing, and compliance with legal obligations. Our legitimate interests include diagnosing failures, preventing fraud, responding to correspondence, and improving our services. Where local law requires consent for optional tracking or similar processing, consent is the applicable basis and may be withdrawn. A device permission and a legal basis for processing are not the same thing.
We do not sell personal information or use it for cross-context behavioral advertising. Swing does not display third-party ads. We do not make decisions that have legal or similarly significant effects on you solely through automated processing.
Who receives information
We share relevant information with providers that help deliver a feature or operate our business. Depending on the service you use, these include:
- Hosting, storage, and security: Vercel, Netlify, Cloudflare, Neon, and Upstash; Convex for real-time chat and generated-content features in participating beta services.
- Sign-in, device services, and purchases: Apple and Google; RevenueCat and Superwall in builds configured to use subscription services, including when a paywall is not shown.
- Analytics and diagnostics: PostHog, Mixpanel, Google Firebase Crashlytics, and Sentry.
- Email, forms, and applications: Google-hosted email, Resend, SendGrid, GetWaitlist, and Netlify.
- Optional integrations: the AI and transcription providers described above, YouTube, and Discord when you use the relevant feature.
Not every provider receives every user’s information. For example, an application email is different from an app analytics event. Some providers act on our instructions; others, including app stores and services you sign in to or visit independently, also process information under their own policies.
We may also disclose information at your direction, to authorized personnel who need it for their work, to professional advisers, to comply with a lawful request, or to protect people, accounts, and legal rights. Information may be transferred as part of a merger, acquisition, financing, or sale of a business, subject to applicable protections. We may use or share aggregate information that does not identify you.
Storage, retention, and deletion
We and our providers process information in the United States and other countries where we operate. Privacy laws may differ from those in your location. Where a restricted international transfer requires safeguards, applicable data-protection law governs those requirements. Contact us to ask about the arrangements relevant to your information.
Retention depends on the purpose and type of record. Account and synchronized settings are generally needed while the account is active; support records while resolving and documenting requests; waitlist information while administering access and requested updates; and application or workspace records while administering the relationship and related obligations. Security, transaction, and legal records may need to remain longer to investigate incidents, meet accounting or legal requirements, or resolve disputes. Backups and provider systems can have separate retention cycles.
In Swing, the account-deletion control begins the account deletion process. Access and sessions can be disabled before all stored records, attachments, backups, or provider records have been erased. Some cleanup runs separately in the background, and limited records may be retained for the reasons above. For a deletion request, an update on its status, or information not included in an in-app export, contact us. Uninstalling an app or clearing local history does not delete your server account. Deleting an account also does not cancel an Apple subscription.
We use access controls and other technical and organizational safeguards to protect information. No online service or storage system can guarantee complete security.
Your choices and rights
- App controls: change available account settings, turn off optional product analytics, and use export, local-history, or account-deletion controls where offered. An in-app export may not include every record held by a provider.
- Device controls: manage notifications, Screen Time authorization, microphone, photos, and any other granted permissions in iOS Settings.
- Email: use the unsubscribe instructions in marketing messages or contact us. Necessary account, security, purchase, and requested support messages may still be sent.
- Privacy requests: email anish@aspireai.com to request access, correction, deletion, a portable copy, or to raise a concern. Swing requests can also go to support@swing.so.
Depending on your location and applicable law, you may also have rights to restrict or object to processing, withdraw consent, use an authorized agent, or appeal a decision on a request. Withdrawal does not change the lawfulness of earlier processing. We may need proportionate information to verify your identity or an agent’s authority. We will respond within the time required by applicable law, explain any permitted exception, and will not discriminate against you for exercising your rights.
If you believe we have not addressed your concern, you may complain to the data-protection authority where you live or work, or another regulator with jurisdiction. You can contact us to appeal a request decision, with “Privacy appeal” in the subject line.
Children
Our services are not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child under 13 has provided information, contact us so we can investigate and take appropriate action. Product age ratings, local consent requirements, and the eligibility rules for a particular opportunity may impose additional restrictions.
Changes and contact
We will update the date on this page when this policy changes. For material changes, we will provide additional notice where appropriate or required, such as a notice in the service or an email. We will seek consent where a change requires it; publication of this policy is not a substitute for consent.
Aspire Labs, Inc.
Privacy and company inquiries: anish@aspireai.com
Swing support: support@swing.so