Privacy for the operating record.

1. Scope and roles

This FrankieFam Software Suite Privacy Policy describes how Albany Automations and the applicable Jamie Lynn Services operation (together, “Provider,” “we,” or “us”) may handle information in connection with FrankieFam software, related services, the FrankieFam website surface, and customer communications. It is cumulative: the general provisions apply across the Suite, and the current product-specific provisions appear below for the products identified in this document.

Provider’s direct relationship is generally with the Customer that asks for, registers, configures, or uses a service. A Customer may deploy Frankie or another Product to its own End Users. In that situation, the Customer controls its own business relationship, configuration, notices, disclosures, permissions, and privacy representations to those End Users. This policy does not replace the Customer’s own privacy notice or make Provider the operator of the Customer’s entire End User relationship.

2. Information provided directly

People may provide contact or inquiry information such as a name, work email, organization, message, requested service, product interest, or information needed to respond to a request. Customers may provide account contacts, license or registration details, business configuration, instructions, Customer Materials, support questions, and information needed to establish or administer a service relationship.

People should not send sensitive information through a general website form or ordinary email unless the applicable instructions expressly provide an approved method. The actual fields and required information depend on the form, product, customer agreement, and service being used.

3. Account, contact, and business configuration information

For a Customer relationship, Provider may handle information needed to identify the Customer and authorized contacts, administer an account or license, communicate about the service, record configuration choices, provide support, and follow authorized instructions. Business configuration information may include the content, settings, workflow instructions, or other Customer Materials the Customer chooses to provide for a particular deployment.

Provider does not treat a product description as proof that every possible field or integration is active for every Customer. The applicable Customer agreement, product configuration, and actual deployment determine what information is processed.

4. Technical and service information

Depending on the deployment and supporting systems, Provider or a service provider may receive limited technical or service information necessary to operate, secure, troubleshoot, maintain, and administer a product. This may include requests, error information, service status, account or license state, and basic technical context generated by the particular environment.

The exact technical fields, logs, storage locations, access controls, and retention periods are deployment-specific. Provider will not describe a category as collected merely because it is common in other software; the applicable architecture and service configuration control.

5. Information processed through Customer-configured software

When a Customer configures a Product for its business, the software may process information the Customer directs it to use or information an End User submits through the Customer’s deployment. The purpose is to provide the configured interaction or workflow, maintain the service, support the Customer, protect the system, and carry out authorized instructions.

The Customer is responsible for determining what information to place into the deployment, whether the deployment is appropriate for its business, what notices and permissions are required, and how the Customer responds to End User requests. The Customer must not configure or use the software in a way that conflicts with the Customer’s own representations, required disclosures, or applicable agreement.

6. How information is used

• To provide, configure, maintain, secure, troubleshoot, and support the requested software or service.
• To administer accounts, licenses, registrations, service communications, and the business relationship.
• To follow Customer instructions and process Customer Materials for the configured purpose.
• To respond to inquiries, support requests, and communications.
• To investigate misuse, protect systems and people, enforce the applicable agreement, and address security or operational events.
• To comply with a legal obligation, establish or defend a claim, or complete a permitted business transaction.

Provider should not use Customer Materials for an unrelated purpose without authorization from the Customer, a clear product term, or another lawful basis identified during attorney review.

7. Third-party providers and connected services

Software functionality may rely on hosting, infrastructure, communications, integrations, devices, or other services provided by third parties. Where a third-party service is used, that provider’s own privacy practices, terms, technical requirements, and retention practices may also apply. Albany Automations does not rewrite or replace third-party agreements.

A Customer may need to maintain its own third-party account or authorization. Third-party availability, security, functionality, and changes may be outside Provider’s control. The Customer is responsible for reviewing and approving connected services for its deployment and for providing any required End User notice about those services.

8. Security and administration

Provider should use reasonable administrative, technical, and organizational measures appropriate to the configured service to protect information against unauthorized access, loss, misuse, or alteration. No website, software, transmission method, or storage system can promise absolute security. Customers are responsible for authorized users, credentials, device security, configuration choices, secure instructions, and promptly reporting suspected account or deployment compromise.

9. Retention and deletion

