← Back to ReduceToOne

ReduceToOne Privacy Policy

Last updated: April 14, 2026

This Privacy Policy explains how ReduceToOne ("ReduceToOne," "we," "us," or "our") collects, uses, stores, and shares information when you use the ReduceToOne website, app, and related services (the "Service").

This document is written to match the product behavior reflected in the current codebase as of April 14, 2026. If the Service changes, this policy should be updated to match.

1. Information We Collect

We collect information in the following categories.

A. Account and profile information

When you create or use an account, we may collect:

  • your email address
  • your authentication identifier
  • your display name
  • your school system or campus information, if provided
  • your tracking topics and notification preferences
  • your app settings and account preferences

B. Information you provide in the Service

We collect information you choose to create, upload, submit, or manage in the Service, such as:

  • manual events
  • groups, sources, and subscriptions
  • event comments
  • source names, descriptions, categories, and related group details
  • school or Canvas setup requests
  • any notes or text you submit through the Service
  • text you paste into the extraction lab or related event-ingestion tools
  • flyer images, screenshots, or other uploaded event images used for OCR or extraction
  • OCR text generated from uploaded images
  • extracted event candidates, evidence spans, validator results, moderation notes, auto-publish decisions, and rollback history associated with event-ingestion workflows

C. Information from connected services

If you connect a third-party account or data source, we collect and process information needed to provide that connection.

#### Google Calendar

If you connect Google Calendar, ReduceToOne requests read-only access to your Google Calendar data and may import event information such as:

  • event titles
  • descriptions
  • start and end times
  • due dates
  • calendar event links
  • related identifiers needed for syncing and deduplication

#### Email forwarding

If you set up email forwarding to a ReduceToOne intake address, or send mail to a ReduceToOne intake address, ReduceToOne may collect and process limited information from the forwarded message, such as:

  • the forwarding address alias associated with your account
  • subject
  • sender/from value
  • received date
  • message identifiers
  • a parsed text or HTML excerpt from the forwarded message
  • links, dates, and other event details extracted from the forwarded message
  • forwarded-email verification codes sent by Gmail when you are setting up forwarding

In the current implementation, ReduceToOne does not request Gmail inbox access through the Gmail API for this feature.

#### Canvas

If you connect a Canvas account through a configured school Canvas site, ReduceToOne may collect and process:

  • basic Canvas user information returned during OAuth
  • course data
  • planner items
  • calendar events
  • school or site metadata needed to manage the connection

#### Facebook Pages and Instagram Business

If you connect a Facebook Page or Instagram Business account, ReduceToOne may collect and process:

  • page or account IDs
  • account names and usernames
  • page categories
  • post or media captions/text
  • timestamps
  • links and media URLs
  • metadata used to convert social posts into event records

#### Apple Calendar / ICS feeds

If you connect an Apple Calendar or another ICS feed by URL, ReduceToOne may collect and process:

  • the feed URL you provide
  • the feed host and a hashed identifier
  • calendar names when present in the feed
  • event titles, descriptions, dates, recurrence details, locations, and links contained in the feed

D. Technical, device, and usage information

We automatically collect some technical information needed to operate and secure the Service, such as:

  • cookie values and one-time security nonces used during OAuth flows
  • local storage and session storage values used for theme settings and app caching
  • request metadata and operational logs
  • IP address information where needed for abuse prevention, security, or rate limiting
  • first-party website telemetry such as page views, CTA clicks, form submissions, referrers, and related usage events
  • pseudonymous visitor and session identifiers generated in the browser for first-party telemetry
  • client, render, and server error information used to troubleshoot failures and monitor site health

2. How We Use Information

We use the information described above to:

  • create and manage your account
  • authenticate users and protect accounts
  • import, organize, rank, and display events and tasks
  • sync connected services such as Google Calendar, email forwarding, Canvas, Facebook, Instagram, and ICS feeds
  • run conservative event extraction, OCR, moderation, duplicate detection, and trusted-source auto-publish safeguards
  • let you create groups, sources, subscriptions, comments, and preferences
  • operate the daily brief, calendar, and related product features
  • measure feature usage and website conversion so we can improve onboarding, public pages, and launch operations
  • troubleshoot issues, monitor performance, and prevent abuse
  • maintain audit and sync history for security and operational purposes
  • communicate with you about account or service issues
  • comply with legal obligations and enforce our Terms

3. How Information May Be Shared

We do not sell your personal information.

We may share information in the following limited ways.

A. Service providers and infrastructure vendors

We may share information with vendors that help us operate the Service, such as:

  • authentication providers
  • hosting and infrastructure providers
  • database and storage providers
  • email delivery providers
  • analytics, error monitoring, OCR, and AI processing providers
  • security and support vendors

