Privacy Policy

AridLogic, a division of AliJede Solutions LLC (“we,” “us,” or “our”) respects your privacy. This Privacy Policy explains what information we collect through the AridLogic website at aridlogic.com, our invite-only client portal at portal.aridlogic.com, and related services, how we use it, and the choices you have. AliJede Solutions LLC is the legal entity responsible for these services. For questions, contact us at inquire@aridlogic.com.

This policy is provided for transparency and operational consistency. It is not a substitute for legal advice. If you need guidance for your specific situation, consult a qualified attorney.

Scope

This policy applies to information collected through our public marketing website (including contact and audit request forms, gated resource downloads, Stripe Checkout or invoice payments, nurture email sequences, and standard web technologies described below) and through our authenticated client portal at portal.aridlogic.com for invited clients. Authorized AridLogicstaff use separate internal tools to operate the portal on your behalf; those tools are not open to the public. It also applies to our Free Missed-Call Rescue Kit and related paid missed-call services (the "Missed-Call Service"), where we handle call and text data for home-service businesses that use the service. For that data, the business is generally in control of its customer relationship and we act on its behalf. See "SMS and call data (Missed-Call Service)" below.

The client portal is a convenience layer for project collaboration — deliverable reviews, document sharing, billing visibility, in-portal messaging, optional Google Analytics and Search Console connections for retainer reporting, and automated AI summaries when enabled for your project. Paid client engagements, deliverables, payment terms, and intellectual property are governed by your statement of work or other signed agreement with us, not solely by this policy or portal features.

Separate agreements govern paid client engagements and are provided at contract time.

Information we collect

Information you provide

We collect information you voluntarily submit, such as:

• Contact requests: name, email address, company name (optional), package interest, budget range (optional), and project details.
• Website audit requests: name, email address, website URL, and goals or context for the audit.
• Resource downloads: email address and any optional name or company fields you provide when a library resource requires an email before download, plus the resource requested.
• Email and calendar correspondence: content of messages you send to us and related metadata (for example, your email address and timestamps).
• Payments: when you pay through Stripe Checkout or a Stripe invoice link, payment and billing details are processed by Stripe. We receive limited transaction metadata (for example, name, email, amount paid, and payment status) — not full card numbers.

Forms on this site are designed for business inquiries. Please do not submit sensitive categories of information (such as government IDs, health data, or payment card numbers) unless we explicitly request them through a secure channel as part of an engagement.

Client portal (authenticated users)

If you are invited to the client portal, we collect and process additional information to operate your account and project workspace, including:

• Account and authentication: email address, display name, profile information you provide, authentication events, and — if you choose Google sign-in — a Google account identifier supplied by Google OAuth. Access is invite-only; we do not offer open public registration on the portal.
• Project and deliverable data: project names, phases, milestone status, deliverable titles and versions, approval or revision requests, comments you post, and @mentions that trigger email notifications to other participants on the project.
• Files and document vault: deliverable files we publish for your review, and files you upload to the document vault (for example, PDF, PNG, JPG, SVG, or ZIP within published size limits). Files are stored in Supabase Storage with access controls tied to your project.
• AI assistant messages: chat messages you send in the portal AI assistant, stored per project, together with metadata needed to operate the feature (for example, timestamps and project association).
• Billing visibility: invoice metadata displayed in the portal (for example, invoice number, amount due, and status). When you manage payment methods or complete certain billing actions, you may be redirected to Stripe Customer Portal, where Stripe collects payment information under its own privacy policy.
• Client analytics connections: if you connect Google Analytics 4 or Google Search Console, we store encrypted OAuth credentials, connection identifiers (for example, Google account email when provided, GA4 property ID, Search Console site URL), and aggregate performance metrics retrieved for retainer reporting. See Client analytics connections.

Do not store production passwords, API secrets, or other credentials in the portal document vault unless we explicitly agree to a secure process as part of your engagement. We recommend sharing credentials through a dedicated password manager when needed.

Missed-Call Service (businesses and their callers)

If a business uses our Missed-Call Service, we collect and process:

