Privacy, terms, cookies, and accessibility.

2. Information visitors may provide directly

• Contact details, including name, email address, phone number, business name, role, website URL, and preferred contact method.
• Project inquiry details, including service interests, goals, budget notes, timeline notes, platform details, current website issues, business workflow problems, and requested deliverables.
• Form messages, comments, support requests, quote requests, feedback, testimonials, and other voluntary communications.
• Files or reference materials voluntarily submitted for a project, such as screenshots, logos, written content, brand assets, site maps, spreadsheets, reports, design notes, or technical documentation.
• Newsletter preferences, resource download requests, event or update signups, and communication preferences if those options are added later.

3. Information collected automatically

• Technical data, such as IP address, browser type, device type, operating system, screen size, referring URL, pages viewed, timestamps, and approximate location derived from network information.
• Usage data, such as page visits, button clicks, form starts, form submissions, resource views, scroll behavior, navigation paths, and conversion activity when analytics tools are active.
• Security and diagnostic data, such as failed form submissions, suspicious requests, spam signals, server errors, access logs, firewall events, and performance measurements.
• Cookie and similar tracking data, as described in the Cookie Policy section below.

4. Project, client, and technical information

When a visitor becomes a prospect or client, Shibey may receive information needed to evaluate, plan, build, repair, maintain, or improve digital systems. This may include WordPress access, hosting information, plugin lists, theme details, API documentation, analytics reports, ecommerce requirements, form settings, business process notes, automation logic, test data, staging-site access, and issue reproduction details.

Clients should avoid sending passwords, secret keys, API tokens, payment card numbers, or other sensitive credentials through normal website forms or unsecured email unless a secure method has been arranged.

5. How information is used

• To respond to inquiries, schedule conversations, provide estimates, evaluate project fit, and communicate about services.
• To scope, design, develop, test, launch, maintain, troubleshoot, and improve websites, software, automations, analytics setups, SEO structures, AI-assisted workflows, and related systems.
• To operate, secure, monitor, debug, and improve the website, forms, hosting environment, performance, accessibility, navigation, and conversion paths.
• To send administrative notices, project updates, invoices, service communications, support messages, or optional marketing communications where permitted.
• To detect spam, fraud, malware, abuse, unauthorized access, and other security risks.
• To comply with legal obligations, preserve business records, enforce agreements, and protect rights, users, clients, and systems.

6. Analytics, measurement, and improvement

Shibey may use analytics and performance tools to understand how visitors find and use the website, which pages are helpful, where visitors drop off, whether forms are working, and how content can be improved. Analytics data may include page views, traffic source, device category, browser data, general geography, click behavior, and conversion events.

Future analytics work may include dashboards, reporting integrations, tag management, A/B testing, heatmaps, conversion tracking, ecommerce tracking, search performance tracking, or other measurement tools, depending on the services enabled.

7. AI-assisted tools and automation

Shibey may use AI-assisted tools, automation systems, scripts, code assistants, content planning tools, QA tools, or workflow integrations to support project planning and delivery. These tools may help summarize requirements, generate draft code, review implementation details, organize tasks, or test digital workflows.

Client confidential information, credentials, private customer data, and sensitive business records should not be submitted to AI tools unless the client has authorized that use and appropriate controls are in place. Final project decisions, approvals, compliance obligations, and production deployment choices remain subject to human review.

8. How information may be shared

Shibey does not sell personal information. Information may be shared only when reasonably needed for website operation, service delivery, security, legal compliance, or business administration.

• Service providers may include hosting providers, email platforms, form tools, analytics tools, security tools, payment or billing systems, project management tools, code repositories, development tools, cloud services, and communication platforms.
• Client-authorized vendors may include hosting companies, plugin vendors, theme vendors, API providers, ecommerce platforms, advertising platforms, CRM tools, automation platforms, or other systems involved in a project.
• Information may be disclosed if required by law, court order, lawful request, dispute process, fraud investigation, security incident response, or to protect legal rights and safety.

9. Payment, billing, and financial information

