Pilot guidelines
A clear, useful, and responsible 60-day pilot.
These plain-language guidelines set expectations for organizations invited to test DevFloHQ. A final participation agreement will be confirmed directly before access is provided.
Purpose and duration
The pilot is a 60-day evaluation intended to determine whether DevFloHQ creates practical value and what should improve. It is not a promise of permanent free service.
Participation
Each organization designates a primary participant, uses the platform consistently, attends onboarding and feedback conversations, and reports problems or confusing workflows honestly.
Data responsibility
The organization must enter only information it is authorized to use. Sensitive medical, client, employee, program-participant, payment-card, or legally protected data should not be entered during the pilot.
Access and confidentiality
Login credentials must not be shared. Participants should access only their own organization’s workspace and promptly report suspected unauthorized access.
Feedback
Participants agree that product feedback may be used to improve DevFloHQ. Public testimonials, organization names, or identifiable stories will not be used without separate permission.
End of pilot
At the end of 60 days, the organization may continue under an agreed future plan, export needed information and discontinue use, or extend the pilot only by mutual agreement. No automatic charge occurs.
Early-stage limitations
The pilot is provided for evaluation. Features may change, and interruptions or errors may occur. Organizations should retain appropriate source records and should not treat DevFloHQ as the sole record for legally required documentation during the pilot.
These guidelines are an operational starting point, not a substitute for legal advice. A lawyer should review commercial terms and privacy obligations before a broader paid launch.