FLO OPS, LLC. PRIVACY POLICY
FLO OPS, LLC.
PRIVACY POLICY
We at FLO-OPS, LLC, take privacy and our obligation to protect your information very seriously. Our aim is to improve as much as possible the learning experience for students, teachers, and professors of all ages and backgrounds. Any personal information we collect is used toward that specific aim and no other. We do not monetize your data, we do not and will not sell or rent your data to third parties unless this is required in the context of changes to our business structure such as a merger or acquisition. What information does Flo-Ops collect?
We provide our services and products to you through agreement with your school or institution, and allow them to process and control your data, sharing it with us for the sole purpose of fulfilling our application’s various functions. Therefore, the main responsibility for data protection lies with your school or institution. We are always careful to follow the guidelines given to us by each partner school or institution, we therefore encourage you to read through your school or institution’s privacy policy in addition to our policy here. When you use our software application, the information we collect directly or indirectly from you includes:
Your Profile Information:
including your first and last name, email address, a photo of yourself (optional) and your date of birth.
Your Credentials:
through integration with the information database and the eLearning platform(s) already in use your school or institution, our software application collects the credentials used therein to identify you, including (where allowed) your username, passwords, password hints, security questions, and other information used for authenticating your account.
Your Uploaded Content and Activity:
including any data, documents, audio or video files, photos, related metadata, and any other information uploaded or input by you into the software application for assignments, note taking, quizzes, course work, chat messaging, comments, feedback, and any other activity while using the software application.
Your Support Queries:
including any information provided when you or your school or institution contacts us for support. We use this information to assist with solving any issues in our software application. When you contact us directly, your phone conversations or chat sessions with our support team may be monitored and recorded for quality improvement and training purposes.
Your Location and Device Usage Data:
In certain instances, with your permission, we will collect information about your device including any unique device identifier, Internet Protocol address, browser type and configuration, and your location while using the software application. We also collect device usage data when you use the software application including date and time of your use, language preferences, and cookie data.
How does Flo-Ops use this information?
Any information we collect from you whether directly or indirectly, is used to improve as much as possible the learning experience for students, teachers, and professors of all ages and backgrounds, nothing more. Specifically, what we do with your information and data will fall into one or more of the following categories:
Analytics:
improving and maintaining our software application’s functionality requires us to monitor the performance and transmission of information and data as it passes through the application. We use this information to evaluate and enhance our software application and for research and development purposes specific to our learning management system as a whole.
Under Instruction from Your School or Institution:
we use the information we collect from you in accordance with the agreement FLO entered into with your school or institution and in accordance with the privacy policy therein adopted. So long as neither this policy nor the school or institution’s policy is violated, we will use the information you provide to follow any specific instructions or requests from your school or institution.
Who does FLO share this information with?
We do not monetize your data. We do not and will not sell or rent your data to third parties for any circumstance other than that which is specifically required in the context of changes to our business structure such as a merger or acquisition. The only third parties we share your information with are:
Your School or Institution:
we may share the information we collect with the school, university, company, or other institution in which you are enrolled in a class or course of study using FLO as a learning management tool; also
Your School or Institution’s Providers:
we may share your information with any Learning Management Software providers or other providers already in use at your school or institution (e.g. BlackBoard, Moodle, Canvas, etc.) for the purpose of integrating our software application for immediate use in your given course of study.
Security
We employ a variety of physical, administrative, and technological safeguards designed to protect personal information against loss, misuse, and unauthorized access or disclosure. We have dedicated information security programs and work hard to continuously enhance our technical and operational security measures. Our measures consider the sensitivity of the information we collect, use, and store, and the current state of technology. Our security measures include data encryption, firewalls, data use, and access limitations for our personnel and vendors and physical access controls to our facilities. Protecting your information is our priority.
Your Rights
United States – FERPA and state education privacy laws
We provide educational products and services to schools and other educational institutions. Through the provision of these products and services, we collect personally identifiable information from or about students (“Student Data”), which may include educational records governed by the Family Educational Rights and Privacy Act (FERPA). We consider such Student Data to be strictly confidential and in general do not use such data for any purpose other than improving and providing our products and services to the educational institution or on the educational institution’s behalf. Our collection, use, and sharing of Student Data is governed by our contracts with the educational institutions, the provisions of FERPA, the Children’s Online Privacy Protection Act (“COPPA”), and other applicable laws that relate to the collection and use of personal information of students, but not by the provisions contained in this Privacy Statement. If you have any questions about reviewing, modifying, or deleting personal information of a student, please contact your educational institution directly. In compliance with the law, we do not knowingly collect any information from children under the age of 13 until and unless the relevant school, parent or institution has provided the necessary consent and authorization for the person under age 13 to use our software application and for us to collect and use the information from said person. Where a client school or institution instructs us to collect personal information from children under the age of 13, we collect, use, process and retain such information solely to provide the educational services on behalf of the client and for the purposes set forth in our agreement with the client. We collect only as much information as is necessary to provide the service and the client may access, delete or withdraw consent for continued processing of the child’s information at any time.
Contact Us
If you are and end user of our software application we provide on behalf of your school or institution, please contact your school or institution first as your institution’s privacy statement and data privacy practices will determine how FLO uses personal information on your school or institution’s behalf. If you have a technical or support issue, please contact the helpdesk of your school or institution. If you have any questions or concerns about our Privacy Statement or our own data privacy practices, contact us at the following address.
FLO OPS, LLC 621 NW 53rd Street Suite 125 Boca Raton, FL 33487
Attention: Privacy Boca Raton, FL 33431
Flo-Ops Accessibility Statement
Flo-ops is committed to ensuring its products are inclusive and meet the diverse accessibility needs of our users. Flo-Ops strives for WCAG 2.1 Level A/AA and Section 508 conformance. Regular testing (internal) is conducted to identify conformance issues, with processes in place for timely remediation of accessibility issues that are identified.
The statements below are accurate as of the date indicated.
Flo-ops has been internally evaluated to meet requirements according to WCAG 2.1 standards. Testing is regularly conducted using automated tools, assistive technology, and coding best practices. Accessibility evaluation occurs regularly with internal audits conducted with each release. Mechanisms are in place for logging and fixing accessibility defects.
Flo-Ops Voluntary Product Accessibility Template (VPAT)
Flo Ops Mobile App LMS Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Name of Product: Flo Ops LMS (Mobile)
Date: June 2024
Contact Information: accessibility@flo-ops.com
Evaluation Methods Used: Manual testing by Flo Ops with supported screen readers
(VoiceOver, NVDA, JAWS) and other accessibility technologies.
Applicable Standards/Guidelines: This report covers the degree of conformance for the
following accessibility standard/guidelines:
- Revised Section 508 standards as published by the U.S. Access Board in the Federal
Register on January 18, 2017 - Web Content Accessibility Guidelines 2.1 (Level A/AA)
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the
criterion without known defects or meets with equivalent facilitation. - Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.1 Report
This table documents conformance of the Flo Ops mobile app LMS (including mobile content, electronic documents, software components, and authoring systems) with WCAG 2.1.
Table 1: Success Criteria, Level A/AA
| Criteria | Conformance Level | Remarks and Explanations |
| 1.1.1 Non-text Content (Level A) | Supports | Image Alt text is available for uploaded content. e.g. image. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Supports | Videos have captions and subtitles, including embedded YouTube videos that utilize YouTube’s caption functionality. For audio, we have added a transcription feature. When the user presses “i” on the audio, a drop down displays the transcribed text. Users can manually edit and correct the text. |
| 1.2.2 Captions (Prerecorded) (Level A) | Supports | Videos have captions and subtitles, including embedded YouTube videos that utilize YouTube’s caption functionality. For audio, we have added a transcription feature. When the user presses “i” on the audio, a drop down displays the transcribed text. Users can manually edit and correct the text. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Supports | Videos have captions and subtitles, including embedded YouTube videos that utilize YouTube’s caption functionality. For audio, we have added a transcription feature. When the user presses “i” on the audio, a drop down displays the transcribed text. Users can manually edit and correct the text. |
| 1.2.4 Captions (Live) (Level AA) | N/A | Only pre-recorded videos are on the platform, no live video |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | Supports | Users are responsible for the accessibility of the content they upload. Our mobile app does not currently support multiple audio tracks, however, users can upload a version of video content that contains audio descriptions. |
| 1.3.1 Info and Relationships (Level A) | Partially supports | Most of the information, structure, and relationships can be programmatically determined or are available in text. On some screens, help text/label cannot be determined programmatically after the value is entered in input field. |
| 1.3.2 Meaningful Sequence (Level A) | Partially supports | Application maintains consistent structures allowing correct reading sequences to be programmatically determined. However, selected tab cannot be determines programmatically on some screens. |
| 1.3.3 Sensory Characteristics (Level A) | Supports | All instructions are text-based and do not rely on colour, shape, or sound alone |
| 1.3.4 Orientation (Level AA 2.1 Only) | Not supported | Currently, only portrait mode is supported |
| 1.3.5 Identify input Purpose (Level AA 2.1 Only) | Supports | Input field purposes can be programmatically determined. |
| 1.4.1 Use of Color (Level A) | Supports | colour is not the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. |
| 1.4.2 Audio Control (Level A) | Supports | No audio plays automatically. Also, user can pause and resume the playback of the sound |
| 1.4.3 Contrast (Minimum) (Level AA) | Supports | App provides a contrast ratio of 5:1 |
| 1.4.4 Resize text (Level AA) | Supports | Users can adjust text size without losing content or functionality. |
| 1.4.5 Images of Text (Level AA) | Supports | Users can add detailed descriptions in a separate text field accompanying the image. Basically giving a summary or detailed explanation rather than an exact transcription. |
| 1.4.10 Reflow (Level AA 2.1 Only) | Supports | With magnification, the functionality and text do not break. |
| 1.4.11 Non-text Contrast (Level AA 2.1 Only) | Supports | All the graphical objects and user interface elements meet or exceed the minimum 3:1 contrast. |
| 1.4.12 Text Spacing (Level AA 2.1 Only) | Supports | The text remains readable and functional at increased sizes, indicating that the text spacing meets this criteria. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 Only) | Supports | The app’s interactive elements were tested for focus actions; any additional content remains visible, is dismissible, and does not disappear unexpectedly. |
| 2.1.1 Keyboard (Level A) | Supports | All functionality can be operated via keyboard alone |
| 2.1.2 No Keyboard Trap (Level A) | Supports | User does not get trapped in the application when using the built-in keyboard of the application |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) | N/A | |
| 2.2.1 Timing Adjustable (Level A) | N/A | |
| 2.2.2 Pause, Stop, Hide (Level A) | N/A | |
| 2.3.1 Three Flashes or Below Threshold (Leve A) | N/A | |
| 2.4.1 Bypass Blocks (Level A) | Partially supports | There are no repeated blocks of contents in the app. On some (not all) screens, user can directly navigate to the home screen or to the parent section. |
| 2.4.2 Page Titled (Level A) | Supports | Each page has a title that describes its topic or purpose. |
| 2.4.3 Focus Order (Level A) | Supports | focus order preserves a meaningful and logical sequence. |
| 2.4.4 Link Purpose (In Context) (Level A) | Supports | The purpose of each link in the app is clearly identified by its text, supplemented with labels when necessary. |
| 2.4.5 Multiple Ways (Level AA) | Partially supported | Currently, users can use the footer menu items to navigate to different sections of the application. |
| 2.4.6 Headings and Labels (Level AA) | Supports | Headings and labels clearly describe the topic or purpose of the content and headings can be programmatically determined. |
| 2.4.7 Focus Visible (Level AA) | Supports | The app provides a visible focus indicator) on input fields and other interactive elements. |
| 2.5.1 Pointer Gestures (Level A 2.1 only) | N/A | |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) | Supports | Functionality that can be operated with a single pointer has at least one of the following: No Down-Event, Abort or Undo, Up Reversal, or Essential. |
| 2.5.3 Label in Name (Level A 2.1 only) | Supports | User interface components with labels that include text or images of text, the name contains the text that is presented visually. |
| 2.5.4 Motion Actuation (Level A 2.1 only) | N/A | |
| 3.1.1 Language of Page (Level A) | Supports | The default language of the app is set to English |
| 3.1.2 Language of Parts (Level AA) | N/A | The app content is exclusively in English, with no sections in other languages. |
| 3.2.1 On Focus (Level A) | Supports | when any component receives focus, it does not initiate a change of context |
| 3.2.2 On Input (Level A) | Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. |
| 3.2.3 Consistent Navigation (Level AA) | Supports | App contains consistent navigation patterns across all pages and content. |
| 3.2.4 Consistent Identification (Level AA) | Supports | All the components are labeled and behave consistently across the application. |
| 3.3.1 Error Identification (Level A) | Partially supported | If an input error is automatically detected, the item that is in error is identified, and the error is described to the user in text. However, some messages that are in the form of toast cannot be recognised programmatically. |
| 3.3.2 Labels or Instructions (Level A) | Supports | Labels or instructions are provided when content requires user input. |
| 3.3.3 Error Suggestion (Level AA) | Partially supported | For all errors, some form of announcement is made. However, error messages shown through toast are not recognizable programmatically. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | N/A | The app does not involve the submission of legal commitments, financial transactions, or data that could significantly impact users. |
| 4.1.1 Parsing (Level A) | Supports | Elements in the app’s content are well-formed, with correct nesting and unique attributes. |
| 4.1.2 Name, Role, Value (Level A) | Supports | All user interface components, the name and role can be programmatically determined. |
| 4.1.3 Status Messages (Level AA 2.1 only) | Partially supported | The error messages and status messages are shown where needed, however, these messages are not recognized programmatically. |
Section 508
Functional Performance Criteria (FPC)
Criteria | Conformance Level | Remarks and Explanations |
Without Vision | Supports | Provides descriptive text alternatives for non-text content, assisting users relying on screen readers. |
With Limited Vision | Supports | Allows users to adjust text size without loss of content or functionality, aiding those with visual impairments. |
Without Perception of Color | Supports | Does not require color perception for operation. |
Without Hearing | Supports | Provides text transcripts or captions for audio and video content, supporting users with hearing impairments. |
With Limited Hearing | Supports | Provides text transcripts or captions for audio and video content, supporting users with hearing impairments. |
Without Speech | N/A | Does not require speech for operation. |
With Limited Manipulation | Supports | All functionality can be operated via keyboard, aiding users with limited manipulation abilities. |
With Limited Reach and Strength | Supports | Keyboard accessibility ensures functionality for users with limited reach and strength. |
With Limited Language, Cognitive, and Learning Abilities | Supports | supports adaptation of content by end users and provides an easy-to-use interface for users with cognitive or learning disabilities. |
Chapter 4 Hardware
Note: These criteria are all Not Applicable because Flo Ops is not a Hardware Product.
Chapter 5 Software
Authoring Tools
Criteria | Conformance Level | Remarks and Explanations |
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | N/A | Flo Ops LMS web app does not provide templates for content creation or editing. |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | N/A | Flo Ops LMS web app does not provide templates for content creation or editing. |
504.2.2 PDF Export | N/A | Flo Ops LMS web app does not provide templates for content creation or editing. |
504.3 Prompts | N/A | Flo Ops LMS web app does not provide templates for content creation or editing. |
504.4 Templates | N/A | Flo Ops LMS web app does not provide templates for content creation or editing. |
Chapter 6: Support Documentation and Services
Criteria | Conformance Level | Remarks and Explanations |
602: Support Documentation | ||
602.2 Accessibility and Compatibility Features | Supports | Privacy policy https://flo-ops.com/policy/ provides details on accessibility features |
602.3 Electronic Support Documentation | Supports | Support documentation is available in the form of Youtube video guides and use guide in PDF format. Customer onboarding email contains links to the support documentation. |
602.4 Alternate Formats for Non-Electronic Support Documentation | N/A | |
603: Support Services | Supports | Support is available in the form of: |
603.2 Information on Accessibility and Compatibility Features | Supports | Customer Support can |
603.3 Accommodation of Communication Needs |
Flo Ops WebApp LMS Accessibility Conformance Report
(Based on VPAT® Version 2.4)
Name of Product: Flo Ops LMS (Web)
Date: June 2024
Contact Information: accessibility@flo-ops.com
Evaluation Methods Used: Manual testing by Flo Ops with supported screen readers (VoiceOver, NVDA, JAWS) and other accessibility technologies.
Applicable Standards/Guidelines: This report covers the degree of conformance for the following accessibility standard/guidelines:
- Revised Section 508 standards as published by the U.S. Access Board in the Federal Register on January 18, 2017
- Web Content Accessibility Guidelines 2.1 (Level A/AA)
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
WCAG 2.1 Report
This table documents conformance of the Flo Ops mobile app LMS (including mobile content, electronic documents, software components, and authoring systems) with WCAG 2.1.
Table 1: Success Criteria, Level A/AA
Criteria | Conformance Level | Remarks and Explanations |
N/A | We do not upload any | |
N/A | We do not upload any | |
N/A | We do not upload any | |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | N/A | We do not upload any |
N/A | We do not upload any | |
Supports | Users are responsible for | |
Partially supports | Most of the information, | |
Partially supports | Application maintains | |
Supports | All instructions are | |
N/A |
| |
Partially Supports | Input field purposes can | |
Supports | color is not the only | |
Supports | No audio plays automatically. Also, user can pause and resume the playback of the sound | |
Partially supports | The Web App provides | |
Supports | Users can adjust text | |
N/A | We do not upload any | |
Supports | With magnification, the functionality and text do not break. | |
Partially supports | Most of the graphical | |
Supports | The text remains readable and functional at increased sizes, indicating that the text spacing meets this criteria. | |
Supports | The app’s interactive elements were tested for focus actions; any additional content remains visible, is dismissible, and does not disappear unexpectedly. | |
Supports | All functionality can be operated via keyboard alone | |
Supports | User does not get trapped in the application when using the built-in keyboard of the application | |
N/A | ||
N/A | ||
N/A | ||
N/A | ||
Partially supports | There are no repeated blocks of contents in the app. On most (not all) screens, user can directly navigate to the home screen or to the parent section. | |
Supports | The page title is | |
Supports | focus order preserves a meaningful and logical sequence. | |
Supports | The purpose of each link in the app is clearly identified by its text, supplemented with labels when necessary. | |
Partially supported | Currently, users can use the footer menu items to navigate to different sections of the application | |
Supports | All of the headings and | |
Supports | The app provides a visible focus indicator) on input fields and other interactive elements. | |
N/A | ||
Supports | Functionality that can be operated with a single pointer has at least one of the following: No Down-Event, Abort or Undo, Up Reversal, or Essential. | |
Supports | User interface components with labels that include text or images of text, the name contains the text that is presented visually. | |
N/A | ||
Supports | The default language of the app is set to English | |
N/A | The app content is exclusively in English, with no sections in other languages. | |
Supports | when any component receives focus, it does not initiate a change of context | |
Supports | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behaviour before using the component. | |
Supports | App contains consistent navigation patterns across all pages and content. | |
Supports | All the components are labelled and behave consistently across the application. | |
Supports | If an input error is | |
Supports | Labels or instructions are provided when content requires user input. | |
Supports | For all errors, some form | |
N/A | The app does not involve the submission of legal commitments, financial transactions, or data that could significantly impact users. | |
Supports | Elements in the app’s content are well-formed, with correct nesting and unique attributes. | |
Supports | All user interface | |
Supports | The error messages and |
Section 508
Functional Performance Criteria (FPC)
Criteria | Conformance Level | Remarks and Explanations |
Without Vision | Supports | Provides descriptive text alternatives for non-text content, assisting users relying on screen readers. |
With Limited Vision | Supports | Allows users to adjust text size without loss of content or functionality, aiding those with visual impairments. |
Without Perception of Color | Supports | Does not require color perception for operation. |
Without Hearing | Supports | Provides text transcripts or captions for audio and video content, supporting users with hearing impairments. |
With Limited Hearing | Supports | Provides text transcripts or captions for audio and video content, supporting users with hearing impairments. |
Without Speech | N/A | Does not require speech for operation. |
With Limited Manipulation | Supports | All functionality can be operated via keyboard, aiding users with limited manipulation abilities. |
With Limited Reach and Strength | Supports | Keyboard accessibility ensures functionality for users with limited reach and strength. |
With Limited Language, Cognitive, and Learning Abilities | Supports | supports adaptation of content by end users and provides an easy-to-use interface for users with cognitive or learning disabilities. |
Chapter 4 Hardware
Note: These criteria are all Not Applicable because Flo Ops is not a Hardware Product.
Chapter 5 Software
Authoring Tools
Criteria | Conformance Level | Remarks and Explanations |
504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | N/A | Flo Ops LMS mobile app does not provide templates for content creation or editing. |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | N/A | Flo Ops LMS mobile app does not provide templates for content creation or editing. |
504.2.2 PDF Export | N/A | Flo Ops LMS mobile app does not provide templates for content creation or editing. |
504.3 Prompts | N/A | Flo Ops LMS mobile app does not provide templates for content creation or editing. |
504.4 Templates | N/A | Flo Ops LMS mobile app does not provide templates for content creation or editing. |
Chapter 6: Support Documentation and Services
Criteria | Conformance Level | Remarks and Explanations |
602: Support Documentation | ||
602.2 Accessibility and Compatibility Features | Supports | Privacy policy https://flo-ops.com/policy/ provides details on accessibility features |
602.3 Electronic Support Documentation | Supports | Support documentation is available in the form of Youtube video guides and use guide in PDF format. Customer onboarding email contains links to the support documentation. |
602.4 Alternate Formats for Non-Electronic Support Documentation | N/A | |
603: Support Services | Supports | Support is available in the form of: |
603.2 Information on Accessibility and Compatibility Features | Supports | Customer Support can provide information about accessibility features of the product. |
603.3 Accommodation of Communication Needs |
