Privacy Policy

1. Controller and scope

FiveToClose (“we,” “us,” or “our”) operates the website wheretheyask.com and the WhereTheyAsk software service (collectively, the “Services”). This Privacy Policy describes how we collect, use, disclose, retain, and protect personal information in connection with the Services. By accessing or using the Services, you acknowledge that you have read this Policy. Seller of record is FiveToClose.

2. Categories of information we collect

We may collect and process:

• Identity and contact data — name and email address obtained when you sign in with Google, and any name displayed on your Google profile.
• Account and authentication data — Google account identifier, session cookies, a confirmation token for your email, and sign-in timestamps. We do not receive or store your Google password.
• Second step. If you turn on a second sign-in step, we store your phone number and the secret that makes the authenticator code. The phone number and the secret stay on your account. They are not shown on your public page. We do not send a text message to that number.
• Calendar and mail access. When you sign in, we store a Google refresh token on your account. An event you create, an event a friend invites you to, or an event you mark as going is written to the Google Calendar of that same Google account. An invite can also be sent from your Gmail to the friends you pick. We do not read your inbox or the rest of your calendar.
• Community content — the profile, posts, replies, photos, pages, groups, events, and live chat you submit, plus camera and microphone media while you host a live room in your browser. Private messages are stored for the two people in that conversation and are not shown on a public page. A song, a background, and the look of a profile are shown on that profile only. A song the member does not own is kept as a 5 second clip.
• Older billing data — if you were charged before the Services were free: plan, purchase dates, paid-through dates, Stripe customer and subscription identifiers, and amounts paid. Full payment card numbers are processed by Stripe and are not stored on our servers.
• Technical and usage data — IP address, browser type, device characteristics, pages viewed, and diagnostic logs used to operate, secure, and improve the Services.
• Communications data — messages you send to support and related metadata.

3. Purposes of processing

We process personal information to:

• Create and authenticate your account, including the confirmation link sent to your email;
• Ask for a 6 digit authenticator code when you have turned the second step on;
• Email the Google address you signed up with, from support@fivetoclose.cloud, when someone adds you, messages you, replies to you, writes on your page, invites you to an event, says they are going, or follows a page or joins a group you run. These start on. Turn it off on Account, or turn one kind off there.
• Show your page, feed, groups, events, and live rooms to the people allowed to see them, and deliver a private message only to the person it was written for;
• Count each signed-in visit to a page. The page shows that number as profile views. It does not show who visited.
• Write an event you create, are invited to, or mark as going onto the Google Calendar of the account you used to sign in, and send an invite from that account's Gmail to friends you choose;
• Keep records of older charges, prevent fraud, and maintain accounting records;
• Provide customer support and service announcements;
• Secure the Services, debug faults, and improve product quality;
• Comply with legal obligations and enforce our Terms of Service.

4. Legal bases (where applicable)

Where data-protection laws require a legal basis, we rely on: (a) performance of a contract (providing the subscribed service); (b) legitimate interests (security, product improvement, limited service communications); (c) consent (where required, including certain optional cookies); and (d) legal compliance.

5. Google sign-in

Sign-in uses Google OAuth. Google authenticates you and returns a verified email address, name, and a stable account identifier. We use that information to create or recognize your WhereTheyAsk account. We also ask to add events to your Google Calendar and to send an invite from your Gmail. We store a refresh token for that. We do not read your inbox, and we do not post to YouTube or any other Google product. Your use of Google is governed by Google’s terms and privacy policy.

6. What we do not do

We do not sell personal information. We do not read your Gmail. The only write to your Google account is an event on your calendar, and an invite email you asked us to send. Photos, SnapShots, and live video stay on this service for the people allowed to see them. A SnapShot is removed from view after a day.

7. Service providers and disclosures

We may disclose information to:

• Payment processors (Stripe) for older charges, invoicing, refunds, and fraud prevention;
• Authentication and email providers (Google for sign-in, and our mail host for the confirmation link);
• Infrastructure providers necessary to host the Services;
• Professional advisers and authorities when required by law or to protect rights, safety, and integrity of the Services.

Providers are instructed to process data only as needed to perform services on our behalf.

8. Cookies and similar technologies

We use a first-party session cookie (wta) to keep you signed in and a short-lived cookie during Google sign-in (wta_oauth). These cookies are necessary for the Service to function. They are not advertising cookies. You may control cookies in your browser; disabling the session cookie will sign you out.

9. Retention

We retain account, community, and older billing records for as long as your account is active and thereafter as reasonably necessary for billing disputes, legal compliance, security, and legitimate archival needs, unless a longer period is required or permitted by law. You may request deletion as described below.

10. Security

We implement administrative, technical, and organizational measures designed to protect personal information, including encrypted transport (HTTPS), access-restricted servers, and hashed session tokens. A public page may be shown inside a preview frame on buildhop.io. Sign-in leaves that frame. No other site may frame the page. No method of transmission or storage is completely secure. You use the Services at your own residual risk.

11. International transfers

Our infrastructure and service providers may process data in the United States and other jurisdictions. Where required, we take steps reasonably designed to ensure that transfers receive an adequate level of protection under applicable law.

12. Your rights

Depending on your location, you may have rights to access, correct, delete, or restrict certain processing of your personal information, to object to processing, or to data portability. To exercise rights, email support@fivetoclose.cloud. We may need to verify your identity before fulfilling a request. Internal operator accounts used to run the Service are not customer records.

13. Children

The Services are not directed to individuals under 18. We do not knowingly collect personal information from children. If you believe we have done so, contact us and we will take appropriate steps to delete such information.

14. Changes to this Policy

We may revise this Privacy Policy from time to time. The “Effective date” above will be updated when material changes are posted. Continued use of the Services after the effective date constitutes acceptance of the revised Policy, except where applicable law requires additional consent.

15. Contact

Privacy inquiries: support@fivetoclose.cloud. Please check spam and promotions folders for replies.