Privacy Policy

1. Who handles your information

NILO is operated by Vignesh Rapaka in Hyderabad, Telangana, India. Email hello@nilo.my for support, privacy requests, grievances, or legal notices. This policy covers our site, studio, profiles, forms, short links, and native bookings.

We decide how account, operational, and security information is used. Creators and hosts separately decide how to use information submitted to them and their exported copies. They have their own privacy obligations. Contact them about their use and us about NILO’s handling or help finding the right route.

2. Information we collect

• Account and content: your sign-in identifier, email address, verification status and basic profile information; username, profile, links, design, media, drafts, published snapshots, card details, and settings. NILO does not receive your ChatGPT conversations through sign-in. Google and email accounts use Google Firebase Authentication. Firebase processes email/password credentials and Google sign-in information; NILO does not store your password in its application database.
• Contacts and forms: names, email addresses, messages, creator-defined answers, consent records, and creator contact notes and labels.
• Poll responses: the selected answer, poll version, submission time and a hash of a random receipt specific to that poll. Creators and visitors can see aggregate results. Poll receipts are separate from analytics and do not establish a voter’s identity.
• Bookings: meeting types, availability, guest name and email, time zones, chosen times, optional notes, consent and status, management-link credentials, and calendar-sync records.
• Usage and security: view, click, form, and vCard-download events; timestamps, referrer domains, broad device, browser and operating-system categories, country-level location supplied by our hosting provider, campaign labels and UTM source or medium, and sources such as QR or NFC. Hosting and security providers also process request information such as IP addresses, browsers, and diagnostic logs.
• Communications: support messages, reports, appeals, moderation records, and operator audit records.
• Optional Google connection: Google email, authorization credentials, primary-calendar busy intervals, and NILO event-copy information described below.
• Optional social connections: connected Spotify or TikTok account identifiers, display names, profile URLs, encrypted access and refresh credentials, and the public content you choose to display. Spotify listening history is read and shown only when you select recently played music and confirm public sharing.
• Earlier Google Analytics data: Google Analytics is currently disabled on NILO. If you previously accepted it, Google may retain earlier analytics-cookie identifiers, public-page usage, session information, and broad device or location data under its retention rules. See section 8.

Do not submit passwords, card details, identity documents, health records, or similarly sensitive information. Review extra fields a creator asks you to submit before sharing.

3. How and why we use it

We use information to sign you in, save and publish content you choose, deliver forms and bookings, check calendar conflicts, maintain appointment copies, provide counts and exports, troubleshoot issues, respond to requests, prevent abuse, enforce rules, and meet legal obligations.

Where a legal basis is required, we rely on providing the service you request, consent for optional connections and disclosures, legitimate interests in operating and securing the service where legally available and balanced against your rights, or legal obligations. Another basis does not substitute for consent where consent is required. Withdrawing optional consent stops future processing dependent on it, without undoing prior lawful processing.

We do not sell personal information, use it for cross-site targeted advertising, or use connected Google data to train general-purpose AI models. NILO currently does not process payments or send marketing email. New payment or materially different data uses would require appropriate disclosures and any required fresh consent before starting.

4. Public content and your choices

Drafts, saved contacts, and account analytics are excluded from public snapshots. Publishing creates a separate copy of visible blocks and chosen details. Publish again after changing email or phone visibility to update the public page and vCard. Unpublishing disables the NILO page, card, and profile redirects; standalone short links must be paused or deleted separately.

Anyone with the URL may see a published page when hosting access permits it. Search discovery is off by default; a no-index instruction is not access control. Others may retain screenshots, downloaded cards, exported records, and cached public information. Unpublishing cannot erase their independent copies.

5. Optional connected services

Google Calendar

NILO requests Google email, availability access, and permission to see, create, change, and delete events on calendars you own. Google’s displayed permission is broader than our current use: we check primary-calendar busy times and create, read, update, or remove copies of confirmed NILO appointments. We do not scan unrelated event titles, descriptions, or attendees.

We store your Google email and an encrypted refresh token; short-lived access tokens are used for authorized requests. Busy intervals calculate slots rather than form a separately stored calendar history. NILO stores event identifiers and sync information to maintain its appointment copies.

Calendar copies include meeting details, guest name and email, and optional notes. These are sent to Google and may be visible to people the host has allowed to view their calendar. NILO does not add attendees or send invitations. Guests see the calendar disclosure before booking. Editing a Google event does not edit NILO.

