Privacy Policy

Last updated: November 5, 2026. This is ARIENESS's pre-launch privacy notice. We may update it as additional features and operational details are finalized. Changes to material data practices will be reflected here before their introduction.

Who this notice covers

ARIENESS Church Growth AI (“ARIENESS”) provides church-focused software and informational resources through arieness.com and app.arieness.com. This notice explains the information processed through the public website and application. It does not replace a church's own privacy notices about its members, visitors, or contacts.

Information involved in the Services

Account and workspace information: names, email addresses, authentication and membership information, church or organization names, church website details, team roles, and workspace settings supplied during account creation and onboarding.

Audit and reporting information: website addresses, publicly accessible website information examined in a requested audit, website-health results, SEO findings, generated recommendations, report dates, and saved workspace reports.

Connected services: where an authorized user connects an available integration, ARIENESS may access permitted account identifiers, property or profile selections, metrics, reports, and relevant connection information from providers such as Google Analytics, Search Console, Google Business Profile, YouTube, Meta, or Twilio. Access depends on the provider authorization and enabled features. Technical connection credentials may be maintained to support continued authorized access.

Technical and communications data: information needed to manage sessions, protect accounts, troubleshoot failures, and respond to inquiries, which may include IP addresses, device and browser information, timestamps, and messages sent to support.

Billing information: where paid features become available, payment services may handle checkout and provide subscription or payment-status information. Payment terms and available plans are displayed separately at the point of purchase.

How information is used

Information is used to authenticate accounts, manage church workspaces and permissions, carry out requested website audits, save and display reports, operate authorized integrations, provide content and AI-assisted features, maintain service security, diagnose problems, support users, and administer any available subscriptions.

Church workspace access

Content and reports in a church workspace may be accessible to members with appropriate workspace permissions. Owners and administrators can manage team access and available integrations. Church administrators should invite only authorized users and evaluate what personal information they provide or connect to the Services.

Visitor, content and safety information

Authorized church users may enter visitor contact details, notes, follow-up information, drafts, AI messages, images and video information. This material may reveal religious beliefs or other sensitive information. Submit only information you are authorized to use. A content report may include the reported text, your explanation, account/workspace identifiers and handling records for restricted safety review. A report is not a request to delete the underlying content.

AI-assisted functionality

Some tools may process user inputs and relevant website or reporting information to generate suggestions, summaries, or other outputs. AI-generated results can be incomplete or inaccurate and should be reviewed before use or publication. OpenAI receives relevant prompts, selected church or website context and, depending on the tool, images or video information. Where Klap video processing is available, Klap receives the submitted source video or URL and related processing information. Klap has described improvement and human-review purposes and downstream AI processing; ARIENESS has not verified a self-service opt-out or a complete per-user deletion procedure. Do not assume provider processing is limited to generating an output. In mobile builds that request permission per operation, Cancel before submission sends no new request; cancelling a dialog or leaving a screen does not cancel a job already started.

Third-party connections and service providers

When a user enables an integration, the connected provider's own privacy policy and terms may also apply. ARIENESS uses technical infrastructure and service providers necessary to deliver and secure its website and application. Information may be disclosed to those providers as necessary to operate requested features or as required by law. ARIENESS does not use an integration to obtain access beyond the permissions provided by the authorized connection.

Service providers include Supabase for authentication, database and file storage; Vercel for application hosting and requests; Stripe for payments and subscription management; Resend for enabled email functions; and Cloudflare R2 for recovery records. Google/YouTube, Meta and Twilio receive information relevant to enabled, authorized integrations. A provider appearing here does not mean every feature is available in every environment.

Cookies and security

Website and application technologies may use cookies or similar mechanisms for essential session, authentication, preference, and security functions. Additional analytics or marketing technologies, if enabled, will be described and controlled in accordance with applicable requirements. Reasonable technical and administrative measures are used to protect the Services, but no online system can promise absolute security.

Retention and requests

Account, workspace, audit, integration, and operational records may be maintained while needed to deliver Services, preserve security, resolve problems, or meet legal obligations. Retention varies by category and feature. Saved Shorts history is offered for up to 30 days and may be removed earlier when shared storage capacity is needed; that display window is not a promise that provider, operational or recovery copies are erased. Account/workspace data, security and billing records, reports and recovery copies have separate purposes and retention needs. Exact provider retention and full deletion handling remain under verification; no universal deletion deadline or zero-provider-retention promise is made. Clearing an app cache, removing a local history item or losing access to a URL does not establish erasure from providers or backups. Automated account deletion remains disabled while safeguards are verified. To request access, correction, or deletion of account-related information, contact ARIENESS using its official website or available in-app support channels. Requests involving data controlled by a church may need to be addressed by that church's authorized administrators. Applicable legal rights depend on location and circumstances.

Children and sensitive information

The software is intended for authorized organizational users rather than use directly by children. Churches should not enter sensitive personal information about children, congregants, or visitors unless they have an appropriate legal basis and a specific need to do so.

Changes and contact

We may revise this notice as the platform evolves, including clarifying service providers, applicable retention schedules, and privacy controls before final launch. Updates will appear on this page with a revised date. For privacy inquiries, email arienessweb@gmail.com, visit Contact ARIENESS or use the support channel provided within the application.