• From the business:business name, address, website, phone numbers, the owner's or staff's names, email addresses, and mobile numbers for alerts, carrier and setup details, and information needed for US text-messaging registration (such as legal name and tax ID).
• About people who call that business ("callers"): the caller's phone number; the time, date, and length of the call; whether it was missed or answered; whether the number can receive texts (a line-type check); text messages sent to and received from the caller, and their content; voicemail audio and, where available, an automated transcript; and opt-out, opt-in, and help requests (for example, STOP or HELP) with their timestamps.

We do not ask callers for sensitive information by text. Callers should not send card numbers, Social Security numbers, or passwords by text.

Information collected automatically

When you visit our site, we and our service providers may collect certain technical information automatically, such as IP address, device type, browser type, general location derived from IP, pages viewed, referring URLs, and dates and times of access. We use PostHog for product analytics (for example, page views and form submission events in aggregate) and may use Vercel Analytics for performance metrics. We may use cookies and similar technologies as described in our Cookie Policy.

When you use the client portal, we similarly collect technical and usage information (for example, authentication events, pages viewed, deliverable interactions, and error diagnostics) through PostHog and Sentry to secure, operate, and improve the portal experience.

Staff access, impersonation, and audit logging

To operate, secure, and support the client portal, authorized AridLogic staff may access client accounts and project data through internal administrative tools. Access is limited to staff who need it for their role and is subject to multi-factor authentication and session controls.

View-as-client (impersonation) for support

In limited circumstances — for example, to reproduce a display issue or walk through portal state with you on a call — a senior authorized staff member may use a “view as client” feature that opens the portal as your account would appear. When this happens:

• A persistent banner is shown on every page indicating that staff are viewing the portal on your behalf.
• The session is short-lived (generally no more than 30 minutes) and ends when the staff member exits or the session expires.
• Staff in an impersonated session cannot submit deliverable approvals or revision decisions on your behalf, or complete invoice payments on your behalf. Those actions remain yours to perform in the portal.
• We use impersonation for support and troubleshooting — not to bypass your decisions or act without your knowledge.

Immutable audit log

We maintain an append-only audit log of significant staff actions in our internal systems, including when impersonation starts and stops. Typical logged fields include the staff actor, action type, affected resource, timestamp, and technical metadata such as IP address. Examples of logged actions include client record changes, deliverable publishing, impersonation sessions, invoice automation steps initiated by staff, and security-relevant events such as multi-factor authentication changes.

Audit log entries are designed to be immutable (they are not edited or deleted through normal application use) so we can investigate issues, meet contractual and legal obligations, and maintain accountability. Client portal users do not have access to the staff audit log; it is visible only to authorized staff through internal security tools.

How we use information

We use personal information to:

• Respond to inquiries, audit requests, and business development messages.
• Store form submissions and related operational records in our database (Supabase).
• Send transactional email such as confirmations and follow-ups related to your request (Resend).
• Process payments, issue receipts, and manage billing when you use Stripe Checkout or pay an invoice (Stripe).
• Operate, secure, maintain, and improve our website and internal processes.
• Understand aggregate usage trends through analytics (PostHog and, where enabled, Vercel Analytics).
• Comply with law, enforce our Terms of Service, and protect rights, safety, and property.
• Send operational messages related to your request (for example, confirming receipt or following up on scope). We do not sell your personal information.
• Operate the client portal: authenticate invited users, display project status, publish and review deliverables, facilitate comments and notifications, store project files, provide the in-portal AI assistant, show billing information, generate automated AI summaries when enabled, and support retainer reporting (including optional Google Analytics / Search Console connections or manually uploaded reports).
• Send portal-related email (for example, invites, deliverable notifications, @mention alerts, and invoice reminders) through our email provider.
• Deliver gated resource downloads and related educational nurture sequences when you request a download (Loops), and send download confirmations and other transactional messages (Resend).
• Record staff administrative actions and impersonation sessions in our immutable audit log for security, support, and accountability (as described above).
• Operate the Missed-Call Service for the business a caller contacted: detect missed calls, send that business's one-time text-back to the caller, play voicemail prompts, deliver voicemails and transcripts, forward caller replies, alert the business by email or text, and prepare that business's call reports.
• Register and maintain US text-messaging registrations with carriers and our messaging providers: A2P 10DLC brands and campaigns for businesses' caller text-backs, and toll-free verification for our own alert number.
• Honor opt-outs and keep records of consent, opt-out, and help requests so we don't text people who asked us to stop.
• Create aggregate, de-identified counts (for example, total missed calls across all businesses in a pilot) that do not identify any business or caller.