NILO’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google data is used for authorized scheduling, not advertising, sale, credit decisions, or generalized AI training. Human access is limited to your affirmative permission for specific support, necessary security investigation, compliance with law, or other uses expressly allowed by that policy. Providers may process it only as needed for authorized features under those restrictions.

Disconnect in Bookings → Calendars to delete NILO’s stored Google credentials. You can also revoke access in Google Account connections. Existing Google events are not automatically erased by disconnecting or deleting NILO; remove them in Google Calendar. Revocation does not delete native appointments. Google handles its copies under its Privacy Policy.

Social content

Where available, you can connect Spotify for recently played music or TikTok for your public videos. Connection requests use the provider’s authorization screen. NILO stores encrypted credentials and account identifiers to refresh this content without asking you to paste each new post. We request read access, not permission to publish posts, follow accounts, send messages, or change your music playback.

Listening activity is not public by default. You must select it, confirm public sharing, and publish the block. The chosen feed then becomes visible to anyone who can view your public page. Public Spotify artist releases and podcast episodes do not read your listening history. Provider metadata is temporarily cached in server memory for up to 15 minutes, or two minutes for listening history; connection records remain until you disconnect or delete the workspace/account.

Use Disconnect from NILO in the block’s automatic-update controls to delete the stored connection and stop subsequent feed requests from using it. You can also remove NILO’s access in the provider’s account settings. Deleting a connection does not erase copies already viewed or retained by other people or the provider. External services may limit access, require reconnection, or remove content.

6. Forms, guests, and management links

Form and booking submissions are stored by NILO and shared with the selected creator or host for the stated purpose. Connected hosts may also receive Google appointment copies. A signup form records a request for updates; NILO does not currently subscribe anyone through an email provider.

Private management links are keys: anyone holding one can view an appointment and may cancel or reschedule it. Keep them private. NILO currently sends no booking confirmation or cancellation emails, so save your link. Cancellation changes status rather than erasing the record. Contact the host and hello@nilo.my about deletion; exported and external calendar copies require separate handling by their holders.

7. Recipients and international processing

Information is disclosed to recipients you choose, including visitors or hosts; necessary service providers; and authorities or others where required by law or reasonably necessary for security, fraud prevention, or rights claims. Access is limited to its purpose. A lawful business transfer may involve data with appropriate safeguards, required notices, and protections applicable to the original collection.

Current infrastructure includes OpenAI Sites and ChatGPT sign-in, Cloudflare hosting/database/media storage, and Google for connected calendars and Firebase Authentication. Google Analytics is currently disabled; Google may retain data collected with earlier consent under its retention rules. External image and font hosts receive ordinary network information when resources load. Video and music players load when you choose to open them; their providers apply separate privacy and cookie practices. Links lead to independent services.

Providers may process data outside India. Applicable safeguards depend on provider, destination, and law. We do not promise India-only hosting or independently certified transfer arrangements. Ask us before submitting information subject to specific location or contractual restrictions.

8. Cookies, storage, and analytics

NILO records aggregate creator activity automatically as part of the service, subject to supported browser privacy signals. These built-in Insights counts use no analytics cookies, persistent visitor identifiers, fingerprinting, precise location, or contact-book scraping. Counts measure requests rather than unique people; repeat visits and imperfect bot filtering affect them. Reports combine activity by asset, campaign, channel, country, and broad browser or device category. Country is coarse network-derived information, and can be unknown or affected by VPNs. NILO does not store raw IP addresses in creator analytics or connect activity to a named visitor. Short-lived hashed IP controls limit abuse and are not visitor analytics.

Sign-in, security, and hosting providers may use cookies or equivalent storage needed for their functions. Google and email sign-in uses Firebase browser storage to remember and refresh your login. NILO keeps a secure, HTTP-only sign-in cookie that expires after one hour and is renewed while you use the studio. Sign out to clear this browser’s login. These necessary sign-in functions are separate from analytics. A separate necessary cookie remembers your selected workspace for up to one year; ownership is checked whenever it is used. NILO remembers theme preferences in browser local storage. When you vote, a random receipt for that poll is kept in local storage to restore your confirmed choice and avoid counting ordinary retries twice. Clearing storage or using another browser can allow another response. These polls are not identity-verified ballots. External resources and players have their own practices. Clearing or blocking storage can affect sign-in and functionality.