Information should be retained only as long as reasonably necessary for the stated service purpose, the Customer relationship, the applicable agreement, security and administration, legitimate technical processes, dispute resolution, or a legal obligation. Actual retention periods depend on the product, configuration, storage system, Customer instructions, and applicable law.

When a Customer account relationship terminates, Customer-specific files and online-accessible Customer Material are scheduled for removal from ordinary online access within 30 days after termination. This is not a promise of instantaneous deletion from every cache, backup, security record, legal or accounting record, or other necessary system process. Material remaining in those systems should remain subject to appropriate access controls and should be removed or overwritten according to the applicable retention and system-rotation process.

10. Customer and End User privacy responsibility

The Customer is responsible for its own privacy notice, disclosures, permissions, consent practices, end-user communications, business representations, configuration decisions, and responses to requests from the Customer’s End Users. The Customer must determine whether its use of a Product requires additional contractual, regulatory, sector-specific, or technical controls.

Where Provider receives information on a Customer’s instructions or through a Customer deployment, the Customer should direct privacy requests, corrections, deletions, and questions from its End Users through the Customer’s own published process unless the applicable agreement says otherwise. Provider will follow the applicable Customer agreement and authorized instructions for the configured service.

11. Communications and privacy requests

Provider may send service, account, security, support, operational, or relationship communications needed for a requested or contracted service. Marketing communications, if used, should be handled through the applicable consent and preference process. Privacy questions about this Suite policy may be sent through the Contact page or the address below. Provider may ask for reasonable information to verify the request and identify the relevant Customer relationship or deployment.

12. Policy updates

Provider may update this cumulative policy as the Suite, Products, deployments, service relationships, or applicable requirements change. A revised version should identify its effective date and be posted or provided through an appropriate notice. Product-specific privacy provisions may be added below the general provisions as new products actually exist. An update does not by itself create a promise that a future product or data practice exists today.

13. Contact and reference

Questions about this policy or a FrankieFam privacy practice should be directed through the Contact page or by written correspondence:

The FrankieFam Software Suite Terms and Conditions contain the cumulative commercial terms, including the customer responsibility boundary and the attorney-review arbitration provision.

14. Product-Specific Privacy — Free Frankie

14.1 What Free Frankie is

Free Frankie is a free website chatbot product. It uses the information and configuration provided for the deployment, together with the available response logic and any connected services used by that deployment, to provide the configured chatbot interaction.

14.2 Conversation and input information

Free Frankie may process conversation and input information that is necessary to provide the configured chatbot interaction. The exact information path may vary based on Customer configuration and connected services. Not every Free Frankie deployment necessarily stores the same information or uses the same connected service. This policy does not promise storage, collection, profiling, or retention of categories that the particular architecture does not support.

14.3 Customer deployment boundary

Albany Automations’ direct relationship is with the Customer that registers or deploys Free Frankie. When the Customer places Free Frankie on its website or another customer-facing surface, the Customer is responsible for telling its End Users what information the Customer’s deployment requests, receives, presents, or sends to a connected service, and for obtaining any notices, permissions, or consents that the Customer’s business requires.

14.4 Free license and attribution

Free Frankie is a $0 licensed product. The free license does not transfer Albany Automations’ intellectual property ownership. The free version may contain Albany Automations or Free Frankie attribution and acquisition messaging. Customer may not assume that attribution can be removed unless applicable product terms expressly allow it. Properly licensed use may continue after the Customer stops using other Albany Automations services, subject to the Terms, registration requirements, and the applicable deployment.

15. Product-Specific Privacy — Form Frankie

15.1 Conversational form submissions

Form Frankie is a conversational form product. A person may intentionally submit information through a particular Form Frankie conversation. Depending on the form and its configuration, that information may include a name, email address, telephone number, business information, address or location information, website, service or request information, custom form responses, or other information deliberately requested by that form. This list describes possible categories only; it does not mean that every Form Frankie collects every category.

Form Frankie is configurable. A Customer-created form may request different information based on the Customer's legitimate business purpose, the applicable deployment, and the fields the Customer enables. The existence of an available field is not proof that the field is active or collected in every deployment.

15.2 Albany Automations use and Customer deployment

When Albany Automations uses Form Frankie for its own onboarding, intake, support, account setup, or other business purpose, information intentionally submitted to Albany Automations is handled under this Privacy Policy and the applicable Terms.