If online payments, invoices, retainers, subscriptions, or ecommerce-style purchases are added later, payment information may be processed by third-party payment providers. Shibey should not receive or store full payment card numbers unless explicitly stated by the payment provider workflow. Billing records may include invoice numbers, payment status, billing contact details, transaction references, tax information, and service descriptions.

10. Email and optional communications

Shibey may send replies to inquiries, project communications, administrative messages, service notices, quote follow-ups, support messages, and invoices. If newsletters, educational updates, offers, or resource emails are added later, visitors may opt out of optional marketing communications. Transactional or service-related emails may still be sent when needed to provide active services or maintain records.

11. Data retention

Information is retained only as long as reasonably needed for the purpose it was collected, including inquiry response, project delivery, support, security, legal compliance, tax or accounting records, dispute resolution, backups, audit logs, and service improvement. Different categories of records may have different retention periods. Backup copies and logs may remain for a limited period after deletion from active systems.

12. Security safeguards

Reasonable administrative, technical, and organizational safeguards are used to protect information. These may include access controls, reputable hosting, software updates, secure development practices, spam prevention, malware monitoring, backups, and careful handling of client access. No website, internet transmission, email system, cloud service, or third-party platform can be guaranteed to be fully secure.

13. Visitor and client choices

• Visitors may choose not to submit optional forms or may provide only the information required to process the request.
• Visitors may adjust browser cookie settings, use privacy controls, or opt out of optional email communications.
• Depending on location and applicable law, individuals may request access, correction, deletion, restriction, portability, or objection regarding personal information.
• Some information may need to be retained for legal, security, accounting, dispute, backup, or active service reasons.

14. Regional privacy rights

Privacy rights vary by location. Visitors from certain regions may have additional rights under applicable privacy laws, such as the right to know what information is collected, request deletion, correct inaccurate information, opt out of certain data uses, or limit certain processing. Shibey will review applicable requests and respond as required by law.

15. Children and minors

This website and its services are intended for business, professional, and general adult audiences. Shibey does not knowingly collect personal information from children under 13. If such information is submitted unintentionally, a request can be made to remove it.

16. Links, embeds, and social platforms

The website may link to or embed content from GitHub, Upwork, LinkedIn, Facebook, Instagram, X, video platforms, maps, code repositories, analytics providers, or other third parties. Interacting with those platforms may allow them to collect information under their own policies. Shibey does not control those external platforms.

2. Website content is informational

Website content describes general capabilities, services, examples, process, portfolio work, technical interests, and potential outcomes. It is not a binding offer, guaranteed result, legal promise, fixed quote, or professional compliance opinion. Service availability, timelines, deliverables, pricing, warranties, support, and responsibilities must be confirmed in writing before work begins.

3. Permitted website use

• You may view pages, submit legitimate inquiries, request service information, review portfolio materials, and use the site for ordinary business evaluation.
• You may not submit unlawful, harmful, misleading, abusive, infringing, confidential third-party, spam, malware, or unauthorized content.
• You may not attempt to disrupt, scrape, overload, scan, reverse engineer, bypass security, access non-public areas, or interfere with the website or connected systems.
• You may not use the website or Shibey materials to impersonate Shibey, misrepresent affiliation, or create confusingly similar branding.

4. Service inquiries and estimates

Submitting a form or inquiry does not create a client relationship, guarantee availability, reserve project time, or require Shibey to accept a project. Estimates are based on information available at the time they are prepared. If requirements change, hidden conditions are discovered, third-party constraints appear, or client-provided information is incomplete, price and timeline may change.

5. Project scope and change requests

Project work may include web design, WordPress theme work, WooCommerce, custom code, APIs, automations, dashboards, SEO foundations, analytics, performance improvements, AI-assisted features, maintenance, documentation, or consulting. Approved scope controls what is included. Additional pages, features, integrations, revisions, troubleshooting, emergency work, migration tasks, content creation, compliance work, or support may require a change order, additional estimate, or separate agreement.

6. Client responsibilities