Google Analytics is currently disabled. NILO does not load the Google Analytics tag or send new Google Analytics measurement requests. Built-in aggregate creator Insights continues independently and does not require Google Analytics cookies.

Earlier versions loaded Google Analytics only after browser opt-in and used cookies such as _ga and _ga_*. When the current site opens, it disables NILO’s earlier tracker and attempts to remove those accessible cookies for this site. This cleanup does not clear your sign-in cookies or account storage. A browser that blocks cookie access may prevent cleanup; you can also remove site cookies through your browser settings. Google may still hold information collected with earlier consent, including ordinary network information. Its processing may take place outside India. Read how Google uses information from sites that use its services.

Disabling collection and clearing cookies do not erase information already processed by Google. Contact hello@nilo.my about past-data requests; we may need the relevant browser identifier to locate a record. You can also use Google’s Analytics opt-out browser add-on.

9. Retention and deletion

• Profiles, uploads, settings, contacts, appointments: generally remain until removed through available tools or account deletion. Appointments, including cancellations, currently remain until account deletion or an operator-assisted request. Unpublishing is not deletion.
• Firebase sign-in records: authentication identifiers and credentials remain with Firebase until removed. Deleting workspace data does not currently remove the Firebase sign-in record automatically; contact hello@nilo.my to request its removal. Signing out clears this browser’s session, without deleting your account.
• Google credentials: removed from NILO on disconnect or account deletion. Temporary OAuth state expires after its short authorization window. Google event copies are not automatically deleted.
• Built-in analytics and abuse-control rows: current maintenance removes raw analytics older than 90 days and expired rate-control rows. An operator runs it; no automatic scheduler is configured, so retention can exceed the target until maintenance runs.
• Earlier Google Analytics data: new collection is disabled. The earlier property’s user-level and event-level data retention was configured to two months, with reset on new activity disabled. Standard aggregated reports may remain longer under Google’s retention rules. Disabling the tracker does not delete those records; a separate request is needed for available past-data deletion.
• Reports, audits, support, and legal records: may remain as needed for cases, security investigations, claims, or legal duties. Purpose, sensitivity, continuing need, and applicable retention obligations determine duration.
• Backups and provider logs: may outlast active deletion under provider recovery/retention processes. We do not currently publish a verified fixed purge period for every backup or log. All copies do not necessarily disappear immediately.

Account deletion removes active NILO records and attempts removal of associated uploaded media. Database and file deletion are separate operations; contact us if deletion appears incomplete. It does not delete ChatGPT or Google accounts, external copies, or creator exports. Limited records may be preserved for a valid legal hold or security need, not unrelated uses.

10. Controls, requests, and grievances

Edit, publish or unpublish, export supported profile/links/contacts/analytics data in Settings, disconnect Google, or delete your account. Guests can manage appointments with their private links. For other information or requests, email hello@nilo.my with the relevant account/page and what you need. Do not email passwords or private booking keys.

Depending on applicable law, you may have rights to access, correct, erase, obtain copies, restrict or object to processing, withdraw consent, and complain to a competent authority. We verify requests proportionately and respond within applicable legal time limits. Rights have lawful exceptions; we will explain a refusal where permitted.

Our privacy and grievance contact is Vignesh Rapaka, hello@nilo.my, based in Hyderabad, Telangana, India. Mandatory rights to approach a competent authority or court remain available. This policy does not claim certification or universal legal compliance.

11. Security and children

We use access controls, encrypted Google refresh-token storage, and other safeguards intended to protect information. No system is completely secure. Protect sign-in, review published content, and keep management links private. Report suspected exposure to hello@nilo.my without unnecessary sensitive data. We will make notifications where law requires.

NILO is not directed to children. Workspace creation and form or booking submissions are intended for adults aged 18 or above. We do not knowingly seek children’s data. Contact us if a child may have provided information so we can investigate and act appropriately. This rule is not a claim that age verification is installed.

12. Policy updates

Updates will be dated here. Material changes receive an appropriate prominent notice in advance where reasonably practicable and fresh consent where required. New wording does not authorize incompatible uses of previously collected information. If payments or integrations are introduced, we will explain actual providers and data flows before they apply.