Skip to main content

Security report for accrescent.app

Accrescent · Technology · N/a

Medium risk. 4 critical or high findings in GDPR outside view.

Security score

69/100

Risk levelMedium

0–100, higher is better. How it is calculated

Accrescent is a small technology company operating an Android app store focused on security, privacy, and usability. The platform targets security-conscious Android users and developers by offering features such as app signing key pinning, signed repository metadata, and no requirement for user accounts. The business is currently in alpha stage and positions itself as a niche alternative to mainstream app stores, emphasizing privacy and developer control. Technically, the website is built with standard HTML5 and CSS3, optimized for mobile devices, and includes proper meta tags for SEO. The site is accessible without any WAF or blocking mechanisms. However, no advanced frameworks or CMS are detected, and hosting details are not disclosed. The site performance is moderate with good mobile optimization and basic accessibility features. From a security perspective, the platform demonstrates strong application-level security practices such as key pinning and repository signing. However, the website itself lacks published security policies, security headers, and vulnerability disclosure mechanisms. No privacy or cookie policies are present, which limits privacy compliance. Contact information is minimal but includes a valid company email and multiple social media channels, including open source code on GitHub, which enhances trust. Overall, the website is professional and trustworthy but would benefit from improved privacy compliance documentation, security headers, and incident response information. The risk level is moderate with no critical vulnerabilities detected in the website content. Strategic improvements in transparency and security posture would enhance user trust and compliance readiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

4 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

    • High

      Third-party services without privacy policy

      Detected services: Twitter

      What to do: Document all third-party data sharing in your privacy policy

Need hands-on remediation? Email guard@offseq.com

Keep watching accrescent.app

This scan found 16 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
95
Security headers
90
Email security
70
DNS health
85
Network security
40
GDPR outside view
35
Average
69

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Accrescent operates in the technology sector as a specialized Android app store emphasizing security and privacy. Its competitive advantage lies in its developer-friendly approach and robust security features uncommon in typical app stores. The business model focuses on direct APK distribution without user accounts, appealing to privacy-conscious users. Revenue streams are not explicitly stated but may include donations as indicated by a donate page. The company maintains an active community presence across Matrix, Twitter, Mastodon, Bluesky, and GitHub, supporting engagement and transparency. The market position is early-stage with growth potential in niche privacy-focused Android users. No parent or subsidiary companies are identified, and the company size is small. The lack of detailed business registration data limits deeper corporate intelligence.

Security posture

The security posture of Accrescent is solid at the application level, with key features such as app signing key pinning, signed repository metadata, and no remote APK signing, which mitigate common supply chain risks. The website itself lacks several standard security best practices, including security headers (e.g., CSP, HSTS), published security policies, and vulnerability disclosure mechanisms. No incident response contacts or security.txt files are provided, which could hinder timely vulnerability reporting and response. Privacy compliance is limited due to the absence of privacy and cookie policies. Overall, the security maturity is moderate, with strengths in product security but gaps in website security and compliance documentation.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve privacy compliance and user trust.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance website security.
  3. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide incident response contact channels such as security@ or abuse@ email addresses to improve security communication.
  5. Regularly review and update security and privacy documentation to align with GDPR and other relevant regulations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Accrescent
Description
Accrescent is a private and secure Android app store focused on security, privacy, and usability, providing a developer-friendly platform and pleasant user experience with modern security and privacy practices.
Key services
Android app store, Secure app signing key pinning, Signed repository metadata, Automatic unprivileged updates, Split APK optimization, No remote APK signing, No user account requirement
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3
Platforms
Android
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • App signing key pinning
  • Signed repository metadata
  • No remote APK signing
  • No account required to improve privacy

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is accessible with full content and no WAF blocking.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. Contact information limited to a single company email address.
  4. No phone numbers or physical addresses provided.
  5. No security.txt or vulnerability disclosure information available.
  6. Site is focused on security and privacy for Android app distribution.
  7. Open source code presence on GitHub is a positive trust indicator.
  8. Multiple social media and community links provided for engagement.
  9. No advertising or tracking technologies detected in the HTML content.
  10. No explicit or adult content detected; content is safe for general audiences.
Technical notes

Notes

The website is built using basic HTML5 and CSS3 technologies without detectable advanced frameworks or CMS. It is optimized for mobile devices and includes proper meta tags for SEO and social sharing (Open Graph and Twitter cards). Hosting and infrastructure details are not disclosed, limiting assessment of backend robustness. Performance is moderate with no visible broken elements or errors. Accessibility is basic but could be improved. The absence of JavaScript libraries or analytics scripts suggests minimal tracking and a lightweight site. Technical debt appears low given the simplicity, but modernization opportunities include adding accessibility features and security headers.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with accrescent.app. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review accrescent.app.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.