Editra is a self-hostable, browser-native WYSIWYG editor application. Its core edits document content locally and does not send that content to Editra by default. The organization embedding Editra decides where documents are stored, which plugins and network features are enabled, and how users are authenticated. The public Editra website is covered separately below and does not require an account or payment.
Editra processes document content in the browser and does not require an Editra account, store documents in an Editra database, or send editor content to Editra by default. An organization embedding Editra controls its users, document storage, retention, and privacy notices.
A textarea synchronizes sanitized HTML to its form control; a div keeps content in the editing surface. Plugins, remote media, collaboration, exports, or callbacks may connect to services selected by the integrator, who is responsible for disclosing that processing.
Demos process editor content in the browser. Theme preferences and feedback drafts may be stored locally. Submitted feedback is sent through FormSubmit to the maintainer. Website infrastructure and third-party resources may receive standard request information. Editra does not sell visitor information.
Editra provides sanitization and plugin boundaries, while the host application remains responsible for authentication, authorization, encryption, and server-side validation. Local values remain until cleared; feedback is retained only as reasonably needed to respond.
You can clear local website data, avoid confidential information in public demos, block optional third-party resources, or self-host Editra. Requests about website information may be sent to support@editra.in. For an embedded Editra instance, contact that application's operator.
Transparency, not certification. Editra provides controls that can support privacy-conscious implementations; this page does not claim that every integration is automatically compliant with every law or industry standard.