• Provide accurate project information, timely decisions, required access, usable content, brand materials, legal permissions, and feedback by agreed deadlines.
• Confirm that supplied text, images, logos, trademarks, data, software, plugins, themes, videos, fonts, and other materials can legally be used.
• Maintain ownership and access to domains, hosting, email, payment systems, analytics accounts, API accounts, social accounts, licenses, subscriptions, and third-party platforms.
• Review deliverables, test business-critical workflows, approve launches, and report issues promptly.
• Keep independent backups and avoid sending sensitive passwords, API keys, or private customer records through unsecured channels.

7. Access credentials and security

Clients may need to provide temporary access to websites, hosting, WordPress admin areas, code repositories, analytics platforms, DNS, APIs, or related systems. Clients are responsible for creating appropriate access levels, revoking access when no longer needed, maintaining secure credentials, and ensuring that provided access is authorized. Shibey may refuse unsafe credential handling methods or request safer alternatives.

8. Third-party services and dependencies

Projects may depend on WordPress, WooCommerce, hosting providers, domains, DNS, payment processors, email systems, CRMs, analytics tools, tag managers, AI tools, APIs, plugins, themes, font providers, maps, video platforms, social platforms, marketplaces, and other third-party systems. Those services are controlled by their own terms, prices, uptime, policies, limits, updates, licensing rules, and support quality. Shibey is not responsible for third-party outages, policy changes, deprecated APIs, plugin conflicts, vendor bugs, account suspensions, or price increases.

9. Domains, hosting, subscriptions, and licenses

Unless a written agreement says otherwise, clients are responsible for purchasing, maintaining, renewing, and paying for domains, hosting, SSL certificates, premium plugins, premium themes, SaaS subscriptions, API usage, stock assets, fonts, email services, ecommerce tools, and other third-party costs. Failure to maintain these items may cause service interruptions or loss of functionality.

10. Payments, deposits, refunds, and late balances

Payment terms are controlled by the applicable proposal, invoice, subscription, retainer, or written agreement. Deposits, milestone payments, recurring support fees, rush fees, cancellation fees, late fees, refunds, and non-refundable work are handled under the written project terms. Shibey may pause or withhold work, delivery, support, transfer, or launch activities if required payments are not received.

11. Reviews, revisions, and approvals

Projects may include a defined number of revisions or review rounds. Delayed feedback, incomplete content, late approvals, changed direction, new stakeholders, or expanded requirements can affect timeline and cost. Approval of designs, copy, features, tests, staging links, or launch plans indicates authorization to proceed with the next phase unless otherwise agreed in writing.

12. Launches, testing, and post-launch support

Launch timing depends on client approval, access availability, third-party services, DNS propagation, hosting conditions, payment status, content readiness, and testing. Clients should test business-critical workflows, forms, checkout, payment, analytics, automations, and integrations before and after launch. Post-launch support, bug fixes, maintenance, monitoring, backups, updates, and emergency work are included only if stated in the applicable agreement.

13. Intellectual property and ownership

Clients retain ownership of their pre-existing materials. Unless a written agreement says otherwise, final custom deliverables created specifically for a paid client project transfer to the client after required payments are received. Shibey may retain ownership of pre-existing tools, reusable code patterns, development methods, starter templates, internal workflows, documentation structures, generic components, know-how, and non-client-specific improvements.

14. Portfolio and attribution

Unless restricted by written agreement, Shibey may describe completed work in a portfolio, case study, proposal, social post, or capability summary, including project type, general goals, non-confidential screenshots, public links, and technical categories. Confidential information, private business data, unpublished strategies, private credentials, and sensitive internal details should not be published without permission.

15. SEO, analytics, performance, accessibility, and compliance

Shibey may provide technical implementation, recommendations, configuration, reporting, and best-effort improvements for SEO, analytics, performance, accessibility, privacy notices, cookie banners, ecommerce flows, forms, and tracking. Search rankings, traffic, revenue, conversion rates, accessibility conformance, legal compliance, platform approval, or advertising performance are not guaranteed unless expressly stated in writing.

16. AI, automation, and generated outputs

AI-assisted outputs, automation logic, scripts, generated content, generated code, and technical recommendations may require human review, testing, security review, compliance review, and client approval before production use. Clients are responsible for reviewing factual accuracy, brand fit, legal suitability, privacy impact, and business consequences of automated or AI-assisted workflows used in their operations.

