What the site collects, why it collects it, and how purchase records may be used.
This policy explains the site’s handling of account information, email preferences, operational analytics, service-intake records, purchase-related logs, and third-party services used to operate Avery Logic Works.
Account, contact, and request details
If you create an account, join updates, make a purchase, submit a private service request, donate, subscribe, or contact the site, Avery Logic Works may collect the information you provide directly, such as your email address, display name, newsletter preference, supporter-update preference, billing-related contact details, and any message contents or project details you send.
Visit, session, and payment-related activity
The site may record operational data such as page visits, referrers, browser or device signals, visitor/session identifiers, account creation events, login events, settings changes, service-intake activity, checkout-start events, successful payment events, refunds, disputes, and related system timestamps used for security, debugging, fraud review, and business operations.
Running the site, fulfilling purchases, and reviewing billing issues
- To create and maintain accounts
- To confirm email ownership and support password resets
- To honor newsletter and supporter-email preferences
- To operate supporter, donation, subscription, or service-purchase flows
- To log purchase and fulfillment records connected to a transaction
- To monitor site activity, performance, misuse, and abuse
- To review duplicate charges, refunds, cancellations, and disputes
- To respond to support, billing, or policy questions
Newsletter messages are preference-based.
If you opt into newsletters or future supporter updates, your email may be sent to a mailing service provider to deliver those messages. Newsletter and supporter communications are intended to remain optional, and future emails should include an unsubscribe path where appropriate.
Some infrastructure is handled by outside services.
The site may use third-party providers for hosting, authentication, database storage, mailing operations, media delivery, analytics, and payment processing. Examples in the current build include Supabase for account, database, and function infrastructure, EmailOctopus for newsletter operations once enabled, and Stripe or other processors when support or purchase features are live.
Payment-card details are usually handled by the processor, while the business keeps transaction records.
When support, subscriptions, or purchases are processed through a payment provider, full payment-card details are typically handled by that processor, not stored directly by the public site code. Avery Logic Works may still receive and retain billing-related records such as transaction identifiers, payment status, customer email, charge, refund, or dispute references, and other records needed to confirm transactions, review refunds, respond to disputes, and manage supporter or service access.
Information may be kept as long as it remains useful or necessary.
Account records, email preferences, service-intake submissions, purchase logs, refund and dispute records, security logs, and operational analytics may be retained as long as needed for site operation, legal compliance, fraud prevention, billing review, security review, dispute response, or project continuity, unless a shorter retention period is required by law.
Reasonable safeguards may be used, but no system is perfect.
Avery Logic Works may use practical technical and organizational safeguards to reduce misuse, unauthorized access, accidental exposure, billing abuse, and payment-related fraud. Even so, no online system can guarantee absolute security.
You can update preferences or ask questions about account and billing records.
You can update account preferences through the site where available, unsubscribe from mailing communications when those tools are active, or contact the support or billing address for questions about account status, communication preferences, or purchase-related records.
This page may be revised as the site grows.
As the platform expands, privacy practices may change. Updated policy language becomes effective when posted unless another date is stated on the page.