Client portal AI assistant

The portal includes an AI assistant powered by Anthropic. When you use it, your messages are stored per project so you can continue conversations and so we can support quality and abuse prevention.

The assistant answers using approved project context only — for example, statement-of-work summaries, current phase information, and staff-approved snippets we add to the project context pack. Client-uploaded vault files are not included in AI context unless our staff explicitly approves them for that purpose.

AridLogic AI is a project-support tool. It is not legal, financial, tax, or professional advice. Confirm important decisions with your project lead. A similar disclaimer is shown in the portal chat interface.

We do not use your portal content to train our own models. When we send prompts to Anthropic’s API, processing is governed by our agreement with Anthropic and their privacy terms. We do not authorize use of your client data for model training without your explicit consent.

Client analytics connections

If you connect Google Analytics 4 (GA4) or Google Search Console through the AridLogic client portal, you authorize AridLogic (AliJede Solutions LLC) to access those Google services on your behalf for your project’s retainer reporting.

What we access

We request read-only access to aggregate performance metrics for properties you select or that are associated with the Google account you connect. Typical metrics include sessions, users, conversions (key events), top pages, Core Web Vitals summaries when available, and Search Console clicks, impressions, CTR, and top queries. We do not request write access to your Google Analytics or Search Console properties, and we do not request Google Ads or Google Drive access for this feature.

What we store

We store OAuth credentials (including refresh tokens) needed to keep the connection active, plus identifiers such as the connected Google account email (when provided by Google), GA4 property ID, and Search Console site URL, and the aggregate metrics we retrieve for reporting. Refresh tokens are encrypted at rest. We do not sell this data. Tokens and pulled metrics are used solely to operate AridLogic reporting for your engagement.

How we use the data

Metrics may appear in portal charts and may be summarized by AI (Anthropic) for portal retainer notes or internal staff reporting related to your project. AI receives aggregated metrics JSON only — not your Google OAuth tokens and not bulk dumps of personal data from Google.

Your choices

You may disconnect at any time in the portal. On disconnect we delete stored OAuth tokens for that connection and stop automated pulls. Historical report summaries already generated in the portal may remain as part of your project records under our retention schedule unless you request deletion consistent with your agreement and applicable law.

If Google access expires or refresh fails, we may notify you (email and/or portal banner) so you can reconnect. Until reconnected, we may continue to use manually uploaded reports your team provides.

Retainer reporting scope and cadence are also defined in your Statement of Work. Manual PDF/CSV upload remains available if you prefer not to connect Google.

Automated AI summaries

In addition to the optional in-portal AI assistant, AridLogic may generate automated summaries using AI models provided by Anthropic:

• Internal staff briefings (for example, weekday operational summaries of overdue work, unpaid invoices, pending approvals, or stale projects). These are for AridLogic staff only and are not client-facing by default.
• Client-facing project health summaries (short bullet summaries shown in the portal for active projects when enabled).
• Retainer performance notes (AI-assisted narratives based on approved metrics and/or staff-uploaded report files, shown in the portal when enabled).

Nature of the output. Summaries are assistive only. They may be incomplete or incorrect. They do not replace human project management, legal advice, or financial advice. For decisions, contact your project lead or reply to inquire@aridlogic.com.

Inputs. Automated jobs use operational data already in AridLogic systems for your engagement (for example, task status, invoice status, approval status, activity signals, curated project context, and aggregate analytics metrics when connected). We do not send Google OAuth tokens to Anthropic. Vault files are included in AI context only when staff have approved them for that purpose (same boundary as portal AI chat).

Controls. Staff may disable AI features per project. Portal AI chat remains subject to monthly per-project budgets. You may ask us to turn off client-facing health or retainer narrative cards for your project.

