Clear from the beginning

Privacy notice.

How information moves through our website, payment checkout and private order records.

Information you provide

Stripe can process information entered during checkout before a payment succeeds. An abandoned, expired or unpaid session may remain in Stripe's records. Leaving checkout does not guarantee that information already provided to Stripe is deleted.

Payment details are entered on Stripe's hosted page. Our checkout application does not collect full card numbers in the project form or copy card data into Google Calendar. Stripe describes its handling of payment and device information in its privacy policy.

How we use this information

We use project and contact information to understand requests, communicate about the service, agree on scope and pricing, deliver websites, manage payments and support orders. Our server receives your checkout intake before payment and signed Stripe notifications, including notifications that may describe an unpaid session. Project information in an abandoned session may remain in Stripe; an unpaid or abandoned checkout does not create a Calendar order record.

When the site is hosted, its hosting provider can process technical request information such as IP addresses, request times, browser information and security logs to deliver and protect the service. This version of the website does not include advertising pixels or analytics trackers. Stripe and other providers can use their own security and processing technologies under their policies.

Our private Google Calendar order log

After the server verifies a signed Stripe notification confirming payment for a website purchase, it creates an all-day order record in a dedicated calendar owned by Onsite Agency's operator. This applies to both monthly-hosting/care setup purchases and outright website purchases.

The record contains the submitted name, email, business name, required phone number and project brief, chosen package and purchase option, gross paid amount, order/subscription references and order date. Billing contact information supplied through Stripe may also identify the payer. Card details are not copied into Calendar. Customers are not added as attendees or sent Calendar invitations.

The owner authorizes only the Google Calendar permission calendar.app.created. This lets the app create a dedicated secondary calendar and read or manage events on app-created calendars. We use calendar metadata and existing order markers to verify access and prevent duplicate records. This connection does not request access to customers' calendars or to events on all calendars the owner owns.

Google OAuth credentials and refresh tokens stay in private server configuration. The owner can revoke authorization in their Google Account; revoking access stops future API access and does not automatically delete existing calendar or payment records.

Google API information is used only for the disclosed order-record function, consistent with the Google API Services User Data Policy and its Limited Use requirements. We do not sell this information or use it for advertising or AI model training.

The order calendar is intended for the owner only. Google Calendar permissions still determine access, so a person later granted sufficient calendar permissions could read private events. Any customer booking-calendar connection purchased as part of a website project is configured separately with that customer's agreement.

Providers and sharing

Stripe handles checkout and payment records. Google handles the private order calendar and messages sent to our Gmail support address. The website host delivers the site and its API. These providers process information needed for those functions under their own terms and privacy practices. See Google's privacy policy and Stripe's privacy policy.

Information may also be used or disclosed when needed to address fraud, protect the service, resolve a dispute or meet applicable obligations. We do not sell customer contact information or Google API data.

Storage, retention and your choices

Order and support information is kept as needed to deliver and support the service, maintain payment and business records, resolve issues and meet applicable obligations. We do not promise a fixed automatic deletion period. Provider records and backups can follow separate retention practices.

To ask about your information, request a correction or request deletion, email contact.ahmed.sites@gmail.com. We may need to confirm your identity and explain which records can be changed or deleted. Payment, dispute or other required records may need to be retained.

Do not include payment-card details, passwords or information unrelated to your project in a brief or support email. Private configuration, access controls and encrypted connections are used to protect service information; no online system can promise absolute security.

Changes and questions

We update this notice when the service's information practices change and show the revised date above. Questions can be sent to contact.ahmed.sites@gmail.com.