Privacy Policy
Effective:
Services and scope
These policies cover the Gridheap services that link here. Read the common provisions together with the product-specific provisions below for the service you use. A separately signed agreement controls a conflict within its scope.
Products and domains
- Gridheapgridheap.com
- Gridheap Accountaccount.gridheap.com
- RShiftrshift.com, rshift.de, accounts.rshift.com, app.rshift.com
- TidyAnswertidyanswer.com
- TidyMessagestidymessages.com
- Speech Namespeech.name
- Planner.liplanner.li
- Enolaeno.la
- Dueglowdueglow.com
- Tooluse.nettooluse.net
- Agentic.Payagentic.pay
- Botsbots.pay, accounts.bots.pay, app.bots.pay
- AI Evalsaievals.app
- AI Agent Payaiagent.pay
- 4dub4dub.com, accounts.4dub.com
- AIRuntimeairuntime.dev
- nnu.usnnu.us
- TrainShelltrain.sh
- heap.pageheap.page
- Outseekoutseek.xyz
- Embeddingsembeddings.app
- Markov Nowmarkov.now
- Serializeserialize.dev
- Cowork Towncowork.town
- Coffee.mscoffee.ms
Grid Heap, Inc., a Delaware corporation (“Gridheap”, “we”, “us” or “our”) provides websites, applications and developer services. This Privacy Policy describes how Gridheap processes personal information that we collect through our digital or online properties or services that link to this Privacy Policy (including as applicable, our website, mobile application, and social media pages), as well as our marketing activities and other activities described in this Privacy Policy (collectively, the “Service”).
Read this policy together with the product-specific information for the Service you use. The categories, purposes, features and recipients below apply only where described for that product; a product does not collect every category merely because it links here.
California Notice at Collection/State Privacy Rights Notice: See the State privacy rights notice section below for important information about your rights under applicable state privacy laws.
Notice to European users: Please see the Notice to European users section below for additional information for individuals located in the European Economic Area or United Kingdom (which we refer to as “Europe”, and “European” should be understood accordingly).
Personal information we collect
Information you provide to us
Personal information you may provide to us through the Service or otherwise includes the following categories, as applicable to the product and features you use:
Contact data, such as your first and last name, email address, billing and mailing addresses, company name, and phone number.
Profile data, such as the username and password that you may set to establish an online account on the Service, photograph or picture, links to your profiles on social networks, preferences, and any other information that you add to your account profile.
Communications data based on our exchanges with you, including when you contact us through the Service, communicate with us via chat features, social media, or otherwise.
Transactional data, such as information relating to or needed to complete your orders on or through the Service, including order numbers and transaction history.
Marketing data, such as your preferences for receiving our marketing communications and details about your engagement with them.
User-generated content and input data, such as photos, images, music, videos, comments, questions, messages, works of authorship, and other content or information that you generate, transmit, or otherwise make available on the Service, as well as associated metadata. Metadata includes information on how, when, where and by whom a piece of content was collected and how that content has been formatted or edited. Metadata also includes information that users can add or can have added to their content, such as keywords, geographical or location information, and other similar data.
Payment data. Payment credentials needed to complete transactions are collected and processed by the payment processor used for the applicable product. We receive the transaction and billing records needed to provide the purchased Service.
Other data not specifically listed here, which we will use as described in this Privacy Policy or as otherwise disclosed at the time of collection.
Third-party sources
We may combine personal information we receive from you with personal information falling within one of the categories identified above that we obtain from other sources, such as:
Public sources, such as social media platforms and other publicly available sources, where described for the applicable product.
Customers, such as an organization that administers your workspace or provides information for its authorized workflow.
Service providers that provide services on our behalf or help us operate the Service or our business.
Business transaction partners. We may receive personal information in connection with an actual or prospective business transaction. For example, we may receive your personal information from an entity we acquire or are acquired by, a successor, or assignee or any party involved in a business transaction such as a merger, acquisition, sale of assets, or similar transaction, and/or in the context of an insolvency, bankruptcy, or receivership.
Third-party services, such as social media services, that you use to log into, or otherwise link to, your Service account. This data may include your username, profile picture and other information associated with your account on that third-party service that is made available to us based on your account settings on that service.
Automatic data collection
We and our service providers may automatically log information about you, your computer or mobile device, and your interaction with the Service, such as:
- Device data, such as your computer or mobile device’s operating system type and version, browser type, IP address and language settings.
- Online activity data, such as pages or screens you viewed, the website you visited before browsing to the Service, access times, and diagnostic, authentication and security records.
For more information concerning our automatic collection of data, please see the Tracking & Other Technologies section below. Product-specific information describes any additional location or communications data.
Data about others. We may offer features that help users invite their friends or contacts to use the Service, and we may collect contact details about these invitees so we can deliver their invitations. Please do not refer someone to us or share their contact details with us unless you have their permission to do so.
Tracking & Other Technologies
Cookies and other technologies. Some of our automatic data collection is facilitated by cookies and other technologies. For more information, see our Cookie Policy.
Chat and other artificial intelligence (“AI”) technologies. For products with AI features, the providers identified in the product-specific information and service provider register operate the chat and user input/prompt features that you can use through the Service. These providers may access information you share through online chats or within inputs to facilitate the provision of the Service for the purposes described in this Privacy Policy and the applicable product provisions below. The product-specific information describes the relevant inputs, routing and any restrictions on using content for model training.
For information concerning your choices with respect to the use of tracking technologies, see the Your choices section of our Cookie Policy.
How we use your personal information
We may use your personal information for the following purposes or as otherwise described at the time of collection, as applicable to the product and features you use:
Service delivery and operations
We may use your personal information to:
-
provide the Service;
-
enable security features of the Service;
-
establish and maintain your user profile on the Service;
-
facilitate your invitations to friends who you want to invite to join the Service;
-
facilitate social features of the Service, such as identifying and suggesting connections with other users of the Service and providing chat or messaging functionality;
-
communicate with you about the Service, including by sending Service-related announcements, updates, security alerts, and support and administrative messages;
-
provide support for the Service, and respond to your requests, questions and feedback.
Service personalization, which may include using your personal information to:
-
understand your needs and interests;
-
personalize your experience with the Service and our Service-related communications; and
-
remember your selections and preferences as you navigate webpages.
Service improvement and analytics
We may use your personal information to analyze your usage of the Service, improve the Service, improve the rest of our business, help us understand user activity on the Service, including which pages are most and least visited and how visitors move around the Service, and to develop new products and services. Product-specific restrictions on customer content and model training apply to these uses; this paragraph does not authorize a use prohibited by those restrictions.
Direct marketing
We may send you direct marketing communications and may personalize these messages based on your needs and interests. You may opt out of our marketing communications as described in the Opt-out of communications section below.
Compliance and protection
We may use your personal information to:
-
comply with applicable laws, lawful requests, and legal process, such as to respond to subpoenas, investigations or requests from government authorities;
-
protect our, your or others’ rights, privacy, safety or property (including by making and defending legal claims);
-
audit our internal processes for compliance with legal and contractual requirements or our internal policies;
-
enforce the terms and conditions that govern the Service; and
-
prevent, identify, investigate and deter fraudulent, harmful, unauthorized, unethical or illegal activity, including cyberattacks and identity theft.
Data sharing in the context of corporate events. We may share certain personal information in the context of actual or prospective corporate events - for more information, see How we share your personal information, below.
To create aggregated, de-identified and/or anonymized data. We may create aggregated, de-identified and/or anonymized data from your personal information and other individuals whose personal information we collect. We make personal information into de-identified and/or anonymized data by removing information that makes the data identifiable to you and we will not attempt to reidentify any such data. We may use this aggregated, de-identified and/or anonymized data and share it with third parties for our lawful business purposes, including analyzing and improving the Service and promoting our business.
Further uses, in some cases, we may use your personal information for further uses, in which case we will ask for your consent to use your personal information for those further purposes if they are not compatible with the initial purpose for which information was collected.
Retention
We generally retain personal information to fulfill the purposes for which we collected it, including for the purposes of satisfying any legal, accounting, or reporting requirements, establishing or defending legal claims, or for fraud prevention purposes. To determine the appropriate retention period for personal information, we may consider factors such as the amount, nature, and sensitivity of the personal information, the potential risk of harm from unauthorized use or disclosure of your personal information, the purposes for which we process your personal information and whether we can achieve those purposes through other means, and the applicable legal requirements.
When we no longer require the personal information, we have collected about you, we may either delete it, anonymize it, or isolate it from further processing.
Product-specific retention periods and deletion commitments remain applicable where stated.
How we share your personal information
We may share your personal information with the following parties (or as otherwise described in this Privacy Policy, in other applicable notices, or at the time of collection).
Service providers. Third parties that provide services on our behalf or help us operate the Service or our business (such as hosting, information technology, customer support, AI providers described in the applicable product information, email delivery, diagnostics and website analytics).
Payment processors. Any payment card information you use to make a purchase on the Service is collected and processed directly by the payment processors identified for that product, which may include Stripe or PayPal. Their use of your payment data is governed by their own privacy policies.
Third parties designated by you. We may share your personal information with third parties where you have instructed us or provided your consent to do so.
Linked third-party services. If you log into the Service with, or otherwise link your Service account to, a social media or other third-party service, we may share your personal information with that third-party service. The third party’s use of the shared information will be governed by its privacy policy and the settings associated with your account with the third-party service.
Professional advisors. Professional advisors, such as lawyers, auditors, bankers and insurers, in the course of the professional services that they render to us.
Authorities and others. Law enforcement, government authorities, and private parties, as we believe in good faith to be necessary or appropriate for the Compliance and protection purposes described above.
Business transferees. We may disclose personal information in the context of actual or prospective business transactions (e.g., investments in Gridheap, financing of Gridheap, public stock offerings, or the sale, transfer or merger of all or part of our business, assets or shares). For example, we may need to share certain personal information with prospective counterparties and their advisers. We may also disclose your personal information to an acquirer, successor, or assignee of Gridheap as part of any merger, acquisition, sale of assets, or similar transaction, and/or in the event of an insolvency, bankruptcy, or receivership in which personal information is transferred to one or more third parties as one of our business assets.
Other users and the public. Where you choose a public feature described in the applicable product provisions below, your profile and other user-generated content and input data may be visible to other users of the Service and the public. For example, other users of the Service or the public may have access to your information if you chose to make your profile or other personal information available to them through the Service, such as when you provide comments, reviews, survey responses, or share other content. This information can be seen, collected and used by others, including being cached, copied, screen captured or stored elsewhere by others (e.g., search engines), and we are not responsible for any such use of this information.
Our service provider register identifies the applicable product, purpose, data, role and disclosed processing location. Internal platforms operated by Gridheap, independent payment providers and customer-selected services have different roles. For processing on a customer’s instructions, the applicable data processing agreement governs subprocessor authorization, notices and objections.
Your choices
In this section, we describe the rights and choices available to all users. Users who are located in certain U.S. states and Europe can find additional information about their rights below.
Access or update your information. If you have registered for an account with us through the Service, you may review and update certain account information by logging into the account.
Opt-out of communications. You may opt out of marketing-related emails by following the opt-out or unsubscribe instructions at the bottom of the email, or by contacting us. Please note that if you choose to opt out of marketing-related emails, you may continue to receive service-related and other non-marketing emails.
Cookies and other technologies. For information about cookies and other technologies employed by the Service and how to control them, see our Cookie Policy.
Blocking images/clear gifs: Most browsers and devices allow you to configure your device to prevent images from loading. To do this, follow the instructions in your particular browser or device settings.
Do Not Track. Some Internet browsers may be configured to send “Do Not Track” signals to the online services that you visit. We currently do not respond to “Do Not Track” signals. These signals differ from legally recognized opt-out preference signals, including Global Privacy Control, which we honor where required by applicable law for the processing to which they apply.
Declining to provide information. We need to collect personal information to provide certain services. If you do not provide the information we identify as required or mandatory, we may not be able to provide those services.
Linked third-party platforms. If you choose to connect to the Service through your social media account or other third-party platform, you may be able to use your settings in your account with that platform to limit the information we receive from it. If you revoke our ability to access information from a third-party platform, that choice will not apply to information that we have already received from that third party.
Delete your content or close your account. Use the deletion controls described for the applicable product or contact us using the details below.
Other sites and services
The Service may contain links to websites, mobile applications, and other online services operated by third parties. In addition, our content may be integrated into web pages or other online services that are not associated with us. These links and integrations are not an endorsement of, or representation that we are affiliated with, any third party. We do not control websites, mobile applications or online services operated by third parties, and we are not responsible for their actions. We encourage you to read the privacy policies of the other websites, mobile applications and online services you use.
Security
We employ technical, organizational and physical safeguards designed to protect the personal information we collect. However, security risk is inherent in all internet and information technologies and we cannot guarantee the security of your personal information.
International data transfer
We are headquartered in the United States and may use service providers that operate in other countries. Your personal information may be transferred to the United States or other locations where privacy laws may not be as protective as those in your state, province, or country.
Users in Europe should read the information below about Data Processing outside Europe. Product-specific information and the provider register identify disclosed processing locations; a provider’s headquarters is not necessarily its processing location.
Children
The Service is not directed to children. The applicable product terms set out the eligibility and age requirements for that product. If you are a parent or guardian of a child from whom you believe we have collected personal information in a manner prohibited by law, please contact us. If we learn that we have collected personal information through the Service from a child without the consent of the child’s parent or guardian as required by law, we will comply with applicable legal requirements to delete the information.
Changes to this Privacy Policy
We reserve the right to modify this Privacy Policy at any time. If we make material changes to this Privacy Policy, we will notify you by updating the date of this Privacy Policy and posting it on the Service or other appropriate means, and providing additional notice where required by applicable law. Any modifications to this Privacy Policy will be effective upon our posting the modified version (or as otherwise indicated at the time of posting). In all cases, your use of the Service after the effective date of any modified Privacy Policy indicates your acknowledging that the modified Privacy Policy applies to your interactions with the Service and our business.
How to contact us
For privacy questions, rights requests or privacy complaints, contact us using the details below.
- Email: legal contact form
- Mail: Grid Heap, Inc., 1111B S Governors Ave Ste 51059, Dover, DE 19904, United States.
Please identify the relevant product so that we can direct your request to the appropriate records and processing.
State privacy rights notice
Except as otherwise provided, this section applies to residents of U.S. states to the extent they have privacy laws applicable to us that grant their residents the rights described below (collectively the “State Privacy Laws”).
This section describes how we collect, use, and share Personal Information of residents of these states and the rights these users may have with respect to their Personal Information. Please note that not all rights listed below may be afforded to all users and that if you are not a resident of one of these states listed above, you may not be able to exercise these rights. In addition, we may not be able to process your request if you do not provide us with sufficient detail to allow us to confirm your identity or understand and respond to it.
For purposes of this section, the term “Personal Information” has the meaning given to “personal data”, “personal information” or other similar terms and “Sensitive Personal Information” has the meaning given to “sensitive personal information,” “sensitive data”, or other similar terms in the State Privacy Laws, except that in neither case does such term include information exempted from the scope of the State Privacy Laws. In some cases, we may provide a different privacy notice to certain categories of residents of these states, in which case that notice will apply instead of this section.
Your privacy rights. The State Privacy Laws may provide residents with some or all of the rights listed below. However, these rights are not absolute and some State Privacy Laws do not provide these rights to their residents. Therefore, we may decline your request in certain cases as permitted by law.
Information. You can request the following information about how we have collected and used your Personal Information:
The categories of Personal Information that we have collected.
The categories of sources from which we collected Personal Information.
The business or commercial purpose for collecting and/or selling Personal Information.
The categories of third parties with which we share Personal Information.
The categories of Personal Information that we sold or disclosed for a business purpose.
The categories of third parties to whom the Personal Information was sold or disclosed for a business purpose.
Access. You can request a copy of the Personal Information that we have collected about you.
Appeal. You can appeal our denial of any request validly submitted.
Correction. You can ask us to correct inaccurate Personal Information that we have collected about you.
Deletion. You can ask us to delete the Personal Information that we have collected from you.
Opt-out. Subject to the applicable State Privacy Laws, you may opt out of the sale or sharing of Personal Information, certain processing for targeted advertising, and qualifying profiling or automated decision-making. California residents may have the right to limit qualifying uses of Sensitive Personal Information. The applicable product provisions below describe the product’s information practices; these rights do not mean every product engages in those activities.
Nondiscrimination. You are entitled to exercise the rights described above free from discrimination as prohibited by the State Privacy Laws.
Exercising state privacy rights. You may submit requests to exercise the state privacy rights listed above by email or mail using the details in How to contact us. To appeal a denial, reply to our response and identify the request. We honor valid opt-out preference signals, including Global Privacy Control, as required by applicable law.
Verification of Identity; Authorized agents. We may need to verify your identity in order to process your information/know, access, appeal, correction, or deletion requests and reserve the right to confirm your residency. We use information appropriate to the request and request additional information only where needed and permitted by law.
Under some State Privacy Laws, you may enable an authorized agent to make a request on your behalf. However, we may need to verify your authorized agent’s identity and authority to act on your behalf. We may require a copy of a valid power of attorney given to your authorized agent pursuant to applicable law. If you have not provided your agent with such a power of attorney, we may ask you to take additional steps permitted by law to verify that your request is authorized, such as by providing your agent with written and signed permission to exercise your State Privacy Laws rights on your behalf, the information we request to verify your identity, and confirmation that you have given the authorized agent permission to submit the request.
Information practices. The categories of Personal Information, sources, purposes, recipients and retention criteria described above apply to the relevant product and features. Read the applicable product provisions below at collection for its specific practices, including any sale, sharing, sensitive-data or additional statutory-category disclosures.
Deidentification. We do not attempt to reidentify deidentified information derived from personal information.
Additional information for California residents.
Shine the light law. Under California’s Shine the Light law (California Civil Code Section 1798.83), California residents may ask companies with whom they have formed a business relationship primarily for personal, family or household purposes to provide the names of third parties to which they have disclosed certain personal information (as defined under the Shine the Light law) during the preceding calendar year for their own direct marketing purposes, and the categories of personal information disclosed. You may send us requests for this information using the details in How to contact us. In your request, you must include the statement “Shine the Light Request,” and provide your first and last name and mailing address and certify that you are a California resident.
Additional information for Nevada residents. Nevada residents have the right to opt-out of the sale of certain personal information for monetary consideration. To make an applicable request, use the details in How to contact us.
Contact Us. If you have questions or concerns about our privacy policies or information practices, please contact us using the contact details set forth in the How to contact us section above.
Notice to European users
General
Where this Notice to European users applies. The information provided in this “Notice to European users” section applies only to individuals in the United Kingdom and the European Economic Area (i.e., “Europe” as defined at the top of this Privacy Policy).
Personal information. References to “personal information” in this Privacy Policy should be understood to include a reference to “personal data” (as defined in the GDPR) - i.e., information about individuals from which they are either directly identified or can be identified.
Controller. Grid Heap, Inc. is the controller in respect of the processing of personal information for our own website, account, billing, security and communications purposes covered by this Privacy Policy under the EU General Data Protection Regulation and the UK GDPR, as applicable. See How to contact us above for our contact details. Where we process customer content on a customer’s instructions, the applicable data processing agreement governs our processor role; requests about that content should ordinarily be directed to the customer.
Our legal bases for processing
In respect of each of the purposes for which we use your personal information, the GDPR requires us to ensure that we have a “legal basis” for that use.
Our legal bases for processing your personal information described in this Privacy Policy are listed below.
Where we need to perform a contract, we are about to enter into or have entered into with you (“Contractual Necessity”).
Where it is necessary for our legitimate interests and your interests and fundamental rights do not override those interests (“Legitimate Interests”). More detail about the specific legitimate interests pursued in respect of each Purpose we use your personal information for is set out in the table below.
Where we need to comply with a legal or regulatory obligation (“Compliance with Law”).
Where we have your specific consent to carry out the processing for the Purpose in question (“Consent”).
We have set out below, in a table format, the legal bases we rely on in respect of the relevant Purposes for which we use your personal information - for more information on these Purposes and the data types involved, see How we use your personal information. Only the categories and purposes applicable to the product and feature are involved.
| Purpose | Categories of personal information involved | Legal basis |
|---|---|---|
| Service delivery and operations | Contact, profile, communications, transactional, user-generated content/input and device data, and linked third-party service information, as applicable | Contractual Necessity. |
| Security | Contact, device and online activity data | Compliance with Law. Legitimate Interests: ensuring the ongoing security and proper operation of our Service and associated IT services, systems, and networks. |
| Service personalization, improvement and analytics | Applicable profile, device and online activity data | Legitimate Interests: providing you with a good service, remembering your selections and preferences, and improving the Service. Consent, in respect of any optional cookies used for this purpose. |
| Direct marketing | Applicable contact, communications, transactional and marketing data | Legitimate Interests: promoting our operations and goals as an organization. Consent, in circumstances or jurisdictions where consent is required to send the communication. |
| Compliance and protection | Data relevant in the circumstances | Compliance with Law. Legitimate Interests, where Compliance with Law is not applicable: participating in and following legal process and ensuring the protection, maintenance, and enforcement of rights, property or safety. |
| Data sharing in the context of corporate events | Data relevant in the circumstances | Legitimate Interests: providing information to relevant parties involved in an actual or prospective corporate event. We look to minimize the amount and sensitivity of personal information shared where possible and appropriate. |
| To create aggregated, de-identified or anonymized data | Data relevant in the circumstances | Legitimate Interests: ensuring that our Services operate as intended. |
| Further uses | Data relevant in the circumstances | The original legal basis, if the further use is compatible with the initial purpose. Consent, if it is not compatible. |
Retention
We retain personal information for as long as necessary to fulfil the purposes for which we collected it, including for the purposes of satisfying any legal, accounting, or reporting requirements, establishing or defending legal claims, or for Compliance and protection purposes.
To determine the appropriate retention period for personal information, we consider the amount, nature, and sensitivity of the personal information, the potential risk of harm from unauthorized use or disclosure of your personal information, the purposes for which we process your personal information and whether we can achieve those purposes through other means, and the applicable legal requirements.
When we no longer require the personal information, we have collected about you, we will either delete or anonymize it or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible. If we anonymize your personal information (so that it can no longer be associated with you), we may use this information indefinitely without further notice to you.
Product-specific retention periods and deletion commitments remain applicable where stated.
Your rights
General. European data protection laws give you certain rights regarding your personal information. If you are located in Europe, you may ask us to take the following actions in relation to your personal information that we hold:
Access. Provide you with information about our processing of your personal information and give you access to your personal information.
- Correct. Update or correct inaccuracies in your personal information.
- Delete. Delete your personal information where there is no good reason for us continuing to process it - you also have the right to ask us to delete or remove your personal information where you have exercised your right to object to processing (see below).
- Transfer. Transfer a machine-readable copy of your personal information to you or a third party of your choice.
- Restrict. Restrict the processing of your personal information, for example if you want us to establish its accuracy or the reason for processing it.
- Object. Object to our processing of your personal information where we are relying on Legitimate Interests - you also have the right to object where we are processing your personal information for direct marketing purposes.
- Withdraw Consent. When we use your personal information based on your consent, you have the right to withdraw that consent at any time.
Exercising These Rights. You may submit these requests by email or mail using the details in How to contact us. We may request specific information from you to help us confirm your identity and process your request. Whether or not we are required to fulfill any request you make will depend on a number of factors (e.g., why and how we are processing your personal information), if we reject any request you may make (whether in whole or in part) we will let you know our grounds for doing so at the time, subject to any legal restrictions.
Your Right to Lodge a Complaint with your Supervisory Authority. In addition to your rights outlined above, if you are not satisfied with our response to a request you make, or how we process your personal information, you can make a complaint to the data protection regulator in your habitual place of residence.
For users in the European Economic Area, contact information for your supervisory authority is available from the European Data Protection Board. For users in the UK, the supervisory authority is the Information Commissioner’s Office.
Data Processing outside Europe
We are a U.S.-based company. Depending on the product and recipients involved, your personal information may be accessed and processed in the U.S. or other countries outside Europe. The applicable product provisions below and service provider register identify disclosed processing locations.
Where we share your personal information with third parties based outside Europe, we use a lawful transfer mechanism where required by applicable data protection law:
- Transfers to territories or recipients covered by an adequacy decision. We may transfer personal information where a relevant European Commission or UK adequacy decision covers the transfer.
- Transfers not covered by an adequacy decision. We may use specific appropriate safeguards, such as standard-form contracts approved by relevant authorities for this purpose; or, in limited circumstances, an applicable exception or derogation permitted by law.
You may contact us if you want further information on the specific mechanism used by us when transferring your personal information out of Europe. You may have the right to receive a copy of the appropriate safeguards under which your personal information is transferred by using the details in How to contact us.
Product-specific additions
The following provisions apply to the named products together with this policy. They control a conflict with a common provision for that product.
Gridheap
gridheap.com
Public pages receive the technical requests necessary for hosting, security and Adobe Fonts delivery. Correspondence contains the information you choose to send.
Gridheap Account
account.gridheap.com
Account and SMS information
These Gridheap Account provisions apply from 21 October 2026. We process your account identifiers, email, authentication and security records to provide shared sign-in. Participating services receive the identity information needed for the access you request; shared sign-in does not expose your private product content to other products.
We use your phone number, verification requests and consent records to send verification texts you request and, with your separate opt-in, security, account and billing notifications, protect your account and honor opt-outs. Mobile information and SMS opt-in consent are not shared with third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties. Messaging and infrastructure providers process only the information needed to deliver requested messages.
We retain consent records to demonstrate authorization and honor opt-outs, following the retention periods in this policy. You can withdraw notification consent in account Security. Carrier opt-out blocks all texts, including SMS codes, from this sender; use email or a passkey instead.
Verification and security email
These email-security provisions apply from 28 October 2026. Grid Heap, Inc. is the controller. Gridheap Account uses Amazon Cognito for hosted sign-in. When you request additional-email verification in Account, or complete a recent sign-in through Account settings, we use the browser and operating-system category, approximate country, partially hidden IP network and UTC time to help you recognize the activity. Browser information is reported by the device; country estimates can be affected by VPNs and mobile networks. The reminder describes the completed return to Account settings. Messages from the hosted sign-in service and other products’ independent sign-in flows may have fewer details or no reminder.
Our legal basis is legitimate interests in preventing unauthorized access and helping you detect account misuse (GDPR Article 6(1)(f)). These essential security messages contain no marketing or tracking pixel. Reminders go only to the verified primary email, with duplicate prevention and frequency limits. Delivery problems do not prevent sign-in. If you do not recognize an activity, review passwords and sessions or contact security report form.
Source information and retention
We derive this context from the existing request and Cloudflare country metadata. We request no GPS or additional location lookup and create no device fingerprint. Before passing context to the private email service, we hide the final IPv4 octet or final 80 IPv6 bits. IP networks and keyed identifiers remain personal data.
Account processes the email’s source context transiently to compose the message; it is not saved in the account profile, session store, reminder receipts or application logs. Limited records used to prevent duplicate reminders expire after seven days; delivery-limit records expire after 40 days. Expired records are no longer used and are removed asynchronously. Existing authentication and infrastructure security records have separate retention under this policy. Cloudflare necessarily receives the original connection data before Account reduces the email context.
Delivered messages remain in your mailbox until you delete them, subject to your provider’s retention. AWS and delivery providers process message content and delivery records under their service terms and retention. Transient application processing does not mean every provider copy is immediately deleted.
Providers and transfers
Cloudflare processes Account edge requests, necessary session storage and delivery coordination. Amazon Web Services processes authentication, account records and email delivery. The Account AWS services are configured in US East (N. Virginia); email delivery and Cloudflare’s global network can involve other countries. Account does not restrict Cloudflare processing to Europe. Your email provider receives delivered messages. See the Account provider register.
The applicable AWS Service Terms incorporate its data processing addendum and supplementary safeguards. Cloudflare’s service agreement incorporates its Customer Data Processing Addendum. For restricted transfers, these agreements provide standard contractual clauses, with UK and Swiss adaptations where applicable. A valid adequacy mechanism may apply to a covered transfer; otherwise the applicable contractual safeguards apply. These safeguards do not mean data stays in Europe. Contact legal contact form for information about applicable safeguards or a copy, subject to necessary redactions.
Choices and rights
Contact legal contact form for access, correction, erasure, restriction, portability where applicable, or to object to processing based on legitimate interests. We assess objections against the account-security purpose and explain any overriding grounds. You may complain to your competent data-protection authority. These rights and the response periods in the common policy apply to Account security processing as well.
RShift
rshift.com · rshift.de · accounts.rshift.com · app.rshift.com
Information and purposes
Clerk Platform is an optional authentication provider for customer applications published through RShift. When a project owner selects it, it processes that application’s end-user account, sign-in, profile and session data. RShift itself uses Gridheap Account for sign-in.
We process account and Gridheap Account sign-in identifiers, membership and permissions; workspace projects and brand knowledge; prompts, conversations, scenes, storyboards, assets, media jobs, custom skills, reviews, approvals and notifications; connected-service permissions, tokens, imported assets, reports, webhooks, comments and synchronization records; usage, security, audit and support records; and Stripe subscription and billing metadata such as status and card last four digits. We do not receive full payment-card details.
The customer controls its workspace content and instructions. Gridheap controls its own account, billing, security and business records. Authorized administrators manage workspace access and retention. AI features send relevant inputs and context to the selected model providers; authorized publishing or integrations send necessary data to the selected platform. We do not disclose one customer’s private workspace content to other customers, except as needed for delivery, security, legal requirements or further authorization.
Where enabled, PostHog receives sanitized feature-use events and permitted account/organization identifiers; Sentry receives redacted technical errors. These data can be account-linked and are distinct from aggregate marketing-site statistics. PostHog session recording is off by default. Its optional recording path requires a configured recording mode and an enabled feature flag; where activated, it can process masked interaction/session data. Sentry error reporting is separate from that path.
We do not sell personal information, use it for cross-context behavioral advertising, use sensitive information outside permitted purposes, or make solely automated decisions with legal or similarly significant effects. Processing takes place principally in the United States and the locations of applicable providers. Where required, transfers use applicable EU Standard Contractual Clauses, UK addenda or another recognized mechanism.
Retention, export and deletion
The default retention settings are:
| Record | Default retention |
|---|---|
| AI conversations | 90 days |
| Monitoring runs | 180 days |
| AI usage records | 365 days |
| Audit records | 730 days; minimum 365 days |
| Export files | 7 days |
Workspace configuration can change applicable retention. Billing, security, backup and legally required records may remain longer under the common retention criteria.
Data Governance exports use open JSON and include account and knowledge records, scenes, assets, conversations, reviews, integration configuration and analytics, excluding credentials. Workspace offboarding follows export-first-then-delete: authorized exports precede removal from the database and object storage, with confirmation of deletion. Required audit and legal records remain for their applicable periods. We use least-privilege access, encryption and audit controls. RShift accounts are for adults aged 18 or older.
TidyAnswer
tidyanswer.com
For enterprise workspaces, the customer controls its content and processing instructions; Gridheap controls account, billing and security records. Customer-provided credentials and integrations are used only within their authorized scope. A signed processing agreement governs customer-instructed processing. Channel and marketplace recipients apply only to features actually enabled, as identified in the shared service provider register.
Customer-support SMS
We use SMS opt-in data and consent only to respond to your support requests. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.
For SMS delivery, messaging and infrastructure providers process telephone numbers, SMS content and routing/delivery metadata, as identified in the provider register.
TidyMessages
tidymessages.com
The public website receives basic delivery and security request metadata. Channel workflows process account, configuration and message data to operate, secure, support and improve the requested workflow and satisfy legal requirements. Selected cloud, identity and messaging providers receive necessary data for their roles. Access and retention depend on operational need and the applicable pilot or production processing agreement.
Customer-support SMS
We use SMS opt-in data and consent only to respond to your support requests. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties.
For SMS delivery, messaging and infrastructure providers process telephone numbers, SMS content and routing/delivery metadata, as identified in the provider register.
Speech Name
speech.name
We process account identifiers, chosen profile fields, billing, API, security and support records, issuance information and audio fingerprints. Public verification uploads are held in memory for the request and discarded when it completes. Fingerprints and issuance records remain as needed for verification, billing, legal obligations and disputes. A handle URL is returned only when an issuance matches and its issuer has enabled public disclosure. Detection can report a mark without exposing a profile. Published profile fields follow your disclosure settings; detection itself does not establish identity, ownership or consent.
Planner.li
planner.li
Content and device storage
Planner.li processes account data, subscription and transaction records, notes, plans, calendar entries, expenses, contacts, journal entries, attachments and imports you choose to provide; diagnostic device/app details, crashes and performance traces; sampled feature-use events; and technical security requests. Full payment-card numbers remain with the payment provider.
Personal account synchronization and multi-user sharing have different storage paths. Where available and enabled, personal sync uses your Apple iCloud/CloudKit account. Enabled hosted sharing sends encrypted snapshots and sharing-access metadata to Cloudflare. Local agent conversation history stays on your device; we do not operate a long-lived memory service for those transcripts. Connected-service credentials use the operating system’s protected credential storage. Product analytics have person profiles disabled and do not receive email bodies, contact source text, generated content or agent transcripts. We do not sell or share information for advertising, collect precise location, use advertising identifiers or include advertising SDKs.
AI and feature lookups
AI Runtime (airuntime.dev) is an internal Gridheap gateway and provides the model service for these features. Hosted AI capabilities are limited to privacy filtering, draft translation and subscription extraction. The privacy filter replaces detected personal information with placeholders before forwarding text, with a maximum of 100 items and 64,000 characters per request. Requested feature text is processed through AI Runtime’s configured feature route. AI Runtime’s model processing is described in the AI Runtime privacy information and AI Runtime service-provider register. Content is not used to train general-purpose models by us or the engaged providers.
Optional weather lookups use the place you reference; currency-rate lookups contain no personal or transaction data. Integrations you initiate use the connected provider’s own terms. Content and account records remain for the requested service and applicable legal, security and billing needs. Local records and backups require deletion through the relevant device controls; deleting browser storage does not delete hosted records.
Keep content while your account is active. Deleting an item removes it from its synced store; backups age out on a rolling basis. App controls provide access/export, item/account deletion and optional diagnostics/usage reporting choices. Service and billing messages continue while the account is open; marketing messages offer unsubscribe. Required tax, accounting, fraud-prevention and legal records can remain after closure.
Enola
eno.la
Enola provisions updated 9 November 2026.
Data and requested features
We process account and invitation identifiers, invitation referrer and allowance records, Gridheap Account sign-in, channel-connection identifiers, and consent timestamps, channel, disclosure version, confirmation and a one-way number digest; messages and attachments; voice transcripts; explicitly saved preferences; reminders, authorized browser-task records, incoming email summaries and confirmed outgoing drafts. Conversation keys use a hashed phone number. Attachments can include photos, voice, video and PDFs up to 8 MB; audio is discarded after transcription. Technical events exclude message contents.
The taste, care, body and money memory areas start off. Preferences are saved only at your explicit request; we do not infer family roles, gender, health, body goals or budget. Reminders can be scheduled up to 30 days ahead. Browser research uses requested queries and pages; you enter passwords and payment details through secure handoff. Optional Mac microphone or other-app access requires its own permission.
The configured assistant and voice routes use internal AI Runtime, Gridheap’s model gateway. The selected route and any enabled fallback determine the external model host that receives submitted context. See the Enola service-provider register and AI Runtime privacy provisions for hosts and processing conditions. Internal Tooluse.net and TidyMessages operate requested browser and channel tasks. Messaging channels use enabled delivery providers and carriers; incoming mail uses Fastmail. Messages, saved preferences and reminders are not used for model training. We do not sell personal information, build advertising profiles or make solely automated decisions with legal or similarly significant effects. We do not read private conversations manually except with your permission or for security, abuse or legal needs.
Google Workspace connections
Connecting Google is optional. You select your own Google account and authorize its permissions. Workspace controls and Enola AI workflows use separate authorizations; AI authorization is available only when the workflow is enabled. Enola does not use domain-wide delegation. Connecting does not start a bulk import.
Gmail access lets you find and read messages, compose and send mail, and update labels. Calendar access lists existing calendars and reads, creates, updates or deletes events. Tasks access reads and manages tasks in your chosen lists. Drive access finds and organizes existing files, including files created outside Enola, and reads, creates and edits Docs, Sheets and Slides. Your instructions determine the content Enola accesses.
Google sends requested results through Enola’s authenticated backend to your workspace. For AI workflows you enable, only the task context needed to answer your request passes through AI Runtime to the configured model host. OAuth client secrets and access or refresh tokens are not included in model prompts. You review the saved action and its exact fields before Enola makes a change, sends a message or edits a file. Google receives the fields necessary for that action; approved message recipients receive the message you send. Hosting and model providers process Google data only as needed for the disclosed features, security or legal obligations, subject to the restrictions below.
Google Limited Use
Enola’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements, and the Google Workspace user data and developer policy.
Google data and data derived from it are used only for the user-facing features you request. We do not sell this data, use it for advertising or lending decisions, or use it to create, train or improve general-purpose or foundation AI models. Our providers must follow these restrictions. Human access requires your documented permission to view specific data, a security or abuse investigation, a legal obligation, or an aggregated and anonymized internal operation permitted by Google’s policy. A business transfer involving Google data requires your explicit prior consent. These Google-specific restrictions take precedence over the shared provisions on service improvement, analytics, aggregation, marketing, sharing and business transfers; those shared provisions do not authorize an additional use or transfer of Google data.
Shop connections
Connecting Shop is optional. If you connect your account, Enola requests the account information and orders needed for the actions you choose. Shop may return profile information, saved delivery addresses, orders and delivery status, and Shop Pay budget or payment-method labels. The current connection provides account and order reads; it does not place orders or initiate payments, and it does not administer merchant stores. Connecting does not start a bulk import.
Shop receives the authorization request and the fields needed to answer your selected account or order request. Results appear in your authenticated workspace. For AI workflows you request, only the task context needed for that request follows the disclosed AI Runtime route. OAuth credentials remain on Enola’s backend and are not included in model prompts. See the Enola service-provider register for the applicable recipients.
Saved authorization remains until disconnected, revoked, replaced or removed with your account. In Workspace, open Shop Pay and choose Disconnect, or revoke the connection through Shop. You can separately remove saved results with Clear imported data in Preferences. Disconnecting Enola does not delete your Shop account or orders.
Retention and deletion
| Record | Retention |
|---|---|
| Text conversation model context | Latest 12 messages / 32,000 characters; 7 days after last activity |
| Shared conversation history | Up to 100 encrypted input and reply records, each retained for 7 days; replies may contain Google-derived information |
| Shop OAuth grants | Until disconnected, replaced, revoked or removed with the account |
| Shop authorization attempts | 10 minutes |
| Saved Shop action reviews and arguments | 30 minutes |
| Saved Shop action results | Until cleared, removed with the account or discarded from bounded workspace history; conversation copies follow conversation retention above |
| Google OAuth grants | Until disconnected, replaced, revoked or removed with the account |
| Google authorization attempts | 10 minutes |
| Saved Google action reviews and arguments | 30 minutes |
| Text tasks | 7 days; pending approval expires after 24 hours |
| Processed photos and files | 24 hours |
| Audio | Discarded after transcription |
| Browser-task records | 24 hours |
| Outgoing queue and duplicate checks | 24 hours |
| Security audit | 7 days |
| Reminder | Until one day after due, cancellation or expiry |
| Received email | 30 days |
| Saved preferences, Life and web settings | Until deleted |
| Account | While open; deleted within 30 days of closure, subject to legal exceptions |
Credentials and saved task data are encrypted in transit and at rest, with access limited to the account and systems that need them. New connector replay receipts do not store raw Google response bodies. Earlier cached results are removed when the account next opens its workspace. Minimal operation identifiers and completion records prevent duplicate actions. Provider-side processing follows the disclosed service arrangements and Google’s Limited Use restrictions.
In Workspace, open Google Workspace and choose Disconnect to remove Enola’s saved Google grants. You can also revoke the project’s access through Google Account permissions. In Preferences, Clear imported data removes retained imported content, pending connector reviews and conversation history. Saved vault items and connections have separate controls. Export data downloads supported saved content without OAuth credentials. Delete account removes Enola’s saved account data and grants after you review and confirm deletion. Preferences remain only until you delete them or ask Enola to forget them. Google-side messages, events, tasks and files are managed in Google; disconnecting Enola does not delete those originals. For access, correction, deletion, account closure, privacy questions or appeals, contact legal contact form.
We record SMS and RCS consent after an explicit subscription action from the number under the disclosed messaging program. For RCS, this is START after the public RCS disclosure, or YES after the disclosure in the conversation. An invitation, account sign-in or WhatsApp connection is not SMS or RCS consent. Mobile opt-in data and consent are not sold or shared for marketing or promotion, including with affiliates. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties. Delivery providers process only the information needed to provide requested messages. Opt-in records remain while the account/number is active and are then removed; opt-out records remain as needed to honor the opt-out. To delete, text DELETE MY DATA, then CONFIRM DELETE within 10 minutes. This removes conversations, saved preferences, Life, reminders, web tasks and received emails. Delivery providers may retain their own required records. Stopping messages alone does not delete these data.
Regional rights and health information
US residents can request access, correction, deletion, portability and applicable opt-outs, use an authorized agent and appeal a denial. We normally respond within 45 days, verify through account email/phone and do not charge for ordinary requests.
EEA, UK and Swiss users normally receive a response within one month, extended to three months for complex requests with reasons. Contract supports requested features; messaging and saved preferences use consent; voluntary health information uses explicit consent; security relies on legitimate interests and required records on law. Transfers use applicable Standard Contractual Clauses with UK/Swiss amendments, or the Data Privacy Framework only for a certified recipient. Request a copy of applicable safeguards at legal contact form.
Canadian users have applicable PIPEDA and Québec Law 25 access, correction and consent-withdrawal rights and may contact the relevant commissioner or Commission d’accès à l’information. Mexican users have ARCO access, rectification, cancellation and opposition rights, and can revoke consent or limit use. Singapore users have PDPA access, correction and withdrawal rights, can contact our privacy contact at legal contact form or the PDPC, and receive applicable comparable-transfer protections.
Under applicable consumer-health laws, including Washington’s My Health My Data Act, voluntarily provided health information is used only for your requested service, not sold or used for advertising, and can be deleted. Contact legal contact form to exercise these rights. Conversation, preference, reminder, email and browser-task data are encrypted in transit and at rest, with access limited to operational need.
Dueglow
dueglow.com
Scope and local storage
These Dueglow provisions apply from 1 November 2026. They cover the Dueglow apps for iPhone, iPad, Mac and Android and the dueglow.com website; read them with the common Privacy Policy above. Dueglow is local-first: your countdowns stay on your device unless you turn on sync or use a feature that needs the internet. Not every feature is offered on every platform, so each provision says where it applies.
Your countdowns, milestones, covers, reminders, preferences and Places journal (the places you save, with check-in dates and notes) are kept in the app’s private storage on your device. You don’t need an account to use Dueglow. Reminders are scheduled on your device as local notifications, and widgets and Live Activities show the same on-device data. The app can use only the photos you choose with the system photo picker, or take with the camera on iPhone and iPad, never your whole photo library. On Android, Dueglow’s data is excluded from Android cloud backup and device-to-device transfer, so use export or Dueglow Sync to move your library to a new phone. When you export or share something, it goes wherever you send it.
Sync and Gridheap Account
Sync is optional and stays off until you turn it on. With iCloud sync, available on Apple devices, your library is stored in the private database of your iCloud account, which Apple operates under its own terms and privacy policy; it doesn’t pass through Dueglow’s servers. With Dueglow Sync, available on Apple devices and Android, you sign in with a Gridheap Account and we keep a copy of your library on Dueglow’s service so your devices can share it. Both sync your countdowns and milestones, covers including photo data, settings such as reminder rules and display preferences, and your Places journal: each place’s name and coordinates, whether you’ve visited it or want to go, and your check-in dates and notes. Dueglow Sync also stores deletion records, sync times and, for each device you connect, a random device identifier, its platform and a device name (on a Mac, the computer’s name). Travel plans stay on your device.
Dueglow Sync and the assistant use Gridheap Account, the account shared across Gridheap apps, which runs on Amazon Cognito from Amazon Web Services in the United States. You sign in on Gridheap’s account page, and Dueglow receives your account identifier, your email address and, if your account has one, your name. The app keeps your session in secure storage on the device (the Keychain on Apple devices, and an encrypted store excluded from backups on Android) and sends a sign-in token with each sync or assistant request so our service can confirm it’s you. Signing out removes the session from that device.
Places and location
Places is your journal of where you’ve been and where you want to go. When you save a place, check in or give a countdown a location, Dueglow stores the place’s name, city, country and coordinates, along with your check-in dates and notes. That is the place you chose, not a record of where your device was. The Android app doesn’t request location permission: its places, check-ins and countdown locations come only from what you choose and enter.
On iPhone, iPad and Mac, location access is optional. If you allow it, Dueglow uses your location to show where you are on the Places map. Visit suggestions are a separate opt-in. They work only if you turn them on and allow location access in the background. Your device then notices significant visits, and Dueglow compares them, on the device, with places you’ve saved. A match becomes a suggestion (the saved place and the time of the visit) that stays on that device. Nothing is added to your journal or synced until you confirm it as a check-in. Dueglow doesn’t store the location your device reports or send it to us. You can turn visit suggestions off, or change location access in your device settings, at any time.
Online lookups and third-party content
Some features look things up online: searching for a place or a cover photo, opening a place’s travel information, and loading Explore series such as conference deadlines, ski season and holidays. The app sends these requests to Dueglow’s service with only what’s needed to answer them, such as your search text, your language, and the country, region or year you pick. They don’t need an account and don’t include your countdowns, notes or check-ins. Our service gets results from third-party sources such as map services, encyclopedias and photo libraries, including Unsplash for cover photos. When you choose a cover photo, we let its source know it was downloaded, for attribution. Photos, videos and map tiles can load straight from those sources and from map providers (Apple Maps on Apple devices, OpenFreeMap on Android), which receive your IP address and what you’re viewing. Results may be saved on your device so the app doesn’t have to ask again. Links you open, such as official sites and directions, go to other services with their own privacy policies.
AI assistant
The assistant helps you create countdowns from a description. It’s available only in the iPhone, iPad and Mac apps, requires a Gridheap Account, and asks for your explicit permission in the app before anything is sent. When you use it, the app sends your message, the recent conversation, your language, time zone and current time, and details of the countdown you’re working on (its title, link, milestones and their dates) to Dueglow’s service, which uses DeepSeek V4.1 Flash through our AI Runtime platform, with requests processed by DeepSeek or DeepInfra, to generate replies. Don’t include anything you don’t want processed this way. The Android app doesn’t include the assistant.
Dueglow’s service and AI Runtime process assistant prompts and model responses transiently and never save them. Countdown details you choose to save are then governed by the local storage and sync provisions above. This does not promise zero retention by every external provider. DeepInfra’s terms provide for deleting model inputs and outputs after processing, with exceptions for authorized support, legal and security needs, and features with separate retention. DeepSeek’s API documentation describes automatic disk caching of request context, normally cleared within hours to days after it is no longer used; that is not a fixed deletion deadline for all provider records.
Purchases, analytics and sharing
Dueglow is a one-time purchase on the App Store and Google Play, with no in-app purchases, subscriptions or ads. Apple and Google handle payment under their own terms and privacy policies. The store releases of Dueglow don’t include crash reporting or analytics, and the dueglow.com website doesn’t set advertising or analytics cookies, save optional data in your browser or request Adobe Fonts. We don’t sell your information, track you across other companies’ apps or websites, or build advertising profiles. If you’ve allowed it in your device settings, Apple or Google may share crash reports and usage statistics with us under their own privacy policies.
We use information only to provide the features you choose (storing and syncing your library, signing you in, and answering lookups and assistant requests), to answer support requests, and to keep Dueglow secure and reliable. Service providers process information on our behalf: Amazon Web Services for Gridheap Account sign-in, our hosting and database providers for Dueglow’s service, and AI model providers for assistant requests. Our hosting provider also receives standard request information, such as your IP address, to deliver the dueglow.com website. Standard technical records on our service may include IP addresses, request times, the addresses requested, app version, platform and errors. Requests to our service use HTTPS.
Deletion and retention
To delete data on a device, delete countdowns and places in the app; on iPhone, iPad and Android, deleting the app also removes its data from that device. To delete your Dueglow Sync data, sign in, open Settings → Sync (Account & Sync on Mac) and choose Delete cloud data. This permanently deletes your Dueglow cloud sync data and registered devices; the events on your device and your Gridheap Account remain. You can then manage or permanently delete your Gridheap Account, which is shared across Gridheap apps, at account.gridheap.com/settings. Data synced with iCloud stays in your iCloud account, where you can manage or delete it in your Apple Account’s iCloud storage settings.
To ask us to delete your Dueglow Sync data and account information without the app, use legal contact form with the subject “Dueglow data deletion” from the email address on your Gridheap Account. Never send your password or a verification code. We may need to confirm that you control the account. These instructions are available without installing or signing in to the app.
Information on your devices stays until you delete it, and data synced with iCloud stays in your iCloud account until you remove it. We keep your Dueglow Sync data while you use Dueglow Sync, until you choose Delete cloud data or ask us to delete it. Records needed for security, fraud prevention, legal obligations or disputes, and restricted backups, may be kept for those purposes and deleted on their regular cycles.
Choices and contact
You can use Dueglow without an account, keep sync off, turn off visit suggestions, and change location, photo, camera and notification access in your device settings at any time. You can also export your library from the app. Dueglow isn’t directed to children under 13, and we don’t knowingly collect personal information from children under 13.
For Dueglow questions and support, use contact form. For privacy requests, including the rights described above, use legal contact form; we may need to verify that a request comes from you. Send security reports to security report form.
Tooluse.net
tooluse.net
We process workflow definitions, connection tokens and authorized browser sessions; integration inputs/outputs; purchase requests, shipping and approval details, order and transaction records; account identifiers, correspondence and technical requests. Selected merchants receive what is necessary for the approved transaction and act under their own policies. Identity, hosting, payment and selected browser/research recipients are identified in the shared register. Internal Gridheap platforms have internal operational roles. We do not sell or share personal information for targeted advertising, use advertising profiles, cross-site analytics or session replay. Revoke connections through product/provider controls. Transaction, refund, security and legal records remain as needed under the common retention criteria; a signed processing agreement governs customer-instructed data.
Agentic.Pay
agentic.pay
We process workflow definitions, connection tokens and authorized browser sessions; integration inputs/outputs; purchase requests, shipping and approval details, order and transaction records; account identifiers, correspondence and technical requests. Selected merchants receive what is necessary for the approved transaction and act under their own policies. Identity, hosting, payment and selected browser/research recipients are identified in the shared register. Internal Gridheap platforms have internal operational roles. We do not sell or share personal information for targeted advertising, use advertising profiles, cross-site analytics or session replay. Revoke connections through product/provider controls. Transaction, refund, security and legal records remain as needed under the common retention criteria; a signed processing agreement governs customer-instructed data.
Bots
bots.pay · accounts.bots.pay · app.bots.pay
Bots privacy provisions updated 10 November 2026.
We process account, billing, credit holds and usage records; conversations, repository code, private files and workspaces, GitHub commits/issues/PR context; tool inputs/outputs, deployment logs and technical security records. MCP tokens are hashed and turn credentials are scoped. Private file links are signed and time-limited; provider keys are not exposed to agent containers.
When you connect a chat channel, we process the channel address (for example a WhatsApp or phone number or email address), the messages people send to your Bot and the Bot’s replies, the senders’ phone numbers, addresses, display names and message metadata, and delivery status. Deployments include the software and data a Bot deploys to machines we operate and the traffic and logs they produce. For voice input, usage records hold an operation identifier, the hold placed for it, the seconds of audio and number of model tokens our providers report, and the amount charged; these records do not contain your audio or the text you dictated. To turn voice input into text, your recording is sent through AI Runtime to Alibaba Cloud Model Studio in mainland China (Beijing) for speech recognition with Qwen Audio; only if that fails is it sent to Meta’s Model API instead. The resulting transcript is cleaned up by the model provider listed for Bots. These providers process the audio under their own API terms, and Gridheap has no zero-data-retention agreement with them. Messages sent through our contact page are delivered by email to our support mailbox through Gridheap’s email service; the Service does not keep its own copy, and its logs record only that a message was sent and its topic.
Model inference, tool execution, messaging and hosting use the services listed in our service providers and subprocessors register, which explains each recipient, purpose and the data processed. Gridheap does not train on content; third-party improvement rules depend on the applicable service provider’s terms and settings.
Bot compute and snapshots are hosted in Frankfurt, Germany. Other recipients and features can process elsewhere; this is not a promise that all data remain in that region. Content persists while the bot exists. Deleting a file or bot removes runtime content and applicable snapshots, subject to backup and legal retention. Temporary turn files and containers are removed at turn end. Billing/tax records remain as legally required. Account data is kept while your account is open and for a reasonable period afterwards to handle refunds, disputes and legal obligations. Channel conversations are kept as part of the Bot’s conversation history while the Bot exists and the channel is connected. Usage, holds and billing records are kept as accounting records for as long as we need them for billing, tax, audit, fraud prevention and legal claims. Server and security logs are kept for a limited period by our hosting and security providers.
Public-site analytics on bots.pay are aggregate and cookie-free: paths without query strings, coarse country, campaign/referrer domain and, where enabled, labeled clicks and scroll events, with no stored IP address or persistent visitor identifier. Where Privacy settings permit optional analytics, the home and contact pages also send one page-view event to PostHog US Cloud through our API, containing only a page category, the product name and random identifiers created for that document; Global Privacy Control blocks it. Account, agent and billing records remain identifiable. We do not sell/share personal information for targeted advertising, and the optional RShift consent-based session-analytics mode is not used for Bots.
In the last 12 months we have collected, for Bots: identifiers (such as name, email address, account identifiers and IP address); commercial information (purchases, balance and usage); internet or other electronic network activity (log data, website analytics, and Apple Music Bot listening events and diagnostics); approximate geolocation (country derived from IP address); audio, electronic or similar information that you choose to include in Bot content and conversations; and account log-in credentials, which are handled by our authentication provider (previously Clerk, now Amazon Cognito through Gridheap Account). We use account log-in credentials only to authenticate you and keep your account secure, and we do not use or disclose sensitive personal information to infer characteristics about you. We do not knowingly sell or share the personal information of consumers under 16. Where the Swiss Federal Act on Data Protection applies to our processing for Bots, Grid Heap, Inc. is the controller, except for data we process for our customers, and you have the rights described in the Notice to European users; use legal contact form to exercise them.
Accessibility pricing
If you apply for accessibility pricing on our contact page, we receive your name, the email address you want replies at, your Bots account email, your two confirmations and any short note you add. The application reaches our support mailbox by email; we use it only to decide it and delete it once it is decided. If we approve it, we keep that your account is enrolled, when we approved it, which version of the application you agreed to, when the enrollment expires, and whether we have paused it. We do not ask for or record what your condition is, and we do not accept documents about it. Bonus credit granted while you were enrolled is recorded with your other billing records.
An application, and the fact that you are enrolled, may indicate that you have a disability, injury or condition. We process them only with your explicit consent, which you give separately in the application, and you can withdraw it at any time through our contact page or by turning accessibility pricing off, which deletes the enrollment record. The resulting billing records are kept under contract and legal obligation. We do not use your enrollment for advertising, analytics or profiling, we do not include it in logs or telemetry, and we do not share it with anyone, including our payment processors. An enrollment is kept until you turn it off, we end it, or you close your account; an expired enrollment remains only so that an approved renewal can continue it.
Apple Music Bot
Apple Music Bot at app.bots.pay/music connects to Apple Music through Apple’s own sign-in. We never receive your Apple ID or password, and Apple’s access token for your account stays in your browser. Your Apple Music listening history and library are read in your browser; song titles and your Apple history are not sent to us. We receive: Apple catalog identifiers of the songs and artists used as starting points, without your account identifier, to look up which music people play together; the request you type and, if you turn on “Include my top genres and artists”, up to five genres and five artist names, which go to our model provider to interpret the request and are not stored; and, unless you turn off listening sync, a listening log of Apple catalog identifiers with what happened to each recommended song (shown, played, skipped, finished, liked or saved), how long it played, its position in the mix, why it was recommended, and the hour and weekday, stored under a pseudonymous key derived from your account. We use these to provide recommendations and keep them in sync across your devices (contract). The synced log is kept for 180 days and at most 20,000 events per listener. Turning off listening sync keeps the log on your device only; Forget my listening deletes it from your device and our servers.
Analytics and diagnostics are optional in every region and are sent only after you allow them (consent). If you allow them, PostHog US Cloud receives the listening events above and playback diagnostics: error codes and how the player recovered, timings such as how long a song took to start, app and player versions, browser family and operating system, and the type of any unexpected error with web addresses and identifiers removed. They are sent under a pseudonymous identifier derived from your account, which PostHog cannot link to your name or email address, and exclude song titles, IP addresses and IP-derived location. No cookies are set for them. We keep them only as long as we need them to measure and improve recommendations and playback. You can withdraw consent at any time under Privacy settings on the Apple Music Bot page, and Global Privacy Control turns these analytics off for that browser. To delete analytics already sent, contact legal contact form.
SMS opt-in data and consent are not shared with third parties or affiliates for marketing or promotion. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties. Delivery providers process only the information needed to deliver requested messages.
AI Evals
aievals.app
AIEvals processes basic delivery/security requests, optional correspondence and Adobe Fonts requests. It has no visitor accounts, checkout or hosted evaluation/model runtime. It does not buy visitor profiles or request government identifiers, biometrics or precise location. Search/filter selections in a URL can be sent to the server or revealed when shared; do not put confidential information in them. We do not sell/share information for advertising, use targeted-ad profiles, cross-site analytics or session replay. Technical and correspondence records remain as needed under common retention criteria.
AI Agent Pay
aiagent.pay
We process shopping requests, merchant and item choices, budgets, shipping/location information you provide, approvals, history and order records, account identifiers, authorized integration inputs/outputs and technical requests. Enola prepares requests; the execution service acts only within approval. Secure checkout sends payment credentials to the payment provider, not full card details to Gridheap. Merchants process necessary purchase data under their own policies. We do not sell/share information for targeted advertising or build advertising profiles. Transaction, refund, security and required legal records remain as needed. Revoke connected access through product/provider controls and exercise privacy rights through legal contact form.
4dub
4dub.com · accounts.4dub.com
Data, AI and analytics
We process account identifiers and chosen Google, Microsoft, Apple or email sign-in; upload video, transcripts, edits, languages, speakers, voice/timing choices, rewrites and generated media; receipt and payment-status records; support and operational records. Full card details remain with the merchant of record. We do not ordinarily request age, government identifiers or precise location.
Microsoft Speech performs transcription, translation and stock-voice synthesis. Rewrite text uses Microsoft models through internal AI Runtime. Provider arrangements exclude content training or improvement. Videos and generated media are private to the account; 4dub has no public profile or sharing-link feature.
Cookie-free events include page visits/leaves with private URL details removed, homepage video plays, account creation, upload size/duration, language, queue/rewrites and checkout amounts. Signed-in events can be account-linked; signed-out events use an ephemeral identifier until reload or closure. They exclude email, media contents and private media URLs. PostHog provides these production event analytics with memory-only persistence. Sentry error records strip private links and may contain account IDs/timing. No session replay or email open/tracking pixels are used. Cookieless processing does not mean anonymous processing.
Google sign-in — Limited Use
Google access is limited to openid, email and profile. We do not request Gmail, Drive, YouTube, Contacts, Calendar or other Google data and do not obtain video or generated content through Google APIs. Google account data is used only to provide sign-in and the Service, with necessary contracted authentication, hosting, database and email providers or lawful disclosure. It is not sold, used for advertising or used to train or improve general-purpose AI models.
4dub’s use and transfer of information received from Google APIs adhere to the Google API Services User Data Policy, including the Limited Use requirements. Revoke access through Google’s connected-app controls or remove 4dub; account deletion also removes associated Google account data.
Retention, export and deletion
| Record | Retention / deletion |
|---|---|
| Project media, including provider processing copies | Until project/account deletion; removed within minutes after deletion |
| Inactive projects/media | 12 months without sign-in, following a 30-day email warning |
| Email and signup IP on account deletion | Erased at once; authentication account removed |
| Transaction/accounting records | Generally seven years; checkout email removed on account deletion |
| Support/email records | Removed on account deletion |
| Free-trial abuse check | A one-way email fingerprint can remain after deletion |
| Daily usage counters | 14 days |
| Daily database backups | 30 days; no video/audio backups; deleted records age out |
| Security logs, errors and events | As needed for the purpose, then aggregated or deleted |
Account export provides download links for media, dubs and subtitles. Project/account controls delete their data; account deletion forfeits credit subject to mandatory rights. Access uses private, short-lived signed links, encrypted storage/database and no provider keys in the browser.
Media are stored privately on Cloudflare R2; account/project metadata and service email use the documented AWS infrastructure. Microsoft Speech selects an available US or West Europe resource; Azure GlobalStandard text rewrites do not create a single-region processing promise. Cloudflare also provides global edge delivery. Contract supports requested features; legitimate interests support security, trial-abuse prevention and cookie-free analytics; legal obligations support required records. We do not sell or share data for targeted advertising, infer sensitive traits, use voiceprints to identify people or make solely automated legally significant decisions.
US statutory categories — preceding 12 months
| Information | Category | Purpose / recipients |
|---|---|---|
| Account identifiers | Identifiers | Sign-in/service; identity, hosting and email providers |
| Project media | Audio/visual information | Requested dubbing; storage and speech/model providers |
| Transactions | Commercial information | Billing/accounting; merchant of record and necessary infrastructure |
| Correspondence | Identifiers and communications | Support; email/infrastructure providers |
| Technical requests | Internet/network activity and IP identifiers | Delivery/security; hosting/CDN and font providers |
None of these categories is sold or shared for cross-context behavioral advertising. Apply the common state-rights and European-rights sections together with these practices.
AIRuntime
airuntime.dev
AI Runtime privacy provisions updated 9 November 2026.
AI model service
AI Runtime (airuntime.dev) provides model processing for other Gridheap products, including Planner.li, nnu.us and Cowork Town. Product-specific model API addresses relay requests to AI Runtime in memory. The requested feature determines the content and instructions processed. AI Runtime is operated by Grid Heap, Inc.; it is an internal service of the same legal entity, and it runs on Amazon Web Services in US East (N. Virginia). External model hosts receive the request content needed for the selected route. See the AI Runtime service-provider register for model hosts and route-specific conditions, including applicable fallback routes. Customer-selected runtimes or provider credentials follow the route configured by the customer.
Payloads, credentials and customer planes
AI Runtime does not write prompts, completions, images, audio, files or embedding inputs to disk, a database, logs or analytics. Content exists in memory only while the request is processed and passes through the selected route to the approved execution provider; it is not retained in the central usage ledger. There are three exceptions, each chosen by the endpoint the caller uses: asynchronous deployment jobs and batches store their input and output encrypted (AES-256-GCM) for a retention the caller chooses, 60 to 900 seconds, and the input is erased as soon as a GPU picks the job up; OCR results are held in memory for at most 20 minutes, keyed by a hash of the document, and are never written to disk; and the Batch API (/v1/files and /v1/batches) stores batch input encrypted (AES-256-GCM) only until the model provider accepts the batch (an upload no batch uses is erased after 24 hours) and results until 60 minutes after their first download, never longer than 7 days after the batch ends, and deletes the provider’s copy of the files once results are collected. AI Runtime keeps no prompt cache; prompt caching is performed by providers. Content is not used to train or evaluate models, and no person reviews it.
Requests are rebuilt field by field before they are forwarded: client user, metadata and safety_identifier fields are not forwarded, and no customer, account or key identifiers are sent, so providers see AI Runtime as the customer. Requests asking a provider to store content (store: true) are rejected. Providers process requests under their own API data terms, and some keep data for a limited time for abuse monitoring; Gridheap has no zero-data-retention agreement with any provider. DeepSeek, Moonshot AI, Alibaba Cloud Bailian (Beijing), ByteDance Volcengine Ark and Zhipu AI process requests in mainland China when a route uses their own API; open models served by Fireworks AI or DeepInfra are processed in the United States.
Provider credentials are held through server-side secret references and can be rotated or revoked without exposing them to product clients. API keys are stored only as SHA-256 digests. The selected customer plane stores workspace configuration; the active route and Home-cloud placement determine the external recipients.
Payload-free usage evidence includes the request identifier, timestamps, model and route, units, latency, price basis and charges, status or error code, the provider used and a one-way SHA-256 request fingerprint used for idempotency and disputes; no IP address or user agent is stored with requests. Its retention window follows the applicable signed agreement and reconciliation needs; billing ledger rows are append-only financial records. Application logs carry identifiers, codes and timings only and are kept for 7 days (GPU service logs for at most 14 days). Organization administrators can export configuration and payload-free usage evidence without secrets or request content. Workspace-specific deletion revokes access and keys, erases stored credentials and scrubs mutable customer runtime records while preserving the minimum immutable deletion receipt and billing-reconciliation evidence; database backups are kept for 7 days. These ledger restrictions do not promise that a selected model provider has the same retention policy.
nnu.us
nnu.us
Library content, AI and sharing
We process sign-in and account identifiers; saved source URLs, titles, aliases, notes, extracted Markdown, transcripts, OCR, summaries, translations, topics and collections; reading and starred states; Recipes, Watches, Findings, provenance and sharing options; scoped API/MCP access; and billing, security and support records. Requested extraction, OCR, transcription, translation, search and change analysis send the relevant source, text and instructions through AI Runtime (airuntime.dev), Gridheap’s internal model service. AI Runtime’s model processing is described in the AI Runtime privacy information and AI Runtime service-provider register. Fetching or watching an external source discloses request metadata and the requested URL to that source.
Saved Items are private by default. A public Profile does not make the Library public. Share Grant recipients can receive the selected reader view, extracted text, summary, provenance or redirect. Passwords restrict access but do not provide end-to-end encryption. Revocation prevents future authorized access through nnu.us and cannot retrieve prior copies or onward disclosures. Legacy public short links and explicitly published content may be collected or indexed by others.
Library telemetry uses a pseudonymous Space key, coarse counts and timing. It excludes source URLs, titles, search queries, private Markdown, contact details, account/resource identifiers, passwords and bearer tokens. This does not make account, security or billing records anonymous. We do not sell information or use it for interest-based or cross-context behavioral advertising.
Retention and account closure
Saved metadata and text remain until you delete an Item or close the account; refreshing a source does not impose a short expiration on retained knowledge. Temporary source binaries are discarded after bounded conversion rather than kept as Library Artifacts. Deletion removes authoritative metadata, then saved text and search copies in the background; short-lived deletion records prevent delayed work from recreating deleted data.
Closure immediately blocks Library use, then removes account data, text, search copies and caches, ends the Stripe subscription and removes nnu.us account access. Shared Gridheap Account access to other products is managed separately. Encrypted recovery backups remain for no more than 35 days. A one-way account-identifier hash and closure time remain for 42 days to prevent an older backup from restoring a closed account; this record contains no email or Library content. A minimal pseudonymous transaction projection may remain for up to seven years for tax, accounting, chargebacks, fraud prevention and legal obligations. Legal holds or applicable law may require longer retention. Operational and audit records are bounded to their documented purpose and avoid retaining source bodies where an identifier suffices.
TrainShell
train.sh
TrainShell processes account and sign-in identifiers, host and instance information, authorized OAuth scopes and repository/storage metadata, SSH keys and provider credentials, recipes and jobs, terminal command input/output, file transfers, logs, artifacts and support records. Connected-host telemetry includes host name, operating system, hardware, heartbeat and connection/session identifiers.
Gridheap controls account, security and billing records. Customer instructions govern customer-controlled files, prompts, code, datasets, secrets and terminal content, subject to necessary security, compliance and billing processing. Selected providers receive the content necessary for the workflow you enable; their own retention and service terms also apply. We do not intentionally train our own foundation models on User Content, sell it, or use it for cross-context advertising. This is not a blanket no-training guarantee for independent providers.
Account data remains while active and for a reasonable period afterward for the common retention purposes. Credentials remain until revoked, replaced, deleted or no longer needed. Host, session, job and transfer records follow operational and security needs, with bounded backup remnants. You can disconnect providers and revoke or delete saved secrets. Limited aggregate public-site analytics exclude terminal content, files, secrets and model prompts.
heap.page
heap.page
We process account and sign-in identifiers, followed Heaps, delivery choices, saved progress, corrections, Agent credential labels, subscription and payment records, support correspondence and technical security metadata. Selected delivery providers receive the information needed to send the notifications you request; Stripe retains full card details.
Product measurement is cookie-free and limited to route, event, status and hourly aggregates. Its event payloads exclude names, emails, account subjects, cookies, raw IP addresses, full request URLs, private text, credentials, payment details and source bodies. Delivery and security processing can still receive network metadata. Account/content records follow the common purpose and legal retention criteria. You can revoke Agent access, unfollow sources, unsubscribe from messages and cancel Premium; browser preference deletion and hosted account deletion are separate controls.
Outseek
outseek.xyz
Career features process the résumé title and text you choose to paste or import, the selected job title and description, sign-in identifiers, consent and request records, and private matching or polishing results. Editing and importing keep the draft in the current page’s memory; résumé content is not written to browser local or session storage. Signed-in users can choose to save, read and delete résumé versions in their private account workspace. Saved résumés and private analysis results are not included in public job listings or sent to employers by Outseek. Deleting the cloud résumé removes saved versions and cached analysis outputs from the active application store. Minimal identity, consent, request-digest, rate-limit and security records may remain under the common retention criteria; infrastructure backups and external-provider records follow their applicable retention arrangements.
AI matching and polishing require confirmation of the processing notice shown in the workspace. Bounded résumé text and the selected job title and description pass through internal AI Runtime to the configured model infrastructure. Matching attempts to remove recognizable email addresses, telephone numbers and web links before forwarding; this automated filtering does not guarantee removal of every identifier. Polishing uses the submitted text, which may include contact details. Omit contact or sensitive information that is unnecessary for the requested review. AI Runtime’s model processing is described in the AI Runtime privacy information and AI Runtime service-provider register. Validated results are cached privately for the same account’s repeated request. A comparison labeled as rule matching makes no model request.
Public career listings contain company and job information from configured employer or third-party sources and can be copied or indexed. Source, change and deduplication evidence can be retained privately for correction and audits. Application links open the declared employer or application-service destination; that destination receives ordinary connection information and any application data you submit there under its own privacy terms. A general company careers link does not identify an exact vacancy. These public listing records are separate from users’ private résumé records.
The following software-directory and campaign descriptions concern records from the former software service and their continuing retention or processing, rather than currently offered features.
We process account and contact identifiers, communications, follow/offer preferences, needs and product submissions, ownership/DNS evidence, merchant-risk records, paid listing and campaign content, transaction and reconciliation references, page/product interactions, request metadata and purpose-limited browser, audience and conversion identifiers. Public-source collection through Bright Data includes public text, handles, product names, source links, timestamps, ranks and engagement evidence; it does not bypass private or access-controlled boundaries.
Requested AI features send bounded software requirements, product fields, public source text or translations through internal AI Runtime to the configured model infrastructure; full payment-card details are excluded. Public needs, source evidence, product and sponsored content and public identifiers can be copied or indexed. When you consent to an introduction and the verified owner accepts, your verified email can be released as disclosed in that flow. Campaign purchase alone does not disclose recipient identities or lists.
Audience-presence storage excludes raw IP addresses, user-agent strings and page URLs. Optional conversion references are encrypted/purpose-limited and honor Global Privacy Control. We use no advertising network, Google Analytics or session replay and do not sell or share information for cross-context advertising. Requested offer emails can be unsubscribed from. Public artifacts may be retained privately for provenance, deduplication, correction and source audits; payment, consent, ownership, security and audit records remain for their operational or legal purpose. The browser-specific durations below also apply.
Embeddings
embeddings.app
The requested embedding input goes through internal AI Runtime to the selected enabled provider. Successful vectors and one-way input digests are persistently cached for reuse; raw embedding request text is not included in the usage ledger. Original uploaded files are stored privately in Cloudflare R2. PostgreSQL stores extracted passages, source metadata, vectors, processing jobs and billing records. Cloudflare Vectorize holds supported-dimension vector indexes in isolated workspace/model namespaces; other supported dimensions use PostgreSQL retrieval. The ledger keeps workspace identifiers, balances, key digests, payment references, byte counts and status. Gridheap Account handles website sign-in through Amazon Cognito; the application maintains its own necessary session records. New API keys are shown once and stored as digests.
Cached vectors remain while their model contract is supported. Private documents, indexed chunks and workspace records remain while the account is active or needed for the agreed service. Verified deletion or account closure removes applicable documents, indexes and cached entries, subject to accounting, security and legal retention. Shared cache entries may require isolation or invalidation. Backups follow their lifecycle and are not used for ordinary active processing. No external-provider no-training or fixed retention guarantee follows merely from these cache rules. We do not sell/share information for targeted advertising or operate visitor session replay or cross-site advertising analytics.
Markov Now
markov.now
Contact submissions include the name, email, topic, message, page URL and request identifier you supply. Alerts store your email, selected event/source and probability-change threshold to deliver the notification you request. Infrastructure and Adobe Fonts receive ordinary connection metadata. Public event titles used for translation are separate from private contact and alert data. You can unsubscribe from alerts or exercise deletion rights through the common legal contact. Retention follows the common purpose, security and legal criteria; there is no product-wide fixed retention promise.
Serialize
serialize.dev
Serialize provides browser-based data conversion, encoding, decoding and inspection tools. Tool inputs, opened local files and results are processed in the browser; the application does not automatically upload them, publish them, place them in a share URL or save them to a server-side history. Explicit network tools, including HTTP Request and DNS over HTTPS, send the requests the user runs to the selected destination or resolver. Application assets and Adobe Fonts are downloaded over the network, and hosting and external providers receive ordinary request metadata.
Where enabled, selected public tool pages display Google AdSense advertising. Google and its partners may receive device, connection and advertising information and use cookies or similar technologies, subject to the choices and disclosures presented for the visitor’s region. Serialize provides a browser-local preference to prevent its advertising requests on subsequent page loads; this preference does not withdraw consent previously given to a third-party consent platform or erase existing third-party cookies. Applicable Google privacy choices are provided through the configured consent message. For advertising-related information, see Google’s explanation of how it uses information from sites or apps that use its services at https://policies.google.com/technologies/partner-sites.
The separately accessible legacy Inspector stores saved Recipes and named schema profiles in local browser storage. Its external dataset, network and model operations contact the selected source or provider. These features are separate from the public tool directory. Users should review a legacy share link before sharing it because operation arguments may be included. Privacy and data-rights requests may be sent to legal contact form.
Cowork Town
cowork.town
Cowork Town processes Gridheap Account identity and organization membership, connected-device identifiers and capabilities, heartbeat/performance metadata, projects and task state, messages, tool/file-change events, thread history pages, control commands, approvals and notifications. These records are scoped to the organization; authorized teammates can see its shared projects and conversations. Sample exploration does not grant access to a live organization.
Opening connected thread history can request a bounded page from its device and cache that page server-side; managed thread messages are also stored server-side. Saved projects and messages can remain available while a connector is offline. Hosted model features use AI Runtime (airuntime.dev), Gridheap’s internal model service. AI Runtime’s model processing is described in the AI Runtime privacy information and AI Runtime service-provider register. Tasks you authorize on a connected device also use its selected runtime and providers. Retention follows the requested service and the common operational, security and legal criteria. Disconnecting a device is separate from deleting saved organization records.
SMS opt-in data and consent are not shared with third parties or affiliates for marketing or promotion. All the above categories exclude text messaging originator opt-in data and consent; this information won’t be shared with any third parties. Delivery providers process only the information needed to deliver requested messages.
Coffee.ms
coffee.ms
Coffee ordering privacy
AI Runtime and DeepSeek process your coffee request to understand your drink, pickup area, options and budget. The request does not authorize an order. Request drafts are retained for up to 24 hours. We use your location only for your current pickup search. Opening the ordering page loads Apple Maps when configured. We send place searches you submit to Apple. Moving the map does not search the coffee provider.
If you sign in, Google confirms your account identity. Your browser tab may retain the selected pickup location and coffee draft for up to 15 minutes so you can resume after Google sign-in, and removes them when you return. Google sign-in can stay active in this browser for up to 400 days. Guest orders are tied to the browser’s secure session.
Provider tokens are stored on the server and are never sent to chat. Order and payment records are retained for up to 90 days. When the coffee shop supports card payment, Stripe processes it on its own checkout page.
Coffee.ms uses necessary session cookies. If you choose to remember a coffee, its name and options stay on this device until you forget it. Price, account tokens and pickup location are excluded from that saved preference. Eligible visitors may receive Proxima Nova through Adobe Fonts, which receives connection information when the font loads. Other visitors use locally served Figtree, which is also the fallback if Adobe is unavailable. Coffee.ms does not enable analytics or advertising.
Read the Coffee.ms cookie disclosure or service provider list.