When a Customer deploys Form Frankie on its own website or other customer-facing surface, the Customer decides what information it asks its End Users to provide, why it requests that information, how it uses the information, and what disclosures, permissions, notices, and other obligations apply to the Customer's business. Albany Automations remains responsible for processing that Albany Automations actually performs as the software or service provider under the applicable agreement and deployment. This policy does not make Provider the operator of the Customer's entire End User relationship.

15.3 Submission acknowledgment

A Form Frankie configuration intended to collect information for submission must present an unchecked, required affirmative acknowledgment immediately before submission, with nearby links to the applicable Privacy Policy and Terms and Conditions. The acknowledgment may state substantially that the person understands they are voluntarily providing the information and consents to its collection and handling as described in the applicable Privacy Policy. Submission must not complete until the acknowledgment is affirmatively selected. The exact disclosure and policy links depend on whether the form is operated by Albany Automations or by a Customer and must not falsely identify Provider as the business requesting every submission.

Where information is intentionally submitted into or through an independent third-party service, that service's own terms and privacy practices may also apply to its handling.

16. Product-Specific Privacy — FAQ Frankie

16.1 Customer-provided business knowledge

FAQ Frankie is a business-knowledge authoring product. A Customer intentionally provides information so it can become part of the Customer's Frankie configuration or knowledge package. Examples may include business hours, services, pricing, policies, frequently asked questions, locations, contact information, business facts, links, approved answers, and other Customer-provided business knowledge.

16.2 Configuration, account association, and use

Information intentionally provided through FAQ Frankie may be stored as part of the Customer's Frankie configuration or knowledge package, associated with the Customer's account or Portal, and used by the Customer's applicable Frankie products to provide responses or information on the Customer's behalf. The actual storage location, technical format, access path, and retention depend on the deployment and applicable service configuration; this policy does not promise a specific storage technology or filename.

FAQ Frankie does not silently harvest business information under this product contract. The Customer deliberately supplies the information for the configured product purpose. The Customer is responsible for the accuracy, appropriateness, currency, and authority to provide the information it teaches or configures into Frankie.

17. Product-Specific Privacy — Contact Frankie

17.1 Conversational contact intake

Contact Frankie replaces or supplements a conventional Contact Us form with conversational contact intake. Depending on the Customer's configuration, a visitor may intentionally submit a name, email address, telephone number, preferred contact method, message or reason for contact, callback request, urgency or on-call request, or other Customer-configured contact responses. This list describes possible categories only; it does not mean that every Contact Frankie collects every field.

The Customer determines the Contact Frankie configuration and the business purpose for which contact information is requested. The visitor intentionally supplies the information; FrankieFam software processes or routes the submission as implemented; and the FrankieFam Customer receives or uses the contact request for the Customer's own business purpose.

17.2 Routing and destination boundary

Contact Frankie may route a completed contact request to a destination configured by the FrankieFam Customer. The destination may vary by Contact Frankie instance. The actual transmission, delivery, storage, and access path depend on the deployment and connected services. A public embed may identify the instance or a destination reference without exposing the private destination email in the public page markup. Albany Automations does not claim to own, control, or automatically receive private account information held by an independent third-party provider.

When a Customer receives a Contact Frankie submission, the Customer is responsible for its use of that information, its relationship with the visitor, and the notices, permissions, privacy representations, and business practices its use requires. Provider remains responsible for processing that Albany Automations actually performs under the applicable agreement and deployment.

17.3 Submission acknowledgment

A Contact Frankie configuration intended to collect and submit visitor information must use the same affirmative acknowledgment architecture described for Form Frankie: an unchecked required acknowledgment immediately before submission, nearby links to the applicable Privacy Policy and Terms and Conditions, and no completed submission until the person affirmatively selects the acknowledgment. The wording and linked policy may vary according to the business operating the particular Contact Frankie instance.

18. Data-minimization principle

Across these products, Provider's intended processing boundary is information a person intentionally submits, information necessary to provide a service or product the person or Customer requested, or information necessary to administer the applicable Customer or account relationship. FrankieFam does not automatically collect unrelated information merely because another service, account, browser, device, or integration possesses it. The actual deployment and connected services determine the information path.