Skip to content
AppDues
Log in
Contact salesSign up

Archived Privacy Policy: What the December 2025 Version Covered

This page explains an archived privacy policy that was effective from December 2025 until it was superseded in June 2026.

It is a historical reference only, not the current policy. Use it to understand the categories of data, purposes, sharing, storage, security, retention and individual rights described during that period, and check the current policy for present terms.

Data collected directly and from others

Information supplied directly could include contact details, account credentials, financial and card information, banking details where access was provided for depositing or redirecting funds, personal description and photograph, and employment history sent with a CV or general inquiry. Technical and visit data could include IP address, login and browser details, time zone, operating system and platform, URLs, clickstream, page response times, download errors, interaction and scrolling or click behaviour, and customer-service contact details. IP-derived location was also described. Data received from other sources included use of other operated sites or apps and third parties such as a lead-scoring provider.

End-user data handled for developer customers

For developer customers, end-user data was divided into three groups. Technical information covered device type and operating system. Transaction information covered last-seen time, an Apple receipt file and a Google purchase token. Optional information, only if the customer selected or enabled it, covered the end user's ID in the customer's app or product and additional attribution or metadata. Together these were called End User Information, and the archived policy said it would be used only to provide services under the signed agreement.

Cookies, tracking and Do Not Track

Cookies and similar technologies, including device IDs, in-app codes, pixel tags and web beacons, were used to distinguish visitors, remember preferences and searches, present personalised content and improve the site. Some lasted only for a session; others persisted across visits. Browsers could be changed to block cookies, but full site functionality might be reduced. Use was framed as necessary for contract performance, legitimate interests not overridden by individual rights, legal requirements, or consent where applicable. Do Not Track signals were not treated as changing practice because the operator said it did not track visitors for targeted advertising.

Purposes, lawful bases and marketing

Stated uses included administering and securing the site, internal operations such as troubleshooting, analysis, testing, research, statistics and surveys, measuring advertising effectiveness and delivering relevant advertising, improving content presentation, enabling interactive features, delivering and improving products and user experience, and depositing or redirecting funds where consent or a contract applied. Information from other sources could be combined with directly supplied information for the same purposes. Promotional emails were described as sent where permitted by legitimate interest or with prior consent where required by law, with unsubscribe and account-preference options and an objection right at any time.

ConfigureTargetTest

Storage, security, retention and international users

Data was described as stored securely on AWS in the USA, with application data secured in transit using TLS, payment transactions encrypted using SSL, lifecycle audits including architecture and code reviews, monitoring for abuse, and no customer data hosted on the operator's premises. The archived policy cautioned that transmission security could not be guaranteed and was at the user's risk, while strict procedures and security features were used after receipt. Retention covered the period of expressed interest, the account period for contractual obligations, and six years afterwards for issue identification and legal proceedings, with aggregate information potentially retained longer for research and improvement. For users outside the USA, transfer to the USA and other countries was described, including possible access by courts, law enforcement, regulators or security authorities.

Individual rights and customer-processed data

Under GDPR, rights listed included obtaining a copy of personal data, requesting rectification or erasure, requesting restriction while concerns were verified or investigated, objecting to further processing including marketing, requesting portability to a third party, withdrawing consent where processing was based on consent, and opting out of further location-data access by email. Requests could be made to the compliance contact, with a response within a reasonable timeframe and possible legal limits. A person could also approach a local data protection authority. Where data was processed on behalf of a customer, the customer was controller and the operator was processor under the terms, data processing addendum or signed agreement; the customer's own privacy policy applied, and removal requests from the controller would be answered within a reasonable timeframe.

Changes, contact and reader checklist

Future changes were to be posted on the page, with substantive changes notified by email. Questions, comments and requests were directed to the compliance officer at the operator's postal address and compliance email, both of which require owner confirmation before any live publication. Use this archived summary as a checklist when comparing versions: confirm status and dates, identify whether you are a direct visitor or an end user of a customer, check the lawful basis and purpose, note any optional end-user settings, and record which contact route applies.

Data categories at a glance
CategoryExamples describedKey limit
Direct informationContact, account, financial, photograph, employment historySupplied via forms, registration, correspondence, events or problem reports
Technical and visit dataIP address, browser, OS, URLs, clickstream, interactions, IP-derived locationCollected during site or service use
End-user technicalDevice type, operating systemReceived when a developer uses the products or services
End-user transactionLast-seen time, Apple receipt file, Google purchase tokenRelated to end-user activity in the customer's app or product
Optional end-userEnd-user ID, attribution or metadataOnly if the customer selects or enables the option

Archived December 2025 version; superseded June 2026. Confirm current terms before relying on any category.

Frequently asked questions

Is this the current privacy policy?

No. This version was effective December 2025 and was superseded in June 2026. It is retained only so readers can see what terms applied during that period.

What categories of information does the archived policy describe?

Direct visitors provide contact, account, employment and payment-related details, plus device, browser, visit and IP-derived location information. Developers may also send end-user technical, transaction and, if enabled, optional identifiers and attribution metadata.

What lawful bases were listed?

Processing was described as relying on consent, contract performance, or legitimate interests that are not overridden by the individual's interests, or another basis required or permitted by law.

Who should an end user contact about customer-processed data?

For data processed on behalf of a customer, the customer is the controller and the operator acts as processor under the applicable agreement. Individuals should contact that customer directly to stop processing or correct, amend or delete inaccurate data.

How long was personal data kept?

The policy described retention while a person expressed interest, while an account remained active to meet contractual obligations, and for six years afterwards for issue identification and legal proceedings, with aggregate information potentially kept longer for research and service improvement.