How OwnFramework's workflow-review and communication pages work.

1. What this page covers

This Help page explains the OwnFramework workflow-review and communication process. It is not a staffed help desk, a live chat service, a ticketing platform, an emergency service, or a guaranteed-response support center. OwnFramework is a small business; replies are sent by a human, when there is a human available to send them.

This page is part of the OwnFramework public website and is read together with the Privacy Notice and the Terms of Use.

2. The workflow-review process

The workflow-review form lets a business describe one bounded workflow it would like to understand better. Typical examples include a repetitive process, a manual handoff between people or tools, an operational bottleneck, a reporting problem, a review or approval flow, or another explicit business workflow.

Submitting the form creates material for internal human review. It does not, by itself, do any of the following:

• connect OwnFramework to your software or systems;
• begin implementation, development, or design work;
• change a customer system, account, or environment;
• create records in a CRM, marketing tool, or sales pipeline;
• send customer messages, marketing emails, or notifications;
• approve a project, scope, timeline, or price;
• charge a payment method, accept payment, or create a purchase;
• authorize access to any account, system, or file;
• deploy automation, bot, or agent.

3. Information you may submit

The workflow-review form is intentionally data-light. The categories below describe what is appropriate to share.

• A business email address that you check.
• The name of your organization (or a working name for it).
• A plain-language description of the workflow you want reviewed.
• Approximate frequency or volume (for example, "around 30 per week").
• The tools involved at a general level (for example, "a spreadsheet and an inbox").
• The outcome you would like to see.
• Known limitations, review requirements, or things that must not be automated.

4. Information you must never submit

The public form is not a secure document exchange. Do not submit, paste, or attach any of the following through the workflow-review form or by email to the addresses shown on this website:

• passwords, passphrases, or password reset links;
• API keys, OAuth tokens, webhook secrets, or any other access tokens;
• authentication codes, one-time codes, or second-factor secrets;
• private encryption keys, signing keys, or certificate material;
• payment-card information, bank account numbers, or banking credentials;
• Social Security numbers, government identification numbers, or tax identifiers;
• health records, medical histories, or insurance identifiers;
• full customer databases, customer exports, or contact lists in bulk;
• confidential customer records, vendor records, or employee records;
• regulated personal data such as children's information or special-category data;
• production secrets, infrastructure secrets, or source code you are not authorized to share;
• sensitive legal records, litigation material, or attorney-client material;
• any information you are not authorized to share.

OwnFramework does not expect sanitized copies of sensitive originals. If a workflow you want reviewed depends on sensitive records, describe the workflow in plain language without pasting the records themselves. Do not paste records "just to be helpful".

5. Human review

A person reviews every workflow-review submission before any implementation decision is made. OwnFramework may, in the reviewer's judgement, do any of the following:

• ask for clarification or a follow-up description;
• determine that the request is outside OwnFramework's scope or capacity;
• recommend a smaller, focused review rather than a full project;
• propose a controlled next step with clear boundaries;
• decline work that cannot be handled safely or within scope.

OwnFramework does not promise that every submission receives a reply, and does not promise a fixed review time or a guaranteed response window. There is no support SLA on this website.

6. After submission

A successful submission means the request was received for review. It does not mean any of the following:

• the project was approved;
• work has started or has been scheduled;
• a contract, engagement letter, or scope document exists;
• a price was accepted or a quote was issued;
• access was granted to any system;
• an automated system was activated.

A subsequent conversation, discovery call, or written exchange is the only place where any of those things can be agreed.

7. Preferences and unsubscribe pages

The OwnFramework Privacy Notice describes how preferences and unsubscribe links work in plain language. The summary below is what those pages do, and what they do not.

• Preferences links show limited communication-related information about how OwnFramework may reach a visitor.
• Unsubscribe confirmation pages are designed to be safe to load. A GET request on an unsubscribe link shows the confirmation page; nothing changes on its own.
• Unsubscribing requires an intentional confirmation action. Going back, ignoring the page, or leaving it does not change anything.
• Repeated confirmation is safe. Confirming a preference or unsubscribing more than once for the same address ends in the same state.
• Personal preferences and unsubscribe links should not be shared. They are scoped to a single address and may contain a long, unguessable token.

OwnFramework does not publish the internal token format, storage paths, ledger names, or identifiers behind those pages. They are operational details, not visitor-facing behavior.

8. Contact

For general questions about the OwnFramework website, the workflow-review process, privacy, or communication preferences, write to [email protected].

OwnFramework does not promise a guaranteed answer or a fixed response time for messages sent to this address. There is no support SLA on this website.

9. What OwnFramework does not do automatically

To be unambiguous, and without limiting anything above, the public website does not, on its own:

• connect to your software, accounts, or systems;
• install agents, scripts, or browser extensions on your devices;
• send customer messages, marketing emails, or notifications on your behalf;
• create, modify, or delete records in your tools;
• approve projects, scope, or pricing;
• charge payment methods, accept payment, or create purchases;
• deploy automation or activate bots;
• open a support ticket, a chat, or a live-channel session.

This list is not exhaustive. It is a plain-language reminder of the boundaries the OwnFramework public website observes.