Questions belong here.

IAPont is a workspace for opening a document, refining its source and seeing its presentation. Compare editorial profiles, then export your text for its next use, without locking it into a new tool.

The document workflow needs no IAPont account or connection to an AI service. Start with your own text. Structural checks and conversions do not automatically establish whether your information is true.

The interface is designed for opening, editing, previewing and exporting on phones and computers. Use Open file and your device's picker. Drag and drop is optional; the layout adapts to the available space.

Choose Open file, paste text or try an example. After an accepted import, source and preview appear without a Generate button. If there is an error, read the message to understand the limit encountered.

Start with ordinary paragraphs. Editing commands help insert headings, lists, links and emphasis. A short example shows what the notation does before you prepare a full article.

Markdown, TXT, IAPont document JSON and targeted imports of text PDFs and unprotected EPUBs are supported. This is not universal layout reconstruction: protected, damaged or unsupported documents may be rejected with an explanation.

A scanned page can be an image rather than extractable text. The local importer is not a universal OCR tool. It reports when it cannot find usable text rather than claiming a successful conversion.

IAPont edits a copy opened in the workspace. Editing does not automatically rewrite your device's file. Export the result and choose where to keep it outside the browser.

A profile changes presentation, not your source. Kachouri, Pierre Gassin and IAPont profiles offer different layouts. The preview is a simulation, not a certified reproduction of another site; substitute fonts and simulated media remain identified.

Mobile, Tablet and Desktop change the document's layout width inside the preview. This helps inspect headings, tables and reading rhythm, but does not replace testing on a real device with its keyboard and browser.

A document must not automatically contact external image servers. Media unavailable in the supported local workflow appears as a clearly simulated placeholder, so you can inspect the layout without an automatic network request.

Vault copies stay in this browser's storage for IAPont. They are not a folder synchronized across devices. Document copies use IndexedDB; small interface preferences have a different role.

Not on a different device or browser. Export the document and open that copy elsewhere. No automatic phone-to-computer synchronization is claimed.

No. Browser quotas, eviction or deletion of site data can remove copies. Keep exported backups of important documents. Saved means a write succeeded in this browser, not on another storage device.

It closes the active document, clears the preview and stops reading. It does not delete the original file or copies already saved in the vault. Unsaved edits require confirmation before closing.

Open the vault and use the deletion action for that copy. Read the confirmation, including any versions affected. Clearing the workspace and deleting a saved copy are separate actions.

Keep the tab open and export a copy. Check browser storage permissions and available space, then retry. A failed save must not prevent reading or exporting the text still in the workspace.

The Device storage panel shows the browser's estimate when available. It is not an exact measurement of your entire disk. If no estimate is available, the interface says so instead of inventing a value.

It asks the browser to protect site data from automatic eviction. The browser can refuse. It adds neither device synchronization nor encryption and cannot prevent deliberate deletion of site data.

Export the selected copies and versions. Restoration previews conflicts before writing and never silently replaces an existing document. Check your downloaded file: starting a download does not guarantee it was kept.

The local workflow offers only voices reported as local by the browser. Availability depends on your system. Without a suitable local voice, the text remains readable and no remote speech service silently takes over.

Speech engines expose different word boundaries. IAPont uses the available information and falls back to paragraph tracking when precise tracking is unavailable. It does not invent progress with a timer.

Use Markdown to continue editing, HTML for presentation or TXT for plain text. JSON and JSONL carry the structures actually prepared. PDF import does not imply PDF export; read the displayed limits.

No. ITYLOS, RoastMyURL and other cards are links, not automatic document transfers. You choose what to do on the destination site. A logo is not a security label or an audit certificate.

IAPont prepares passages and metadata. RAG preparation organizes what other tools will retrieve; the OAM discussion on Kachouri addresses context, relationships and changes over time. IAPont is not itself a question-answering engine or a complete OAM implementation.

No. Local describes document processing in the browser. Initially loading the application and its assets can require a connection. Complete offline operation needs separate verification.

Discovery files and the FAQ describe public product pages only. They do not contain your text, filenames, personal metadata or vault copies. Public discoverability does not require exposing private documents.

Give the page, device, browser, steps and visible error. Prefer a small non-confidential example. For security issues, use the published security.txt contact when configured; do not expose sensitive documents in a public screenshot.