Processing by Anthropic is governed by our agreement with Anthropic and their privacy terms. We do not use client content to train AridLogic’s own models; use of data by Anthropic is subject to their API terms.

Resource downloads and email

Some library resources (for example, checklists, kits, or calculators) may require an email address before download. When you submit that form:

• We collect the email address and any optional name/company fields you provide, plus the resource requested and technical metadata needed to prevent abuse (for example, Turnstile verification).
• We create or update a lead record in our systems (with a source such as resource-gate).
• We deliver the download (immediate link and/or confirmation email).
• We may enroll you in a short educational email sequence (for example, Day 0 / 3 / 7) related to the resource or your audit interest, sent via our nurture provider (Loops) from our sending identity on mail.aridlogic.com.

Marketing vs transactional. Nurture sequence messages are commercial / educational follow-up. Transactional messages (for example, download confirmation, portal invites, billing, handoff packs) are sent as needed to fulfill your request or engagement.

Your choices. Every nurture message includes an unsubscribe mechanism. You may also email inquire@aridlogic.com to opt out. We stop sequences when you unsubscribe, reply requesting stop, or when your opportunity is marked closed-won or closed-lost in our process.

We do not sell your email address. Physical mailing address appears in commercial email footers as required by applicable US email law (CAN-SPAM).

SMS and call data (Missed-Call Service)

Who is in control.When a business uses our Missed-Call Service, its callers are that business's customers. The business decides how to respond to them. We process caller data on the business's behalf and only to provide the service to that business. Under the California Consumer Privacy Act and similar laws, we act as that business's service provider or processor for caller data.

How texting works. When a call to a participating business is not answered, the caller may receive one text in that business's name, inviting them to reply. Further texts are sent only as part of the conversation the caller continues. We do not send marketing or promotional texts through this service.

Message frequency and costs. Message frequency varies; typically 1-3 messages per missed call. Message and data rates may apply.

Opting out and help. Reply STOPto any message to opt out. You'll get one confirmation and no further texts from that number. Reply HELP for help, or contact the business you called. You can also email inquire@aridlogic.com. Carriers are not liable for delayed or undelivered messages.

Mobile information. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties. The only exception is service providers (sub-processors) who need the information to deliver the messages and run the service for us, such as phone and messaging providers and carriers, and who may not use it for their own purposes; and disclosures required by law. All the categories of sharing described elsewhere in this policy exclude text messaging originator opt-in data and consent.

Voicemail and transcripts. If a caller leaves a voicemail, the recording is sent to the business the caller called, with an automated transcript where available. Transcripts can contain errors.

No selling, no marketing use.We do not sell caller data or use it to market our own services, and we do not combine one business's caller data with another's except to create aggregate, de-identified counts.

Callers' privacy requests. If you called a business that uses our service and want to access or delete your information, please contact that business. You can also email inquire@aridlogic.comwith "Privacy request" in the subject; we will pass it to the business and help it respond.

SMS terms for the kit: SMS Terms.

Google API Services User Data Policy

AridLogic’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In plain terms, for Google Analytics and Search Console data obtained through our portal connection:

• We use the data only to provide or improve user-facing features that are prominent in our app’s interface (retainer reporting and related portal summaries for your project).
• We do not use that Google user data for serving advertisements.
• We do not sell it to third parties.
• We do not use it for determining credit-worthiness or for lending purposes.
• Human access to that data is limited to cases needed to operate or secure the service (for example, troubleshooting a failed sync, with appropriate access controls), or where you provide consent, or where required for security / legal compliance.

You can revoke AridLogic’s access at any time in the portal (Disconnect) and additionally via your Google Account permissions.

Stripe Customer Portal

For certain billing actions in the client portal (for example, updating a payment method), we may redirect you to Stripe Customer Portal. Stripe processes payment card and billing details directly. We receive limited status and metadata needed to reconcile invoices and subscriptions. Stripe’s privacy practices are described in the Stripe Privacy Policy.

Legal bases (EEA, UK, and similar regions)

