ISOHub
← Back to ISOHubISOHUB / PRIVACY

Your data deserves care.

Development privacy and processing overview.

What the workspace handles

When account services are configured, ISOHub stores your name, email, authentication records, sessions, workspace notes, saved residual assumptions, aggregate statement reviews, proposal drafts, agent page drafts and conversations you choose to save. Technical session information can include your IP address and browser information. Essential session cookies keep you signed in; your theme preference is stored in your browser.

Local statement reading and optional image analysis

You can select PDFs or JPEG/PNG images, or use your camera to capture multiple pages. PDF rendering and English OCR run locally in your browser using reader assets hosted by ISOHub. Selecting files and reading locally do not transmit statement content. If image AI analysis is activated, a signed-in agent may separately review and consent to sending rendered page images through ISOHub to OpenAI. Original PDFs are not sent. The optional text analysis path sends only the text you review. Nothing is sent to PaymentUSA. The camera starts only when you request it and your browser grants access; it stops when you finish, start reading, leave the page or hide the tab.

Source pages and extracted text remain in this tab's memory until you clear them, start a new review or reload. They are not restored with saved reviews. Your browser or operating system may independently retain camera captures or selected originals. Local OCR suggests values and requires your verification; it is not a complete fee audit. Only aggregate amounts, counts, fee categories, page numbers and verification status are included when you explicitly save a summary to your private account. Do not include merchant identifiers in review labels, notes or AI chat. Server-side document storage remains unavailable pending separate privacy and security controls.

Optional AI image analysis

Image analysis has separate activation and consent controls. Before sending, review every image and remove merchant identifiers, bank or card details and other personal information. Images are not automatically redacted. The optional local privacy editor lets you manually cover selected areas with opaque pixels. Applying masks replaces that page’s local image and clears its embedded text and earlier readings; your original file is unchanged. You must check all pages for remaining identifiers. ISOHub validates, decodes and reencodes JPEG pages without metadata, then sends all pages together to OpenAI. This processing is not a malware scan. Application code does not persist the image copies or log their contents; content-free consent and usage records are kept. Provider retention rules still apply even when response storage is disabled. AI source quotes are visual transcriptions, not independently verified evidence. Confirm each finding against the original page.

Optional AI statement interpretation

When the operator activates this feature, a signed-in agent can review and edit automatically redacted text for every page. Automatic redaction is incomplete by nature: remove business names, addresses and all personal or financial identifiers yourself. Confirm permission and processing consent before choosing Analyze with AI. Only that reviewed text is sent through ISOHub to the configured OpenAI model. It is not used as a privileged instruction, stored in the workspace or logged by application code. The response stays in this tab; explicitly importing and saving values retains only aggregate worksheet fields. Hosting/APM body capture must remain off.

Before an accepted AI analysis request proceeds, ISOHub records the version of the consent notice you accepted, a receipt ID, your account ID and a timestamp. This receipt contains no statement text or extracted amounts. It records acceptance, not proof that you reviewed every page or that analysis succeeded. You can export your own receipts from Settings. Account deletion removes their link to your account; audit retention is a separate policy still requiring final operator review.

Provider response storage is disabled, but this alone does not guarantee zero retention. The operator must document applicable OpenAI retention and processing terms before activating this feature. AI statement processing is disabled by default and requires a separate privacy-review flag and approved spending. Cancelled or failed calls can still consume the reserved allowance. Model confidence, quote matches and arithmetic reconciliation do not establish a complete or accurate statement audit; verify all numbers against the original.

Proposals, public pages and inquiries

Saved proposals may contain merchant business names, agent contact details, entered terms and aggregate statement snapshots. Local logos are not uploaded or saved. Printing uses your browser; ISOHub does not send the PDF to a third party. Public agent pages are published only on your explicit action and expose the identity, contact details and service descriptions you chose to publish. Unpublishing removes public access; saved drafts and inquiries remain private.

Some agent pages offer a payment-conversation planner. Its channel, goal and timing choices stay in the current page; generating or downloading the checklist does not send them to ISOHub, the agent or an AI provider. If you choose to include the plan in an inquiry, those details become part of the message you review and explicitly send.

Contact forms collect a name, email, message and consent to share them with the page owner for an inquiry response, not marketing enrollment. Inquiries appear in the owner’s private inbox; email notifications are not enabled. To limit spam, forms use expiring signed challenges, replay protection and daily limits. A keyed daily hash of the sender’s IP address is stored rather than the raw address in lead records. Messages older than 90 days are excluded from exports and removed when the owner opens the inbox or the page receives another message. A scheduled retention sweep runs hourly in production. Cleanup can be delayed if the job fails; this is not an exact deletion-time guarantee. Page owners can delete inquiries; account deletion removes published pages and leads.

If email alerts are activated, verified page owners can opt in from Settings. Resend receives the owner's email address and a generic inbox link, not the inquiry's name, address or message. ISOHub stores the alert preference and delivery-attempt metadata, which are included in the owner's account export. Delivery records are removed with their inquiry or account. Provider acceptance is not proof of inbox delivery.

Optional tool activity

Activity tracking is off by default. If you enable it in Settings, we store the tool you visited, the day, a capped view count and last-seen time to show recent tools and aggregate usage. We do not include your tool inputs in these events. Turning it off removes existing activity. Activity and reply notifications have a 90-day cleanup policy, subject to the configured retention job.

Proposal writing assistance

When available, optional AI editing sends only the benefit names and descriptions you approve to OpenAI. It does not send the proposal's pricing, merchant identity or contract terms. Remove sensitive data from descriptions first. Suggestions require your review and are not automatically applied or saved. Provider retention conditions described below also apply to this operation.

Service providers

The architecture uses Vercel for hosting, managed PostgreSQL for accounts and records, Better Auth for authentication, and Resend for sign-in email delivery. Google sign-in is optional. Provider availability depends on the environment. AI infrastructure uses OpenAI and is disabled by default until the operator configures it.

AI chat processing

When enabled, sending a question transmits your prompt, the last eight messages, practice difficulty and relevant reference excerpts to the configured OpenAI model. Conversations are stored in your private workspace only when you choose Save. You can delete saved conversations or export them through Settings. The operator must verify applicable provider retention and publish the final processing policy before public activation. Disabling provider response storage is not a promise of zero retention. The foundation records token and estimated cost metadata, not prompt text, in its AI usage ledger.

Community and industry reading

Community participation uses an explicitly published display name and bio. Discussions and replies remain visible only to their author and administrators until approved. Published contributions and helpful-vote totals are public. Saved discussions, reports and reply notifications are private to the member or authorized moderators as appropriate. Contributions are not sent to AI. Account export includes your community records; account deletion removes your profile and contributions. Moderation events retain no content in audit logs.

Industry Pulse reads headlines, links and publication dates from fixed official RSS sources. Browsing the feed does not send articles to AI. Optional account bookmarks retain the selected headline metadata. The weekly digest is a local download; no email subscriptions are created. When AI is activated and you explicitly request a brief, ISOHub sends only the selected publisher's RSS title, publication date and available excerpt to OpenAI. It does not fetch the full article for this operation. The brief is an interpretation of that excerpt, not a verified account of the entire article. The AI processing conditions above also apply.

Your controls

Signed-in members can export workspace records from Settings and delete their account. Account deletion removes associated workspace items. Operational audit events are detached from the user on deletion. Hosting and provider backup expiration are separate from live record deletion.

Before public launch

This foundation disclosure is not the final production policy. Operator contact information, exact retention periods, backup expiry, subprocessors, applicable rights and the document-processing design must be completed before public account enrollment or merchant document collection.