Skip to content
Isletby NextWinDev
OverviewPrivacyTerms of use

Transparency, without the fine print

Privacy policy

What Islet accesses, why it needs it, and the choices you have. Google Calendar is optional, and its data is used for calendar features—not advertising.

Last updated November 1, 2026 · Applies to Islet by NextWinDev and this website

On this page

01 · Who we are02 · Data and purposes03 · Google Calendar04 · Sharing and services05 · Storage and deletion06 · Security07 · Your rights08 · Children09 · Changes and contact

The short version

Local tools keep their content on your PC. Online features send the information needed to the relevant service. You choose whether to connect Google Calendar or run an AI action. We do not sell Google user data or use it for advertising.

This summary is a guide; the sections below explain the details.

01. Who we are

ADAPTIVE SOLUTIONS TECH LTD, company number 14922021, operates Islet under the developer brand NextWinDev and is the controller of personal information processed under this policy. Its business contact address is International House, 12 Constance Street, London, E16 2DQ, United Kingdom.

In this policy, “Islet” means the Windows desktop app, and “we,” “us,” and “our” refer to ADAPTIVE SOLUTIONS TECH LTD. This policy covers Islet and the Islet website at droidhack.org, not unrelated products or sites.

For privacy questions or requests, email support@droidhack.org with “Islet privacy” in the subject, or write to the business contact address above.

02. Data we access and why

The data involved depends on the sections you enable and the actions you take. “Access” includes data the app handles locally even when it is not sent to us.

Feature / informationHow it is usedWhere it is handled
Clipboard text, links, images; notes; shelf items and file referencesShow history, search, pin, copy, take notes, and move files.Locally on your Windows device, unless you explicitly submit content to an online feature or another app.
Google account email, authorization tokens, calendars, and eventsIdentify the connected account, maintain access, show calendars and reminders, and carry out event changes you request.Between your device and Google, with local sign-in storage and an event cache. See section 03.
Windows calendar informationDisplay events and reminders from calendars made available through Windows permissions.Through Windows on your device; account synchronization is also subject to your calendar provider’s policies.
AI prompts, selected text, chat messages and context, or a selected screen imageGenerate a reply or perform the AI action you request.Processed temporarily on NextWinDev’s private server. AI request and response content is not retained on the server after processing. Local app storage is separate; see section 05.
Approximate location from IP address, a city you select, and forecast coordinatesFind your weather location and retrieve forecasts.IP geolocation and weather services; your selected place and preferences may be saved locally.
Media metadata, Bluetooth device names and battery levels, audio/display settings, app activity, shortcuts, and preferencesProvide controls, activity capsules, device status, and your chosen layout.Through Windows APIs and local app storage. A microphone/camera activity indicator does not mean Islet uploads an audio/video recording.
Cryptocurrency pairs, prices, and alert settingsFetch public market data and show your selected alerts.Market-data requests go to the relevant exchange; preferences are stored locally. These features do not require a trading-account password.
Store entitlement and subscription statusDetermine access to paid features and process purchases through Microsoft.Microsoft Store services. Payment-card processing is handled by Microsoft, not by an Islet payment form.
Support email and information you choose to includeRespond to your request and investigate an issue.Our support mailbox and email service. Please do not email passwords, access tokens, or unnecessary sensitive content.
Technical connection information, such as IP address, request time, and service/error informationDeliver web and online-service requests, maintain reliability, and investigate abuse.The hosting or online-service infrastructure receiving the request. Retention and providers require operational confirmation before publication.

This static website contains no advertising pixels, analytics scripts, third-party fonts, or cookie-based tracking code. The landing page uses a local animation script that does not collect or transmit information. Hosting infrastructure may still process connection information. This statement does not describe the independent websites you open using our links.

03. Google Calendar data

Connecting is your choice

Islet accesses your Google account only after you choose to connect it and authorize access through Google’s sign-in and consent flow. We do not ask for or receive your Google password. Declining access leaves the Google Calendar integration unavailable; it does not require you to stop using unrelated local features.