17. Confidentiality

Shibey will use reasonable care with non-public client information shared for legitimate project purposes. Clients should label sensitive information clearly and avoid sending unnecessary personal data or secrets. A separate nondisclosure agreement may be used where appropriate. Shibey may still use general skills, knowledge, workflows, and non-confidential lessons learned from projects.

18. Prohibited client requests

Shibey may refuse work involving unlawful activity, deceptive tracking, unauthorized access, malware, credential theft, scraping that violates rights or terms, spam, counterfeit goods, infringement, harassment, evasion of platform rules, or requests that would compromise security, privacy, safety, or professional standards.

19. Suspension, termination, and refusal of service

Shibey may pause, decline, suspend, or terminate website access, project work, support, or communications where there is non-payment, abusive conduct, security risk, legal concern, scope dispute, missing access, unsafe instructions, impossible requirements, or violation of these terms or a project agreement. Termination does not remove payment obligations for completed or authorized work.

20. Disclaimers

The website is provided on an as-is and as-available basis. Shibey does not warrant that the website will be uninterrupted, error-free, secure, compatible with every browser or device, or free from harmful components. Service outcomes depend on many factors outside Shibey control, including client decisions, third-party platforms, market conditions, search algorithms, hosting quality, user behavior, plugin updates, and business operations.

21. Limitation of liability

To the fullest extent permitted by law, Shibey is not liable for indirect, incidental, special, consequential, punitive, exemplary, lost-profit, lost-revenue, lost-data, business interruption, reputational, or third-party damages arising from website use, reliance on website content, project delays, third-party tools, service interruptions, security incidents, or platform changes. Any liability for paid services is limited by the applicable written agreement and applicable law.

22. Indemnification

Users and clients agree to be responsible for claims, losses, damages, liabilities, costs, and expenses arising from their misuse of the website, violation of these terms, supplied materials, unauthorized content, infringement claims, unlawful instructions, or failure to maintain required third-party accounts, licenses, permissions, or approvals.

2. Essential cookies

Essential cookies support core website functions. They may be used for security, page delivery, load balancing, form submissions, spam prevention, login sessions, consent preferences, accessibility preferences, caching, and basic site operation. Blocking essential cookies may prevent forms, navigation, login areas, or security features from working correctly.

3. Preference and functionality cookies

Preference cookies may remember visitor choices such as cookie settings, saved form state, display preferences, region choices, or interface options. If future features include client portals, calculators, dashboards, downloads, or personalization, functionality cookies may support those experiences.

4. Analytics and performance cookies

Analytics cookies may measure traffic sources, page views, scroll depth, click paths, form completions, conversions, device categories, browser behavior, approximate geography, and site speed. Performance tools may help identify slow pages, broken scripts, layout problems, accessibility issues, or conversion bottlenecks.

5. Security, fraud, and spam-prevention cookies

Security cookies and related signals may help detect bots, spam, malware, suspicious requests, abuse, repeated failed submissions, or unauthorized access attempts. These tools may process IP addresses, request headers, browser signals, timestamps, and behavior patterns to protect the website and its users.

6. Marketing, remarketing, and conversion cookies

If advertising, remarketing, or conversion measurement is added later, cookies or pixels may help measure ad performance, understand whether visitors submit forms after seeing campaigns, limit repeated ads, build audiences, or improve campaign reporting. Visitors may have choices through cookie banners, browser controls, ad network controls, or platform-specific settings where available.

7. Third-party and embedded-content cookies

Third-party cookies may be set by tools or embeds such as social platforms, GitHub, Upwork, LinkedIn, Facebook, Instagram, X, video providers, maps, chat tools, analytics providers, payment providers, scheduling tools, email marketing platforms, security tools, or content delivery systems. These providers control their own cookies and privacy practices.

8. Session cookies and persistent cookies

Session cookies usually expire when the browser is closed. Persistent cookies remain for a set period or until deleted. Retention periods depend on the cookie purpose and provider. Some cookies are controlled directly by the website, while others are controlled by third-party tools or platforms.

9. Cookie consent and preferences

