Privacy policy

FortLauderDev operates fortlauderdev.com and provides website hosting and shared sign-in for participating businesses (“the sites”). This policy explains how FortLauderDev handles information through those services. Questions go to hello@fortlauderdev.com.

Each business is responsible for how it uses its customers’ messages, bookings and orders. We handle information needed to provide its website and related services, and make customer information available to that business. Its own privacy notice may explain additional uses. For questions about a booking, order or the business’s records, contact that business first; contact us about hosting, shared sign-in or information we hold.

Shared sign-in uses one identity across participating sites. Your contact profile and access permissions on each business’s site are managed separately.

What we collect

• What you send us. When you email us, fill in a contact or inquiry form, or ask for a booking, we receive what you enter, such as your name, email address, phone number and message.
• Your account, if you create one. Your email address, whether it's verified, your name if you give it, and the details you save on a site's account page. If you set a password, it is stored only by Amazon Cognito, which runs the sign-in pages; we never see it.
• Booking and order records, where those features are offered: dates, services or products, booking or order identifiers, amounts, payment choices or status, and notes you provide. Booking and payment providers may send us these records so the site can handle your request and notify the business.
• Your access on each site, for example customer, member or owner, and a record of changes to it.
• Basic technical data. Like any website, our hosting provider records requests (such as IP address, browser and the page requested) to deliver the site and protect it from abuse.

Signing in with Google or another provider

If you choose to continue with Google (or another sign-in provider a site offers), we receive a provider account identifier and basic profile information, such as your name, email address and, where supplied, whether that address is verified. For sign-in, we request only basic identity, email and profile permissions, not access to your contacts, files or calendar. A verified email address may be used to link your sign-in to an existing account; providers that do not supply trusted email verification may remain separate.

FortLauderDev's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use it only to sign you in and never for advertising.

How we use it

To provide and protect the sites: to answer your messages, handle bookings and orders, send confirmations and business notifications, sign you in, show the details you save, decide what you can see or change, and investigate abuse or service problems. We don't sell your information, share it for advertising, or use it to build advertising profiles.

Services that handle data for us

The sites rely on a few providers, each under its own privacy policy:

• Amazon Web Services provides hosting, sign-in (Amazon Cognito), account storage (Amazon DynamoDB) and booking and form email delivery. Email messages also pass through the email providers used by you and the business.
• Booking and payments, on sites that offer them: Cal.com, Square, Shopify or Stripe. These providers process bookings, checkout or payments. The site and business may receive booking or order details, transaction identifiers and payment status, and may keep copies in their systems and notification emails. Card details are handled by the payment provider; FortLauderDev does not receive or store full card numbers.
• Fonts, on pages that load Google Fonts: your browser requests font files and styles from Google, which receives technical request information such as your IP address and browser headers.
• Visit counts, on sites that turn them on: a cookie-free service such as GoatCounter or Umami measures visits, pages, referrers, browser or device characteristics and approximate location. These services may process IP addresses and browser information to derive statistics or distinguish visits without advertising cookies. The data collected and retained depends on the service and the site’s settings.

Cookies and browser storage

FortLauderDev does not use advertising cookies or build advertising profiles. The shared sign-in pages use cookies for login sessions, and embedded or linked booking and payment services may use their own cookies or storage under their policies.

The shared sign-in code keeps its access, identity and refresh tokens in browser memory, rather than persistent local storage. It keeps temporary sign-in state in session storage to complete the login redirect. On sites with a Shopify shop, a cart identifier is saved in local storage so the cart can survive a reload or later visit. Clearing browser storage removes these local entries; it does not delete records held by us, the business or a provider.

How long we keep it

Retention depends on the record and service. Account identities, site profiles and access history support sign-in and account administration. Messages, bookings, orders and payment records may also be held by the business, its email provider and the booking or payment provider. Technical logs support operation and security. We keep information for the service and for necessary security, dispute handling and applicable recordkeeping obligations, and assess deletion requests as described below.

Deleting an account does not necessarily remove every related record immediately. Records needed for legal obligations, disputes or security may be retained, and copies may remain in backups. Providers and individual businesses have their own retention practices. Contact us with the site and type of record if you need details about information we hold.

Your choices

You can ask to see, correct or delete information we hold about you by emailing hello@fortlauderdev.com. Tell us which site and records your request concerns. Use the address on your account where possible; we may need to verify your identity. We aim to respond within 30 days and will follow any applicable legal response deadlines.

Tell us whether you want to remove access to one business’s site or delete your shared sign-in identity. These are different requests: deleting the shared identity can affect sign-in across participating sites. We will explain any records we need to retain and direct you to the business or provider for records it controls.

You can also revoke Google sign-in access in your Google account’s security settings. Revoking access does not itself delete an existing account, booking, order or other stored record.

Security

We use HTTPS, encryption for stored account data, and access controls intended to limit access to what each part of the system needs. Businesses and other providers are responsible for protecting the copies they hold.

Children

The sites aren't directed at children under 13, and we don't knowingly collect their information. If you believe a child has given us information, contact us and we'll delete it.

Changes

If this policy changes, we'll update it here and change the date at the top.