Permissions requested

  • openid and email: identify the Google account you connected and display its email address.
  • https://www.googleapis.com/auth/calendar.calendarlist.readonly: retrieve your calendar list, including identifiers, names, colors, selection, and access role, so Islet can show the calendars available to you.
  • https://www.googleapis.com/auth/calendar.events: read event information and create, update, or delete events when you use those actions. This is not a read-only permission.

Information accessed and how it is used

Calendar responses can contain calendar and event identifiers, event titles, descriptions, locations, start and end times, time zones, all-day and recurrence information, status, organizer or attendee information, and meeting or event links. Islet uses relevant event fields to display your agenda, show meeting reminders, open meeting links, and support event actions. The app periodically refreshes events while the calendar section is enabled and may request additional dates when you browse.

When you create or change an event, Islet sends the fields you enter or change to Google. Islet deletes Google Calendar events only in response to your explicit request. It does not automatically delete events from your Google account. Event changes, invitations, and visibility are governed by Google Calendar permissions and settings. Opening a meeting link connects you to its meeting provider; that provider’s privacy policy then applies.

Storage, sharing, and Limited Use

Calendar API requests go directly from the app to Google over HTTPS. The integration does not send your Google authorization tokens or calendar event feed to a NextWinDev calendar server. Your refresh token, connected email, and granted scopes are stored locally using Windows Data Protection API encryption for the current Windows user. Access tokens are kept in memory. Event information is also cached locally so the agenda can remain available between refreshes or while offline.

Islet’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 user data is used only to provide the visible calendar features described here. We do not sell it, use it for advertising or credit decisions, or use it to train generalized AI or machine-learning models. The Calendar integration does not automatically send Google Calendar data to the AI service. If you independently copy calendar information and submit it in an AI request, that is a separate action you choose to take.

We do not allow people to read Google user data except with your affirmative agreement to access specific data, where necessary for security investigations, to comply with applicable law, or as otherwise permitted by Google’s Limited Use requirements. Any permitted transfer must be limited to providing the disclosed user-facing feature with your consent, security, legal obligations, or a business transfer with your prior explicit consent, as required by that policy.

Disconnecting and revoking access

Use the Google sign-out control in Islet’s Calendar settings to disconnect. Islet clears its in-memory sign-in state, attempts to delete the saved local grant, and attempts to revoke the token with Google. File locks or network failures can prevent deletion or revocation from completing. You can independently remove Islet’s access at Google Account → Third-party connections. Revoking access prevents new authorized API requests; it does not delete events already saved in your Google Calendar.

Disconnecting is not a promise that all cached event content is immediately erased. Local calendar caches can persist until replaced or removed. To remove remaining local data, close Islet and remove its local app data using the instructions in section 05. Contact support if you need help identifying the correct files.

04. Sharing and services

Online services receive the requests necessary for the feature you use, including ordinary connection metadata such as your IP address. Current integrations include:

  • Google: sign-in, token management, and Google Calendar. See Google’s privacy policy.
  • Microsoft: Windows platform services and Microsoft Store purchases, licensing, and subscriptions. See Microsoft’s privacy statement.
  • Weather: IPWho.is for IP-based approximate location and Open-Meteo for place search and forecasts. See IPWho.is privacy information and Open-Meteo terms and privacy information.
  • Market data: Binance public market-data services and Bybit for requested price information. See Binance privacy information and Bybit’s privacy policy.
  • AI processing: submitted AI content is handled privately on NextWinDev’s private server solely to process your request. AI request and response content is not retained on that server after processing. This describes AI content, not separately handled support messages, technical connection information, or local app data.
  • Hosting and email: infrastructure providers process website requests, service requests, or support messages on our behalf. Their identities and retention arrangements must be confirmed before publication.

We may disclose information where legally required or necessary to protect security and investigate abuse, subject to applicable law and the additional Google-data restrictions above. Service providers may process data outside your country. Where required, appropriate transfer safeguards must be in place; the actual jurisdictions and safeguards must be confirmed before this draft is published.