The site displays a cookie banner that allows visitors to accept all optional categories, continue with essential storage only, or open a detailed preference center. The preference center lists active service groups, services, and providers and allows visitors to review their local consent history. Analytics and Advertising are separate choices, and configured Google tags do not load until the matching consent is granted. After a visitor chooses, the functional, analytics, and advertising category flags are stored in a compact first-party cookie for up to 365 days. A random consent identifier, timestamps, and up to 20 history entries remain in that browser's local storage for the same period and are not transmitted by the preference-center feature. Preferences can be changed at any time through the Cookie Preferences control in the footer. Choosing essential-only keeps Google advertising and analytics consent denied and removes accessible Google Analytics and advertising cookies. Essential storage may still be used because it is needed to operate and secure the site and remember the visitor's privacy choice.

10. How to manage cookies in a browser

Most browsers allow users to block, delete, or limit cookies. Browser settings may also allow users to clear site data, block third-party cookies, use private browsing, send privacy signals, or manage permissions for location, notifications, camera, microphone, and other features. Blocking cookies may affect form behavior, saved preferences, analytics accuracy, security checks, embedded content, or future client-portal features.

11. Do Not Track, Global Privacy Control, and similar signals

Some browsers and extensions send Do Not Track, Global Privacy Control, or similar signals. Because these signals are not handled consistently across all websites, platforms, and vendors, the site may not respond to every signal unless required by applicable law or supported by the active tools on the website.

12. Server logs and non-cookie tracking

Even when cookies are blocked, the website and hosting provider may process server logs and technical records needed for security, diagnostics, uptime, abuse prevention, debugging, and legal compliance. These records may include IP address, request path, browser information, timestamps, errors, and response status codes.

13. Cookie updates

The cookies and similar technologies used by this site may change as Shibey updates website features, analytics, security tools, forms, embeds, client portals, resource downloads, advertising, automations, or third-party integrations. This Cookie Policy may be updated to reflect those changes.

2. Accessibility standards and references

Shibey may use recognized accessibility guidance when designing, reviewing, and improving website experiences. This may include the Web Content Accessibility Guidelines, semantic HTML practices, keyboard usability checks, contrast checks, heading structure reviews, link clarity reviews, form-label reviews, focus-state checks, responsive testing, and assistive-technology testing where practical.

Accessibility standards, legal requirements, browser behavior, assistive technologies, plugins, third-party embeds, and platform features can change over time. Shibey may update this page and the site’s implementation as practices, tools, services, and requirements evolve.

3. Current accessibility practices

• Use of semantic page structure where practical, including headings, sections, navigation regions, lists, buttons, and links.
• Visible link and button states intended to help keyboard and pointer users identify interactive elements.
• Responsive layouts intended to support desktop, laptop, tablet, and mobile screen sizes.
• Readable spacing, scalable text, clear content grouping, and consistent navigation patterns.
• Attention to color contrast, tap targets, form clarity, focus order, and reduced visual clutter where possible.

4. Keyboard and non-pointer access

The website is intended to support ordinary keyboard navigation for key interactive areas, including menus, buttons, links, form controls, and policy-page anchors. Visitors should be able to move through meaningful content in a logical order and identify the active element when focus styles are available.

If a keyboard trap, missing focus style, unreachable link, menu issue, or other keyboard barrier is discovered, Shibey will review the issue and prioritize a reasonable correction based on severity, affected page, available tools, and implementation complexity.

5. Screen readers and semantic structure

Shibey aims to use meaningful headings, descriptive link text, readable labels, helpful landmarks, and structured content so screen-reader users can understand the page hierarchy and move through the site efficiently. Decorative visuals should not be required to understand core policy, service, contact, portfolio, or resource content.

Some generated, embedded, or third-party content may use markup outside Shibey’s direct control. When issues are found in controllable theme code or site content, Shibey may adjust markup, labels, headings, descriptions, or copy to improve usability.

6. Visual design, contrast, and readability

Shibey intends to use readable typography, sufficient spacing, clear content blocks, distinguishable links, and color choices that support ordinary readability. Color should not be the only method used to communicate important information when another practical indicator can be provided.

