Last updated:
1. About this policy
This is the privacy policy for BellSync’s public iPhone, iPad, and Apple Watch app, Web Display, website, Request Your School workflow, and support. The App Store also lists the Apple app as compatible with some Macs; a separate native Mac app is not publicly released. The Android sections describe existing test builds, which are not publicly released. BellSync is operated by Strategic Edits LLC. In this policy, “we,” “us,” and “our” refer to Strategic Edits LLC.
Using an app or Web Display to view a schedule is different from choosing to send us a school request, document, or support message through the website. The sections below explain what stays on your device or in your browser, what may pass through Apple or other services, and what we receive when you submit information. Other services you open may have their own privacy notices.
2. Website information we receive
- School request information: your name, email address, school name, state or region, role, selected platforms, any optional Other platform description, and any district, city, public bell schedule URL, or notes you provide. A school-issued email address is not required. The optional schedule URL is saved with your request notes and included in the notification email.
- Documents you choose to share: file contents and metadata such as filename, file type, size, private storage path, and the associated request ID. We also record the submission time and, for attached documents, the time of your sharing confirmation.
- Google Drive import information: selected file IDs, names, types, sizes when available, download permissions, file contents or exported copies, and the temporary authorization needed to retrieve them. Original Drive IDs and authorization tokens are not stored in the saved school request.
- Correspondence: your name, email address, optional school/district, help topic, and message submitted through the support form, plus information you send in follow-up correspondence.
- Technical information: our hosting and service providers may process IP addresses, browser and device details, request timestamps, and connection or error information needed to deliver and protect the service.
The website does not currently include advertising trackers or an analytics integration. When Google Drive import is enabled, the school request page loads Google’s sign-in and Picker libraries only after the requester eligibility step allows the request to continue. Those requests can provide Google with technical information before you open the Picker. Google may use its own cookies or account information under its privacy policy; BellSync does not store your Google access token in cookies or browser local or session storage.
3. How we use information
We use support messages to answer questions and investigate reported problems. We use school request information to review and support your school request, understand scheduling requirements, communicate with you, and support adding or updating your school in BellSync. We also use necessary technical information to operate the website, investigate failures, and protect against misuse.
BellSync staff handling your request may review the information and documents you deliberately share for that purpose. We do not sell personal information. We do not use imported Google Drive information for advertising or training general-purpose AI or machine-learning models.
4. Optional schedule links and documents
Teachers, school staff, parents, guardians, and students age 13 and older can request a school. Students under 13 should ask an adult to submit a request using the adult’s own information. You can submit a request without schedule documents, a schedule link, or a Google account. You may optionally provide a public HTTP or HTTPS link to your school’s bell schedule. The website does not automatically retrieve the contents of that link; we may review it when handling your request. If you attach documents, you must confirm that they can be shared with BellSync for the purpose of adding your school. Please share only files you are authorized to provide.
You can choose local files or select individual files from Google Drive. Both sources share the same limit of five files, with a maximum of 15 MB per file. Supported formats include PDF, DOC/DOCX, XLS/XLSX, CSV, PNG, and JPG/JPEG. You can remove a selected file before submitting.
5. Google Drive and authorization
Google Drive import is optional. Clicking “Choose from Google Drive” opens Google’s authorization and Picker flow so you can deliberately select individual files. BellSync requests only the https://www.googleapis.com/auth/drive.file permission for files you choose to share with the application. We do not request broad access to your Drive, crawl or index unrelated files, or perform background Google Drive synchronization.
When you submit the form with sharing confirmation, our server retrieves the selected documents and copies them into BellSync’s private storage. Google Docs are exported as PDF and Google Sheets as XLSX. Google’s native export service has a separate 10 MB limit. Import does not modify your original files or their sharing settings. Once imported, BellSync’s copy does not depend on the original Drive file remaining accessible.
The short-lived Google access token is held temporarily in browser memory and used by our server for that import. We do not persist it in our database, request records, email, or application logs, and we do not obtain or store Google refresh tokens. The browser clears the token and attempts to revoke authorization after a submission attempt, when the last Drive selection is removed, when authorization approaches expiry, or when you leave the form. If revocation cannot complete, the token still expires; we do not refresh it.
New authorization obtained for a cancelled Picker is cleared and revocation is attempted. If you already selected Drive files in the same form, cancelling a later Picker preserves the temporary authorization needed for those selections. Cancelling selection does not import files.
BellSync’s use and transfer of Google API data follows the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data policy. Selected file data is used for the school request feature you authorize, with supporting service providers as described below.
6. Private storage and email notifications
School request records are stored in Supabase. Uploaded and imported documents use a private Supabase Storage bucket and randomized object paths; original filenames are preserved as display metadata rather than used as the sole storage key. Documents are not made available through public storage links.
Resend delivers school request notifications and support form messages to BellSync’s support inbox. When automatic school request acknowledgments are enabled, we use Resend to attempt a confirmation to the email address on an accepted request. Support form messages are handled through email rather than saved as school request records in Supabase. The email address submitted with a support message is used as Reply-To. School request notifications include submitted form information, document filenames, and temporary signed download links instead of binary file attachments. Your submitted email address is used as Reply-To so we can respond to you. The support mailbox and any configured forwarding also process and store these messages.
Notification download links expire after 24 hours. Anyone who possesses a valid signed link may access the document until it expires, so links should not be forwarded beyond the people handling your request. Link expiration does not delete the stored file or request. BellSync can continue to access the private copy for the request’s purposes.
7. Third-party service providers
We use the following providers for the website, Web Display hosting, school requests, and support workflow. Apple device services and Android test-build services are described in their sections below:
- Vercel: website and Web Display hosting and website server processing. See Vercel’s privacy notice.
- Supabase: school request database and private document storage. See Supabase’s privacy notice.
- Resend: notification and support email delivery, including submitted details and, for school requests, temporary document links. See Resend’s privacy policy.
- Google: optional authorization, file selection, and selected-file retrieval or export. See Google’s privacy policy.
- Apple and device services: system photo and file selection, notifications, iPhone–Watch transfer, sharing, and device backups if enabled. See Apple’s privacy policy.
- Support email providers: receiving and storing notifications, correspondence, and any configured forwarding.
Information necessary for these services is processed by the relevant providers. Their own privacy notices and service terms also apply. We may disclose information when required by applicable law or necessary to address security or misuse. Any use or transfer of Google API data remains subject to the Google policies linked above.
8. Website and support retention
Support messages and related correspondence are retained only as reasonably necessary to answer and follow up on the support request. BellSync retains submitted school request information and uploaded or imported files only as reasonably necessary to review and support the school request, including related follow-up. We have not established a fixed retention period or an automated retention-deletion schedule for this workflow.
Interrupted or failed uploads can leave private files that are not associated with a saved request. Cleanup of those files is best effort and may require manual review. We do not promise deletion after a specific number of days. A formal cleanup and retention policy should be defined separately for request records, stored files, support email copies, and any applicable provider backups.
If information exists in provider backups or required security records, removal may be subject to those systems’ retention and restoration processes. The 24-hour lifetime of email links is an access limit, not a retention period.
9. Website choices and deletion requests
You can omit optional fields and documents, remove selected files before submission, cancel Google authorization, or use local uploads instead of Drive. You can also remove BellSync’s Google permission through your Google Account’s third-party connections. Revoking permission does not automatically delete documents already copied into BellSync storage.
To ask about, correct, or request deletion of your submitted information or documents, email support@bellsync.app. Include the email address used for the request and enough school/request information to help us locate it. Please do not send unnecessary sensitive information.
We may ask for information reasonably needed to verify your authority to make the request. These requests are handled manually, including review of stored files, request records, and support email copies. We may need to retain information where required by applicable law or for necessary security purposes, and will explain any relevant limitations. There is no automated deletion portal for this workflow.
10. Security practices
The website submission workflow uses HTTPS connections, server-side privileged credentials, private storage, randomized file paths, file count and size limits, file-type checks, and expiring signed links. Supabase service credentials and the Resend API key are not exposed in browser code. Application error logs avoid submitted document contents and Google authorization tokens.
File validation is not antivirus scanning, and a private bucket does not prevent access by someone holding a valid signed link. No internet service or storage system can guarantee absolute security. Please share only the information necessary for your school request.
11. Children and student information
The school request form is available to teachers, school staff, parents, guardians, and students age 13 and older. Before showing contact fields or document tools, we ask who is making the request and ask students to select an age group. We do not ask for an exact age or birthday. Students who select under 13 are directed to ask a parent, guardian, or teacher to make a fresh request using the adult’s own name and email. The student is not shown contact fields or upload tools, and the adult request does not carry over student-entered information. This is an adult-submitted request, not a parental-consent process.
The age-group choice is used only to decide whether the request may continue. We use a signed, essential session cookie to remember the requester category and eligibility decision, including when an adult must take over, so going back cannot simply change an under-13 answer. The cookie contains no name, email, birthday, or selected age group; its validity is limited to 24 hours, even if the browser restores the session. The submission, upload, and Google Drive import endpoints check this cookie before reading request details. We do not add screening choices or cookie details to saved school requests or notification emails. Ordinary hosting and security information described above may still be processed when someone visits the website or uses the screening step.
Eligible requests ask for the requester’s name and email address so we can review the request and follow up. Adults must provide their own contact information, not a child’s. Students do not need to provide official documents or a personal class schedule. Submitting a request does not automatically add a school to BellSync.
Beyond your own requested contact details, do not submit student names, student IDs, personal student schedules, grades, attendance records, medical information, or other unnecessary sensitive personal information in links, notes, documents, or support messages. Share general school scheduling materials and remove unnecessary personal details. If you have a concern about a child’s information or believe sensitive information was submitted, contact support@bellsync.app so we can review and address it.
12. BellSync on iPhone, iPad, and Apple Watch
Schedules and preferences. The Apple app saves personal schedules and settings on your device. These can include school and profile names, class or activity names, rooms, lunch choices, calendar corrections, colors, reminder choices, and display preferences. BellSync uses them for schedules, countdowns, widgets, and Live Activities where available. The app does not require a BellSync account to use a saved schedule. Device backups may retain copies depending on your Apple settings.
Local imports and exports. When you choose a photo or PDF in the app, BellSync reads it on the device to help prepare a schedule; that app import does not upload the selected file to BellSync’s website storage. You can also import or export BellSync schedule files. An exported file can contain schedule names, school details, classes, rooms, dates, notes, and other settings you saved. Sharing an export uses the destination you select through Apple’s share controls; please review the file and recipient before sharing. These app import and export paths are separate from the website’s optional school-request uploads and Google Drive import, which send selected documents to us as described above.
Apple Watch and notifications. BellSync uses Apple’s device frameworks to pass the active schedule and relevant settings between your iPhone and paired Apple Watch. The Watch may keep a local copy for its app, complications, and reminders. Optional notifications and Live Activities can show schedule details on your devices, including their Lock Screens, depending on your settings. You control notification permission and visibility through Apple’s settings. BellSync does not receive your schedule through this iPhone-to-Watch exchange.
Support from the app. If you choose Report a Problem, you enter a title and message. The technical-details switch starts on; you can turn it off before composing. When on, it adds the app version and build, iOS version, device model, and selected school and profile names if available. The app opens the system mail composer addressed to support@bellsync.app so you can review and choose whether to send. It does not send the report automatically or attach schedule files. If sent, the message passes through your configured email provider and is kept in our support inbox and any configured forwarding as described above; your mail provider may also retain a sent copy. If you save a draft, it remains in your mail drafts. If mail is unavailable, the app offers the support website without transferring your draft; that form asks you to enter your name, email, help topic, message, and optional school or district. If you open Request Your School, the website practices in this policy apply to anything you submit there.
Removal. You can remove saved schedules in the app and use your device’s app-data or uninstall controls for local data. Removing data on one device does not necessarily remove a Watch copy, a device backup, or a schedule file you shared or saved elsewhere. Use the relevant device, backup, or recipient controls for those copies.
13. BellSync Web Display
Web Display runs in your browser. Schedules you create or import and display preferences are saved in that browser’s local storage so they can appear when you return on the same browser and device. Imported BellSync or Web Display schedule files are read in the browser; their contents are not uploaded to a BellSync server by the Web Display import. Its built-in school resources are downloaded from the Web Display host.
You can download a schedule or collection as a Web Display backup file. The file is saved where your browser places downloads or where you choose, and anyone you give it to may see its contents. Removing a schedule in Web Display or clearing that site’s browser data removes the local browser copy; it does not remove exported files or copies on other devices. Browser settings, private browsing, and storage limits can affect whether local data persists.
Visiting Web Display still makes ordinary requests to its hosting provider, which may process the technical information described above. If you follow its links to the BellSync support or school-request website, those separate website forms handle only information you choose to submit.
14. BellSync for Android test builds
BellSync for Android is not publicly released. This section describes existing test-build behavior for people who have access to a build; it does not announce Android availability.
Local schedules and preferences. The Android app stores saved schedule profiles, profile names, class and activity names, rooms, colors, lunch choices, Bell Timing Adjustment, appearance settings, and reminder preferences in its private app storage. This information supports schedule displays, countdowns, and local reminders. The app does not upload saved profiles to a BellSync server or require a BellSync account. BellSync does not include advertising, analytics, or an automatic crash-report upload service in the Android app.
Device backups. Depending on your Android settings, Android may back up saved profiles and preferences to your device’s backup service or transfer them to another device. BellSync does not operate that service. The app’s backup configuration includes profiles, reminder preferences, and appearance preferences; it excludes alarm queues, diagnostic history, and Garmin synchronization metadata. Backup copies are managed through your backup provider’s controls.
Local notifications. Notification permission is optional. Reminders are planned locally using your stored schedule information and preferences. If allowed, notifications may show class names, activity names, and rooms on your lock screen or other devices connected to your phone, depending on your system and companion-app settings. You can disable BellSync notifications without deleting your reminder preferences.
Website links and support. Request Your School and the privacy-policy link open your browser. BellSync does not attach your saved schedule to those links. Information you choose to submit through the website or send to support is covered by this policy’s website and support sections. Your browser and the website may process ordinary web-request information as described above.
15. Optional Garmin synchronization in Android test builds
Garmin synchronization is optional and defaults off. You can use BellSync’s Android scheduling, countdowns, and local reminders without it. After you set it up, BellSync uses Garmin’s Connect IQ companion SDK and the Garmin Connect app to send the active schedule to configured, eligible paired watches running BellSync.
Transferred information includes profile and school names and identifiers, school dates, rotation and schedule labels, activity identifiers, class or activity names, rooms when supplied, effective activity start and end times, end-of-day markers, and a synchronization timestamp. This may include information you entered yourself. Bell Timing Adjustment is reflected in the transferred times. Notification preferences and notification history are not included in this schedule message.
After setup, updated schedules may be sent automatically while BellSync is open, including after schedule or profile changes, reconnection, or returning to the app. BellSync uses watch identifiers, connection status, and information about whether BellSync is installed on a watch to route transfers. Selected watch identifiers and synchronization receipts are stored locally.
To stop schedule transfers, open Settings → Garmin → Choose Garmin Watches and deselect all listed watches. Clearing BellSync’s app storage also resets Garmin setup. Stopping transfers or deleting a phone profile does not erase a schedule already sent to a watch.
Garmin Connect and your watch handle transferred copies. Garmin’s services are subject to Garmin’s privacy terms. We have not verified Garmin’s server handling or retention of schedule data, transport encryption, telemetry, or deletion behavior. We do not guarantee how Garmin handles or deletes transferred copies.
16. Android test-build storage and deletion
BellSync uses Android’s private app storage and does not operate a server containing your Android saved profiles. Manage Schedules lets you delete an individual phone profile. Android’s Clear storage control removes BellSync’s local profiles, preferences, and synchronization metadata. Android manages the app’s local files when it is uninstalled.
Deleting phone data does not necessarily delete copies previously transferred to Garmin Connect, a watch, or a backup provider, and it does not delete information you submitted separately to support or through the website. Use the relevant watch or provider’s controls and support process for those copies. Contact support@bellsync.app for help with information you submitted to BellSync. We do not promise that removing a phone profile deletes data held by an external service.
17. Policy changes and contact
We may update this policy as BellSync’s apps, Web Display, website, school request workflow, or support services change. The current version will be posted on this page with an updated date. If a change involves a new use of Google data or different permissions, we will provide the required notice and seek authorization before that new access or use.
For questions about privacy or how your information is handled, contact Strategic Edits LLC, the operator of BellSync, at support@bellsync.app.