Where applicable privacy laws require a “legal basis,” we rely on one or more of the following: your consent (for example, submitting a contact or audit form after reading our consent notice, or non-essential cookies where required); performance of steps you request before entering a contract; our legitimate interests in operating and securing our business and website, provided those interests are not overridden by your rights; and compliance with legal obligations.

How we share information

We do not sell your personal information. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes; see "SMS and call data (Missed-Call Service)." We may share information with service providers who process data on our behalf under appropriate safeguards, including:

• Hosting and infrastructure (Vercel) to serve the site and related assets.
• Database and file storage (Supabase) to store form submissions, audit requests, portal accounts, project data, deliverables, document vault files, AI chat messages, and related operational records under access controls and row-level security.
• Email delivery (Resend) to send confirmations, follow-ups, portal invites, deliverable and mention notifications, invoice reminders, resource download confirmations, and other operational messages.
• Nurture email (Loops) to send educational follow-up sequences related to gated resource downloads or audit interest, with unsubscribe controls.
• Payments (Stripe) to process Checkout sessions, invoices, Customer Portal sessions, and related billing events. Stripe’s privacy policy governs payment card data they collect directly.
• AI processing (Anthropic) to generate in-portal assistant responses from approved project context when you use the AI chat feature, and to generate automated staff briefings, client health summaries, and retainer notes when those features are enabled.
• Google Analytics and Search Console APIs when you connect those services in the portal, so we can retrieve aggregate metrics for retainer reporting. Google’s policies apply to data Google processes; our use of Google user data is described in Google API Services User Data Policy.
• Error monitoring (Sentry) to diagnose portal and application errors, including technical metadata about the request that failed.
• Analytics (PostHog, and where enabled, Vercel Analytics) to measure aggregate site and portal usage and performance.
• Authentication (Supabase Auth, and Google when you choose Google sign-in) to verify portal users. Google’s privacy policy applies to information Google processes when you authenticate with your Google account.
• Bot protection (Cloudflare Turnstile, when enabled on forms) to reduce spam and automated abuse.
• Phone and messaging providers (SignalWire, our primary provider, and Twilio as a backup) and wireless carriers, to provide phone numbers, route forwarded calls, check whether a number can receive texts, send and receive texts, record voicemails, and support text-messaging registration and toll-free verification.
• Automation and hosting(n8n, which we run ourselves on Railway's hosting) to run the missed-call workflow.
• Transcription (SignalWire built-in recording transcription, or Twilio built-in transcription if we fall back to Twilio) to create voicemail transcripts.
• Email delivery for the Missed-Call Service (Resend) to send voicemail emails, alerts, and reports to the business.
• Data storage and logs for the Missed-Call Service (Railway, managed Postgres holding n8n workflow and run data). Voicemail audio stays with SignalWire (or Twilio).
• Mid-trial and monthly report prep (n8n on Railway, sent by email through Resend). The tracker sheet holds shop-level counts only and never caller phone numbers.
• The business the caller called.Caller data is shared with the business that received the call, because it is that business's customer relationship.

We may also disclose information if required by law, legal process, or government request, or to protect the rights, privacy, safety, or property of AliJede Solutions LLC, our users, or the public.

Retention

We retain personal information only as long as reasonably necessary for the purposes described in this policy, unless a longer period is required or permitted by law. The periods below are our general guidelines and may vary based on your agreement with us, legal holds, disputes, or backup cycles. When data is no longer needed, we take reasonable steps to delete or de-identify it.

• Marketing inquiries and audit requests (no paid engagement): typically up to 24 months from your last interaction, so we can respond to follow-ups and measure interest.
• Client portal data (account profile, project and deliverable records, comments, document vault files, and AI assistant messages): for the life of your engagement, then generally up to 36 months after the engagement ends or your last portal activity — whichever is later — unless your statement of work or law requires longer retention.
• Client analytics OAuth tokens: retained while the connection is active; deleted on disconnect or when the engagement ends and tokens are purged per our operations runbook.
• Pulled aggregate metrics (GA4 / Search Console): retained for the life of the project reporting need (aligned with project / engagement retention), then deleted or anonymized per the general portal retention schedule.
• AI briefing / health / narrative rows: retained per operational need (briefings typically ≤ 90 days unless needed longer for audit); client-visible summaries follow project record retention.
• Resource-gate leads and nurture enrollment: retained while sequences are active and thereafter aligned with marketing inquiry retention (typically up to 24 months from last interaction), or until you unsubscribe / request deletion, subject to legal holds.
• Billing and payment records (invoice metadata, transaction references, and related correspondence): generally up to 7 years for tax, accounting, and audit purposes.
• Staff audit log (including impersonation start/stop and administrative actions): generally up to 36 months, or longer if required for an investigation, legal obligation, or active dispute.
• Technical logs and backups (error diagnostics, security logs, database backups): retained on rolling schedules appropriate to the service; deleted copies may persist in backups for a limited period before rotation.
• Missed-Call Service caller data (call records, text content, voicemail audio and transcripts): kept while the business uses the service, then deleted within 30 days after the service ends, unless the business moves to a paid service or asks for an export first.
• Opt-out and consent records (phone number, shop, event type, timestamp and message ID; never message bodies): kept for 5 years from the last consent or opt-out event, so we can keep honoring opt-outs and show how texting was handled.
• Business account and registration detailsfor the Missed-Call Service: aligned with "Marketing inquiries and audit requests" (no paid engagement) or "Client portal data" (paid engagement), as applicable.
• Aggregate, de-identified counts: may be kept indefinitely because they do not identify anyone.

You may request deletion of personal information where applicable, subject to the exceptions in the “Your privacy rights” section below, any active statement of work, and records we must keep for legal, accounting, or security reasons (including audit log entries tied to an investigation).

A summary of this retention schedule is also displayed in our internal Security center for staff reference. Automated deletion jobs for every category are not required for routine operations at our current scale; we review retention when engagements end or when you submit a privacy request.

Security

We use reasonable administrative, technical, and organizational measures designed to protect personal information, including access controls on the client portal, multi-factor authentication for staff, row-level security in our database, and the immutable audit log described above. No method of transmission over the Internet or electronic storage is completely secure, and we cannot guarantee absolute security.

Your privacy rights and choices

Depending on where you live, you may have rights to access, correct, delete, or restrict certain processing of your personal information, to receive a portable copy, or to object to certain processing. You may also have the right to lodge a complaint with a supervisory authority. To exercise rights that apply to you, email inquire@aridlogic.com with “Privacy request” in the subject line. We may need to verify your identity before responding.

California residents: If the California Consumer Privacy Act (CCPA) applies, you may have additional rights regarding personal information, including the right to know, delete, and opt out of certain sharing (we do not sell personal information as defined by the CCPA). You may designate an authorized agent where permitted by law.

Email preferences: For commercial nurture messages, use the unsubscribe link in the email or contact us at inquire@aridlogic.com. Transactional messages related to downloads, billing, or your engagement may still be sent as needed.

Text messages:reply STOP to opt out of texts from a business using our Missed-Call Service, or HELP for help. To stop optional owner-alert texts, reply STOP to an alert; that stops alert texts only and does not cancel the kit. If you are a caller, see "Callers' privacy requests" in the SMS and call data section. See our SMS Terms.

International visitors

We are based in the United States. If you access our site from other regions, your information may be processed in the United States or other countries where we or our service providers operate. Those countries may have data protection laws that differ from those in your jurisdiction. Where required, we use appropriate safeguards for cross-border transfers.

Children

Our services are directed to businesses and adults. We do not knowingly collect personal information from children under 13 (or the age required by local law). If you believe we have collected information from a child, please contact us and we will take appropriate steps to delete it.

Third-party links

Our site may link to third-party websites or services we do not control. This policy does not apply to those third parties. Review their privacy policies before providing information.

Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the “Last updated” date above and, where appropriate, provide additional notice. Your continued use of the site after changes become effective constitutes your acknowledgment of the revised policy, to the extent permitted by law.

Contact

AridLogic, a division of AliJede Solutions LLC
Attention: Privacy
Email: inquire@aridlogic.com

Related documents: Terms of Service, Cookie Policy, Accessibility, SMS Terms.