Visitors may use browser zoom, operating-system display settings, reader modes, high-contrast modes, or custom stylesheets. Some layout or visual differences may occur when visitors use those settings, but core information should remain reasonably accessible where practical.

7. Motion, animation, and interaction effects

The site may use hover effects, transitions, reveal effects, scrolling sections, cards, buttons, or other visual polish. These effects should support the experience without making core content inaccessible. If future features add heavier animation, video, sliders, interactive demos, dashboards, calculators, or AI-assisted tools, accessibility considerations should be reviewed as part of implementation.

Where reasonable, motion-sensitive users should be able to use platform-level reduced-motion preferences or browser-level controls to reduce visual strain.

8. Forms, inquiries, and communication access

Contact forms, project inquiry forms, newsletter forms, quote forms, resource forms, and future client-intake workflows should use clear labels, understandable instructions, visible error messages, and appropriate input types where practical. If a form is unavailable or difficult to use, visitors may request assistance through another listed contact method where available.

Shibey may use spam prevention, validation, security checks, or third-party form services. These tools can sometimes create accessibility barriers. If a barrier is reported, Shibey may review available alternatives, settings, or implementation changes.

9. Third-party platforms and embedded tools

The website may link to or embed content from platforms such as GitHub, Upwork, LinkedIn, Facebook, Instagram, X, analytics tools, maps, videos, scheduling tools, forms, chat tools, payment providers, code repositories, or other third-party services. Accessibility of those third-party systems is controlled by the provider, not Shibey.

Third-party widgets, plugins, iframes, scripts, cookie banners, social feeds, tracking tags, and embedded media may affect keyboard behavior, screen-reader output, contrast, performance, or focus order. Shibey may adjust or remove third-party tools when practical if they create significant barriers and suitable alternatives exist.

10. Client project accessibility work

For client projects, Shibey may provide accessibility-minded design, development, review, remediation, documentation, recommendations, plugin configuration, content structure, form improvements, contrast adjustments, keyboard checks, responsive checks, or technical implementation. The exact accessibility scope depends on the written proposal, project requirements, client budget, platform limitations, and third-party systems involved.

Accessibility services may require separate review cycles, specialized testing, legal review, user testing, assistive-technology testing, content rewrites, design revisions, plugin changes, theme updates, custom code, or third-party audits. Unless a written agreement specifically says otherwise, accessibility work is performed as best-effort technical and design support, not as a legal guarantee.

11. Legal compliance limits

Shibey may help improve accessibility and reduce barriers, but accessibility laws and compliance obligations can vary by jurisdiction, industry, business type, funding source, audience, and legal context. Website accessibility work does not replace advice from a qualified attorney, compliance consultant, accessibility specialist, or certified auditor.

Clients remain responsible for understanding the legal and regulatory requirements that apply to their own organizations, websites, applications, ecommerce stores, customer data, employment content, public accommodations, government-related services, healthcare content, education content, financial content, and other regulated uses.

12. Ongoing maintenance and future changes

Accessibility can be affected by new content, plugin updates, theme changes, design revisions, third-party scripts, browser updates, media uploads, PDFs, form changes, marketing tags, analytics tools, AI features, automations, ecommerce changes, and future interactive components. Continued accessibility maintenance may require periodic reviews and updates.

If Shibey adds client portals, calculators, dashboards, downloads, resource libraries, ecommerce features, booking tools, AI chat features, automation demos, video content, or interactive case studies in the future, those features may require additional accessibility review beyond this baseline policy page.

13. Known limitations and remediation priorities

Despite reasonable efforts, some barriers may exist or may appear after updates. Examples may include third-party embed behavior, plugin output, legacy browser quirks, unusual assistive-technology combinations, uploaded media without complete descriptions, PDF limitations, color or contrast edge cases, form validation issues, menu behavior, animation preferences, or code introduced by future integrations.

When an accessibility concern is identified, Shibey may prioritize fixes based on the severity of the barrier, the number of affected visitors, whether the issue blocks core information or transactions, whether the code is controlled by Shibey, and whether a reasonable technical fix is available.