05. Storage, retention, and deletion

  • Local content and preferences: clipboard history, notes, shelf data, and settings remain in local app storage until removed through the relevant feature, replaced by the app’s storage behavior, or removed with local app data. Removing a shelf reference is not necessarily the same as deleting the original file.
  • Google sign-in: the saved grant remains until disconnection or local-data removal; an access token expires and may be refreshed while the account is connected. Local token-file deletion can fail if the file cannot be accessed.
  • Calendar cache: event information can remain locally between sessions and during offline use. Turning the section off or revoking Google access does not by itself guarantee removal of the cache. Removing a local cached copy is separate from deleting an event in your Google account; Islet only requests the latter when you explicitly ask it to.
  • Removing local app data: close Islet, then use the Windows app reset/data-removal option if available for your installation. Otherwise, ask support for the app-data location for your installed package before deleting files. Uninstallation can leave data or backups depending on Windows and your installation method. Do not delete unrelated folders. Removing local data does not delete your Google Calendar events or cancel a Store subscription.
  • AI content: AI requests and responses are processed temporarily on our private server and are not retained there after processing, including in content logs, persistent caches, or backups. This server-side policy does not mean all data is absent from your device: content you keep in the app or save elsewhere remains subject to that local storage.
  • Support and technical server logs: these are separate from AI request and response content. Specific retention periods, deletion procedures, and backup expiry for support messages and technical metadata must be completed before publication.

We cannot remotely erase information that exists only on your device. Google and Microsoft retain information in their services under their own policies; you may need to use their account controls as well as contacting us.

06. How information is protected

Google authentication and Calendar requests use HTTPS. Saved Google grants are protected using Windows DPAPI for the current Windows user. This protection does not mean every local file is encrypted: calendar caches, clipboard content, notes, and other app files should also be protected by your Windows account permissions, device security, and disk encryption where available.

No app or network can guarantee absolute security. Keep Windows and Islet updated, protect access to your account, and avoid sharing logs or screenshots containing private content or credentials.

07. Your choices and privacy rights

You can choose which sections to enable, decline or revoke Google access, manage Windows permissions, remove local content, and decide whether to submit content to AI. Permission to connect a service is not blanket consent to unrelated uses.

Where applicable, we process information to provide the features you request and perform our contract with you; on the basis of consent where required for optional access or processing; for legitimate interests such as maintaining service security and responding to support, subject to your rights; and to comply with legal obligations.

Depending on your location and the applicable law, you may have rights to access, correct, delete, or receive a portable copy of information, restrict or object to processing, and withdraw consent without affecting prior lawful processing. You may also complain to your local data-protection authority. We do not sell Google user data or share it for cross-context behavioral advertising.

Send requests to support@droidhack.org. Tell us what you need and the relevant service; do not send identity documents unless we request a proportionate verification method. We may need to verify your identity and will respond within applicable legal deadlines. Rights may be limited by legal retention requirements or by the fact that we do not hold your locally stored data.

08. Children’s privacy

Islet is a general-purpose desktop utility and is not directed at children under 13. We do not knowingly collect children’s personal information through our online services. If you believe a child has provided information to us, contact support so we can investigate and take appropriate action. The applicable Store age rating and local age requirements also apply.

09. Changes and contact

We will update the date on this page when the policy changes. Material changes will be communicated as required by law. Before using Google user data for a new purpose or requesting additional access, we will update the disclosures and obtain any required consent.

Legal operator and controller: ADAPTIVE SOLUTIONS TECH LTD
Company number: 14922021
Address: International House, 12 Constance Street, London, E16 2DQ, United Kingdom
Developer brand: NextWinDev
Product: Islet for Windows
Website: droidhack.org
Privacy and support: support@droidhack.org

© 2026 NextWinDev. Islet for Windows.

OverviewPrivacy policyTerms of useContact