These providers may process information on our behalf and under our instructions.

B. With other users or the public, based on how you use the Service

Some information becomes visible to others because of product features you choose to use. Examples include:

  • comments you post on group events
  • group, source, and event information you publish through public or shared sources
  • public source pages that display source and event information to visitors

If you post a comment on a group event, your display name may be shown to other users with access to that event. In some cases, if no display name is available, your email address may be used as the visible author label.

C. Connected platforms at your direction

When you choose to connect a third-party service, ReduceToOne exchanges information with that provider to complete authentication, refresh access, and fetch the data you authorized us to access.

D. Legal and business transfers

We may disclose information if reasonably necessary to:

  • comply with law, regulation, legal process, or lawful requests
  • protect the rights, safety, and security of ReduceToOne, our users, or others
  • investigate fraud, abuse, or security issues
  • support a merger, acquisition, financing, or asset transfer involving the Service

E. AI and OCR processing

If you use extraction features, we may send relevant text, OCR text, and uploaded images to service providers that help us:

  • detect likely event information
  • extract structured fields
  • run OCR or document-text extraction
  • validate or score extracted candidates

We use those systems to support review-first event ingestion, source trust decisions, duplicate checks, and related moderation workflows. In the current implementation, image/flyer extraction remains review-first, and trusted-source auto-publish is limited by internal evidence, validator, confidence, duplicate, and rollback safeguards. We do not promise that extraction systems are perfect, and extracted results may still require review or correction.

4. Google API Data

ReduceToOne'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.

5. Cookies, Local Storage, and Similar Technologies

ReduceToOne uses a small set of cookies and browser storage technologies to operate the Service. In the current implementation, these uses include:

  • security cookies or nonces used during OAuth sign-in and account-connection flows
  • local storage used for theme preferences and certain client-side state
  • session storage used for temporary caches and faster in-app navigation
  • first-party telemetry requests used to measure visits, CTA clicks, form submissions, and website errors
  • browser storage values used to maintain pseudonymous telemetry visitor and session identifiers

ReduceToOne does not currently use these technologies for cross-site advertising.

Telemetry strings are sanitized before storage to remove obvious query-string fragments, email addresses, bearer tokens, JWTs, and similar credential-like values when they appear in tracked paths, referrers, messages, or metadata.

6. Security

We use reasonable technical and organizational measures designed to protect information.

In the current implementation, certain sensitive connection credentials, including OAuth tokens and ICS feed URLs, are encrypted at rest. Even so, no system is perfectly secure, and we cannot guarantee absolute security.

7. Data Retention

We retain information for as long as reasonably necessary to provide the Service, maintain security, comply with legal obligations, resolve disputes, and enforce agreements.

In practice:

  • account and product data are generally retained while your account is active
  • sync logs, audit information, and operational records may be retained longer where reasonably necessary
  • website telemetry and error records may be retained for product analytics, reliability monitoring, and launch operations
  • telemetry records may include sanitized paths, referrers, event names, pseudonymous visitor/session identifiers, and limited error metadata needed for internal observability
  • extraction candidates, OCR text, evidence spans, moderation notes, and rollback history may be retained as part of event-ingestion history and source trust calculations
  • disconnecting a third-party connection may stop future syncing, but previously imported event records may remain unless they are separately removed
  • disconnecting email forwarding removes the forwarding connection and deletes the forwarded-email imports associated with that connection
  • when you delete your account, we delete or attempt to delete the core account data associated with that account, subject to limited retention for backups, logs, fraud prevention, or legal compliance

8. Your Choices

You can generally:

  • update account preferences and settings in the app
  • disconnect connected services from the connections area of the app
  • delete your account from the settings area of the app
  • request privacy assistance by contacting us at reducetoone.com@gmail.com
  • request access, correction, or deletion help where applicable law gives you those rights

If you disconnect a service, that does not always remove data previously imported from that service. Account deletion is the stronger removal action. For deletion-specific instructions, see the Data Deletion page.

9. Third-Party Services and Links

The Service relies on third-party platforms and may link to third-party sites, including Google, Meta, Canvas, Apple Calendar feeds, and other source links. Their privacy practices are governed by their own policies, not this Privacy Policy.

10. Children's Privacy

If you believe a child provided personal information to ReduceToOne in a way that violates applicable law, contact us at reducetoone.com@gmail.com, and we will review the request.

11. Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we may update the date above and take additional steps where required.

12. Contact

If you have questions about this Privacy Policy or ReduceToOne's privacy practices, contact:

  • Email: reducetoone.com@gmail.com