Template disclosure · Version 1.0 · 4 November 2026
1. Who operates this demonstration?
Relaypoint is a fictional product name used by this MIT-licensed website template. There is no fictional company receiving your submissions. If you adapt or host the template, replace this disclosure with information about your real operator, actual processing, and contact route.
2. Local demo information.
Workspace, profile, and preference demonstrations use browser-local data. Where saved, this data stays in local storage on the current browser and device. It is not a secure account store, is not shared with a team, and may be visible to other people using the same browser profile.
Use fictional information while exploring. The template does not need your real password, payment details, confidential customer records, or identity documents.
3. Contact and application forms.
The contact and career application demonstrations show local acknowledgments. They do not email a sales team or recruiter. There is no server-side submission store in this template.
4. Optional direct API requests.
The public preview has no credentials and blocks live requests. When your authorized downloaded configuration enables access, submitting the AI workflow form sends its prompt and the page’s workflow guidance to AI.Mihajlo.mk. Submitting the email check sends the supplied email address to that service.
Those requests include your configured development authorization. The external service processes requests under its own terms and policies. Review those policies through the service documentation before submitting personal or sensitive information.
Smart Routing AI documentation ↗ · Email Validator documentation ↗
5. Cookies, analytics, and assets.
The supplied template adds no analytics, advertising pixels, tracking cookies, or remote font requests. Styles, scripts, icons, and diagrams are bundled locally. Your hosting provider may keep ordinary access logs; its practices are separate from this template.
6. Clearing local data.
The sample workspace includes a reset control for workflow records. You can remove all local template data by clearing this site’s storage in your browser. Downloaded CSV files remain wherever you saved them and must be deleted separately. Clearing local data does not delete API provider records or reset account quotas.
7. Public configuration and account access.
Frontend configuration is inspectable. Keep personalized development credentials out of public repositories and hosted previews. A production application should use a secure backend and real authorization controls.
8. Questions and adaptation.
For the demonstration, the trust center explains the implementation boundaries. A real deployment needs its own operator contact details, data retention practices, and user request process.